Repository navigation
Rebuild the landing page with Astro and deploy it from Actions - #97
Merged
Merged
Conversation
…tions
Every GitHub Pages build since mid-September failed: the legacy "master /docs"
source runs Jekyll over all of docs/, and a literal "{{" in an installer spec is
a Liquid syntax error, so the live page was stuck on an old build (and the repo
copy still said 0.3.0-beta).
- site/: an Astro one-pager in the app's own brand (amber, Bebas Neue, Source
Serif 4, the crate "P" mark). Latest version, date, installer link and
release highlights come from the GitHub API at build time; a failed lookup
fails the build in CI instead of publishing stale data.
- .github/workflows/site.yml: builds PRs, deploys master via deploy-pages.
- release.yml: a refresh-site job dispatches site.yml on master after each
release (GITHUB_TOKEN releases can't trigger release: published, and a
reusable-workflow call would run on the tag, which github-pages rejects).
- docs/index.html, sitemap.xml and the Google verification file are replaced
by site/ (verification file moved to site/public/).
- wiki: review queues now live in Library Health, not a migration-overlay
"Needs Review" tab; the Preferences tab is "Library", not "Libraries".
Spec: docs/superpowers/specs/2026-09-27-landing-site-redesign-design.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Why
Every GitHub Pages build since mid-September has failed. The legacy "master /docs" source runs Jekyll over all of
docs/, and a literal{{indocs/superpowers/specs/2026-09-09-installer-redesign-plan.mdis a Liquid syntax error. The live page was stuck on an old build, and even the repo copy still said 0.3.0-beta.What
site/: a new Astro one-pager in the app's own brand (amber#C9803F, Bebas Neue, Source Serif 4, the crate "P" mark), with fresh 0.7.3 screenshots. Latest version, date, installer link and release highlights come from the GitHub API at build time. A failed lookup fails the build in CI rather than publishing stale data..github/workflows/site.yml: runsastro checkand builds on PRs; builds and deploys master throughactions/deploy-pages.release.yml: a newrefresh-sitejob dispatchessite.ymlon master after each release, so the page picks up the new version.docs/index.htmlanddocs/sitemap.xml, replaced bysite/. The Google verification file moves tosite/public/.Spec:
docs/superpowers/specs/2026-09-27-landing-site-redesign-design.mdAfter merge
The Pages source switches from "master /docs" to "GitHub Actions". Then the internal
docs/*.mdnotes are no longer served on the site.🤖 Generated with Claude Code