Repository navigation
Conversation
The website for issue #10. scripts/build-site.sh writes one static page from the repository itself: a scene per module group from MOD_NAME, MOD_GROUP, MOD_DESCRIPTION, MOD_CONFLICTS and MOD_OPTIONS, the profiles, the guard defaults, the help text of lss, the whiptail menu and data/systems.conf. The Pages workflow runs it on every deploy and the page is never committed, so a module added later (Traefik, say) is on the site without anyone touching it. Scrolling scrubs each scene: log lines appear like a run of lss, module lists roll past, profiles and menu items switch one at a time. Every word is in the HTML from the start; with reduced motion, without scripting or on a short screen the same scenes are a still sequence. No framework, no fonts or requests from elsewhere, a strict Content Security Policy with the inlined stylesheet allowed by its hash. Lighthouse runs in CI and fails below 100 in any category; deploy runs only on main. data/systems.conf becomes the one source of the supported systems and the resource figures; the build fails when the README tables say something else. Refs #10 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: VectoDE <system.bot.discord.utility@gmail.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.
Stage 8 of the 2.0 rebuild: the website on GitHub Pages, lss explained as a film that plays while scrolling.
scripts/build-site.shbuilds one static page from the repository: a scene per module group from the module metadata (MOD_NAME,MOD_GROUP,MOD_DESCRIPTION,MOD_CONFLICTS,MOD_OPTIONS,MOD_REQUIRES), the profiles, the guard defaults,lss --help, the menu oflib/ui.shanddata/systems.conf. The page is generated in the Pages workflow and never committed, so modules added later appear with the next deploy.site/: inlined stylesheet (allowed by its SHA-256 in the CSP),film.js(the only script), favicon, robots.txt. System fonts only, no external requests, no tracking.data/systems.conf: one source for the supported systems and the resource figures; the build fails when the README tables differ..github/workflows/pages.yml: build and Lighthouse (100 in all four categories, three runs, median) on every pull request; upload and deploy only onmain, withpages: writeandid-token: writefor the deploy job alone.docs/website.md: sources, build, CSP and the headers a host should send, deploy.GitHub Pages has to be enabled once with the source "GitHub Actions" before the first deploy from
main.Refs #10
🤖 Generated with Claude Code