This is the source code for the website of the Apache Events website, hosted at:

https://events.apache.org/

To get in touch with the Community Development PMC (responsible for the website) please use the dev@community.apache.org mailing list.

The repository for the main Community Development website is at https://github.com/apache/comdev-site

Changes to the main branch of this repository trigger the events-site Jenkins Job, which generates the website content and commits it to the asf-site branch of this repository. There's currently (April 2020) a lag of about ten minutes for the Jenkins job to start, if you commit directly to the GitHub repository.

The ASF's gitpubsub mechanism then synchronizes that content to https://events.apache.org/, usually within a few seconds. More details about the publication process can be found in the ASF Documentation about Project sites. If for some reason this process fails, you can use the self-service page from ASF Infra to trigger a resync of the git repo.

A GitHub Action workflow runs daily at 09:20 UTC, to fetch the Comdev calendar events and update the local JSON copy.

Any calendar changes are then committed to to main branch, which triggers a site rebuild as described above.

To update the website quickly after editing the Google calendar, the workflow can also be triggered manually using the Run workflow button on the "Fetch the Google Calendar" workflow page.

The website uses Hugo as static website generator, see their website for more information and for how to install and run it if needed.

Other Apache websites that are built with Hugo should be listed by this GitHub query for the 'hugo' tag.

To generate the static website, execute hugo to generate the website under target/content.

During development, it may be useful to run an incremental build. For this to work, execute hugo server -D to continuously (re)generate and serve the website on localhost:1313.

All PMCs are asked to help promote Community Over Code and other major Apache sponsored events by adding some form of img link to their homepages, in whatever place works best for your site navigation.

The process for doing this is documented at https://apachecon.com/event-images/

• Maintenance of current-event* files for PMC inclusion:

• update text in content/current-event.mdtext
• replace content/images/current-event-*.png files with the new versions from content/ads/ApacheCon