feat(docs): Landingpage mit Projektübersicht - #3
Merged
Merged
Conversation
The site opened with the docToolchain placeholder page, which said nothing about this project. Replace it with an overview: what the generator does, the four build phases, one card per document, and how to build the templates and the site. It reuses the theme's own CSS classes, so it does not drift from the rest of the site. The page lives in site/doc/landingpage.gsp. microsite.siteFolder resolves relative to docs/, so '../site' keeps the template outside the published output - inside docs/ the .gsp would be copied along as a stray asset. Harden the workflow check while here. generateSite reports success even when the landing page template fails to parse; it then writes an index.html without any landing content. That happened during development: a '$/' in the text was read as the start of a GSP expression, the include failed, and the build still went green. The check now looks for landing content, not just for a non-empty file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014S4btgSH36ViayKLqGLd6G
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.
Was sich ändert
Die Startseite war die Platzhalter-Seite des docToolchain-Themes — „Solution Architecture Documentation for System X". Sie sagte nichts über dieses Projekt.
Neu: eine Übersicht, die den Generator erklärt.
Sie nutzt die CSS-Klassen des Themes (
dtc-hero,dtc-card,dtc-pipeline), driftet also optisch nicht weg.Wo die Datei liegt
site/doc/landingpage.gsp, nichtdocs/site/....microsite.siteFolderlöst relativ zudocs/auf; mit'../site'bleibt das Template außerhalb der veröffentlichten Seite. Innerhalb vondocs/wird es als Asset mitkopiert und landet alssite/doc/landingpage.gspim Output — nachgemessen und deshalb verschoben.Der Workflow-Check greift jetzt wirklich
Beim Entwickeln ist genau das passiert, wogegen EPIC 1 des Backlogs antritt:
generateSitemeldet Erfolg, obwohl das Template nicht geparst werden konnte.Ein
/^[A-Z]{2,}$/im Fließtext — die GSP-Engine las$als Expression-Start, der Include scheiterte, und der Build lief grün weiter. Dieindex.htmlexistierte, war aber inhaltsleer; der bisherige Checktest -s index.htmlhätte das durchgewunken.Der Check sucht jetzt nach Landing-Inhalt statt nur nach einer nicht-leeren Datei:
Test
🤖 Generated with Claude Code
https://claude.ai/code/session_014S4btgSH36ViayKLqGLd6G
Generated by Claude Code