|author||mseidel <firstname.lastname@example.org>||Fri Jul 22 18:48:11 2022 +0200|
|committer||mseidel <email@example.com>||Fri Jul 22 18:48:11 2022 +0200|
Changes for the AOO 4.1.13 release
This is the content and theme for https://openoffice.apache.org/
You can fork from https://github.com/apache/openoffice-project, test your changes as described below and raise a pull request.
You can simply raise a pull request with a set of simple changes.
Use the firstname.lastname@example.org mailing list to contact the OpenOffice PMC which manages this website.
Commits to the
main branch are automatically published using Pelican using the instructions in the
.asf.yaml file. Information about
.asf.yaml is found here.
Any build failures are reported to email@example.com mailing list.
Updating a single file is simple. Simply edit the file online and save with your commit message. The website will be published in a minute or two.
Create a branch named
* is the name of your new feature. For example if your feature branch is named
preview/refresh then commits are automatically staged to https://openoffice-refresh.staged.apache.org
Once your features are ready you can create a PR and do a squash & merge.
All of the pages in the site are in Github Flavored Markdown in
md files. See GFM.
Pelican templates are included in the
theme/openoffice/templates directory. The site templates are written in
base.htmlis the main page template.
page.htmlextands the base template for the pages.
topnav.htmlis the navigation menu and is included.
The CSS stylesheet is in
All content - pages and assets are in the content tree.