feat: add GitHub Pages deployment - #2
Merged
Merged
Conversation
superposition
marked this pull request as ready for review
July 25, 2026 02:09
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.
What changed
coldfront-uilanding page.nojekyll, and a fallback404.htmlWhy
Cold Front currently requires the Topcoat development server. This gives the project a static artifact that can be reviewed locally and hosted on GitHub Pages without coupling the production page to Coatcheck.
Impact
After this merges and GitHub Pages is configured to use GitHub Actions, pushes to
mainpublish the site. Authentication remains optional through theCLERK_PUBLISHABLE_KEYrepository variable.Validation
./scripts/check./scripts/export-pages404.htmlreturned 200node --check crates/coldfront-ui/src/auth.jsgit diff --check