| commit | 75697430a83486921c2f385a679b8ae048aff451 | [log] [tgz] |
|---|---|---|
| author | jenkins <builds@apache.org> | Wed May 01 04:35:14 2024 +0000 |
| committer | jenkins <builds@apache.org> | Wed May 01 04:35:14 2024 +0000 |
| tree | 2be8048c5f252efd641ae9adec14ae1bfe3fb972 | |
| parent | b9dd206295c01738ebab3e8487727ac45fff3664 [diff] |
Updated preview/0421b-staging from preview/0421b at d62b4ec952d4a422b79ca7a04d88b810da1289af Built from https://ci-builds.apache.org/job/Community%20Development/job/site/job/preview%252F0421b/3/
This is the source code for the website of the Apache Community Development PMC website, hosted at:
https://community.apache.org/
To get in touch with that PMC please use the dev@community.apache.org mailing list.
The repository for the events.apache.org website, which is also managed by the Community Development PMC, is at https://github.com/apache/comdev-events-site
Changes to the main branch of this repository trigger the comdev-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://community.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.
TODO: currently disabled in the Jenkinsfile
Branches named preview/* are staged automatically, a branch named preview/demo0421 for example is staged at https://community-demo0421.staged.apache.org/
The website uses Hugo as static website generator, see the Hugo 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.
You need a recent version of hugo, to find out which one is used to deploy this site look at the Jenkins build output, linked above.
To generate the static website, execute hugo to generate the website under target/content and execute npx -y pagefind --source target/content to index the content for Pagefind (the search bar on the website).
During development, it may be useful to run an incremental build. For this to work, execute hugo server -D -d /tmp/comdev-generated-site to continuously (re)generate and serve the website on localhost:1313 (-D means include draft pages). In another terminal, execute npx -y pagefind --source /tmp/comdev-generated-site to index the site content for Pagefind (the search bar on the website).