| commit | e66d3f104e19bafe79f49e731a6d46154565c6ff | [log] [tgz] |
|---|---|---|
| author | Marcus <marcus@apache.org> | Sat Nov 09 18:04:48 2024 +0100 |
| committer | Marcus <marcus@apache.org> | Sat Nov 09 18:04:48 2024 +0100 |
| tree | 0ccb1cf8b43bab3b8886fb0ffc77a58277d68c49 | |
| parent | 2455b312a89798df5034643d45a9c16b0b5f2c27 [diff] |
Fixed markdown syntax
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 dev@openoffice.a.o 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 commits@openoffice.a.o 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 preview/* where * 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 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 html.
base.html is the main page template.page.html extends the base template for the pages.topnav.html is the navigation menu and is included.The CSS stylesheet is in theme/openoffice/static/css/openoffice.css.
All content - pages and assets are in the content tree.
https://github.com/apache/openoffice-project/tree/main/content