Apache Software Events Website (http://communityovercode.apache.org)

This repository provides the source for the CommunityOverCode website of The Apache Software Foundation. The content and design of the site is the responsibility of VP, Marketing and Publicity. Any proposed improvements or fixes should have issues created first, to be approved by VP, M&P.

• Production website

• Content

  • md pages in GitHub Flavored Markdown (GFM), which can include HTML.
  • ezmd pages in a combination of ezt and GFM.
  • html files are treated as static files.
  • Static assets of all types.
  • .htaccess files for redirection and rewrite rules.

EZMD link syntax

In .ezmd files, EZT processing runs before Markdown. Because both syntaxes use square brackets, write Markdown links and image alt text in .ezmd with an escaped opening bracket:

• Link in .ezmd: [[]Link text](https://example.org)
• Image in .ezmd: ![[]Alt text](./images/example.png)

In normal .md files, use regular Markdown syntax:

• Link in .md: [Link text](https://example.org)
• Image in .md: ![Alt text](./images/example.png)

Adding An Event

For details on adding an event, see content/events/README.md.

• Issues

• Branches. Note that .asf.yaml is set up for autopreview. A branch named preview/mytest for example is automatically staged at https://www-mytest.staged.apache.org/

• Pull requests

  • Creating a pull request

Documentation

Read the ASF-Pelican Getting started guide and the pages it links to.

Notes

The website is built with Pelican.

Continuous Integration / Continuous Deployment (CI/CD) is via the .asf.yaml file mechanism, which runs Buildbot. The build is triggered by changes to the source, and also every 8 hours (currently 1:22, 9:22, 17:22) to pick up changes to external data. It also rotates the featured projects on the main page.

• Pelican Configuration -- Pelican configuration.
• ASF Data Load -- ASF metadata to be used by ezt and Pelican. See asfdata.py.
• ASF YAML Pelican Build -- ASF infrastructure instructions.