Repository navigation
Focus landing page, move founder narrative to About me, and remove extraneous exports - #70
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 23e815180c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <div class="awakening-actions" aria-label="Continue from the origin text"> | ||
| <div class="awakening-copy landing-copy"> | ||
| <h1>The interdependent way:</h1> | ||
| <p class="landing-statement">a tensored approach to social constructs designed to elicit maximal wealth from sustainable technology implementated in globally interconnected markets</p> |
There was a problem hiding this comment.
Running npm run test:browser will fail in the primary public routes render meaningful headings test: its / entry still requires this is interdependence. this is the way., but that text was moved to /about-me/ and the new root page contains only the landing statement shown here. Update the route-table expectation to the new root heading or statement so the browser gate can pass.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 434433c069
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .landing-stage { display: grid; align-items: center; min-height: calc(100svh - 8rem); } | ||
| .landing-copy { max-width: 58rem; } | ||
| .landing-copy h1 { font-size: clamp(2.6rem, 7vw, 6rem); line-height: 1.08; letter-spacing: -.035em; } | ||
| .landing-statement { margin: 0; max-width: 44ch; font-size: clamp(1.25rem, 2.7vw, 2rem); line-height: 1.5; color: #dce6fa; } |
There was a problem hiding this comment.
When the new / landing page is printed or saved as a PDF through the browser, this explicit pale text color remains active while the preceding print rules switch the page background to white. Because the inherited print color cannot override this declaration, the page’s central statement has extremely low contrast in the resulting document; add a print-specific override for .landing-statement.
Useful? React with 👍 / 👎.
| <p class="eyebrow"><a href="/">The Interdependent Way</a> · About me</p> | ||
| <h1>In Service to Love</h1> | ||
|
|
||
| <article class="awakening-text origin-text" data-copy-field aria-label="In Service to Love"> |
There was a problem hiding this comment.
When a visitor uses the Markdown or PDF control on /about-me/, fieldTitle() cannot find the sibling <h1> inside this export field and falls back to the document title, so the download becomes about-me.md and the PDF heading becomes “About me” rather than “In Service to Love.” The same field previously inherited the correct narrative title from the root document title; include its heading in the field or make the export title derive from the existing aria-label.
Useful? React with 👍 / 👎.
1 participant
The landing page currently opens with the full founder narrative, and automatic export controls clutter navigation cards and layout containers.
This change places the requested landing statement at
/, preserves the In Service to Love article verbatim at/about-me/, and links About me from the landing page and site navigation. It retains the exact supplied wording, including “implementated.”Copy, Markdown, and PDF controls remain on substantive reading fields and explicit export targets. Generic cards, headings, panels, notices, and footer containers no longer receive them.
Existing source, generated-route, browser, and accessibility checks are updated for the new placement. The narrative article was compared byte-for-byte with its previous source. Local source contracts pass (9/9); full production validation and browser checks are required in CI.