Repository navigation
Rebuild the website with Docusaurus - #110
Merged
Merged
Conversation
Member
Author
|
Some links to the GitHub repo, especially to the Merging for now. |
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the outdated Pelican website with a compact Docusaurus site in the existing
site/directory. The new pages cover the current v3 application, tally tools, community, and release status, link to documentation maintained alongside the code, and remove the outdated member list. Common legacy.htmlURLs redirect to the new pages.GitHub Actions validates website changes, publishes
preview/<name>branches to ASF staging, and publishestrunktoasf-site. Generated branches retain their history, include the required.asf.yaml, and are cleaned up when a preview PR closes. This replaces the Pelican publishing configuration.Project metadata stays in
.asf.yaml; the build generates/doap.rdffor consumers that require XML. After the website is published to production, a separate change inapache/comdev-projects/data/projects.xmlmust repoint STeVe from the SVN DOAP tohttps://steve.apache.org/doap.rdf. Until then, the legacy project feed continues to read SVN.Live preview: https://steve-website.staged.apache.org/
Validation:
pnpm validate: formatting, metadata/serialization tests, production build, and broken-link checks.actionlintfor both website workflows.uv run ruff format .,uv run ruff check --fix ., anduv run mypy --ignore-missing-imports .inv3/.