Repository navigation
feat: add feature highlights and footer to landing page - #121
Merged
Merged
Conversation
Co-authored-by: Muse Code <muse-code@meta.com>
Co-authored-by: OpenAI Codex <noreply@openai.com>
Describe the existing catalog and TechDocs search accurately and record the rendered highlights and footer. Co-authored-by: OpenAI Codex <noreply@openai.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
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.
The landing page at
/landingnow continues below the portal screenshot with four feature cards for software templates, the catalog, GitHub integration and search. Each card links to its existing portal surface. A footer repeats the showcase and catalog entry points and explains read-only guest access.The search card describes the existing catalog and TechDocs search rather than promising cited answers. This continuation also merges current main into the existing branch without rewriting history and adds the previously missing browser proof.
Part of #84
Closes #120
Verified on the final implementation through mise
mise run installpassed, with existing peer-dependency warnings and no lockfile changes.mise run lintpassed across all five packages.mise run test -- --runInBand --verbosepassed 37 tests in 6 suites, with 1 skipped test in 1 skipped suite.mise run devserved this worktree on localhost:3000 and the backend on localhost:7007. Entered the read-only guest demo and verified all four cards and both footer links in the AO browser.git diff --checkpassed.mise run buildwas not run locally because this slice changes frontend content and tests only. The final-head CI Build job passed install, lint, tests and the Docker build in 5m39s. CodeQL and both Socket Security checks also passed onb2c30a1.Final-head CI build
The verbose test output includes
Captured with
mise run devandao browser screenshotafter guest entry, scrolled to the highlights and footer. The 2560 x 1440 PNG is committed at.tmp/proof/landing-highlights.png. The capture succeeded on this continuation run.The route remains
/landing. Whether it replaces/remains Johnny's decision. The parent epic stays open. Search currently provides catalog and TechDocs results; a live cited-answer service is outside this slice. Existing React/MUI deprecation warnings and jsdom stylesheet parsing warnings were observed during verification; the render and all test assertions passed.