Repository navigation
feat(site): article navigation (ToC) and Ask AI sidebar - #7873
Open
jstirnaman wants to merge 10 commits into
Open
jstirnaman wants to merge 10 commits into
jstirnaman wants to merge 10 commits into
Conversation
What changed: Add the product spec, reviewed implementation plan, and decision record for site-wide article navigation and the Ask AI composer/sidebar. Collapse the ToC at 1280px and below and define exclusive right-side ownership. Why: Extend the API ToC pattern to articles and ground issue #7706 in current code and documented Kapa behavior. Impact: Documentation only. Feature implementation and browser acceptance remain pending. Store the plan outside the root ephemeral filenames so it can merge. Verification: Relative documentation links and whitespace checks pass. The changed-file verifier selects no checks for these documentation paths. Runtime checks were not run.
What changed: Link the spec, implementation plan, and decision record to draft PR #7873. Why: Keep the review location available from the checked-in documents. Impact: Documentation links only. Issue #7706 stays open for implementation. Verification: All documents reference the created draft PR; the feature remains unimplemented.
What changed: Refine the product spec, implementation plan, and decision record for separate desktop ToC and chat columns at 1280px and above. Add a compact width budget, narrower-screen drawer coordination, and screenshot-based acceptance cases. Why: The supplied ChatGPT documentation captures retain both panels at 1280px and 1920px. The previous exclusive-rail plan would hide navigation during chat. Impact: Documentation only. Feature implementation remains pending. Preserve the existing planning commits and leave issue #7706 open. Verification: Relative links and anchors resolve; whitespace checks and the 1280px budget pass. The changed-file verifier selects no manual checks for these documentation paths. No production files or checked-in tests changed; browser and live Kapa validation remain implementation requirements.
What changed: add shared rendered-heading navigation, narrow ToC drawer, scoped sizing, focused browser coverage, and an explicit implementation checkpoint. Why: preserve verified progress and the next red chat handoff test for continuation in a new environment. Impact: API layout integration and the composer lifecycle remain pending. This draft checkpoint is not mergeable; the handoff test intentionally fails until its implementation exists. Verification: two ToC Cypress tests and the Chromium component test passed; TypeScript compilation and diff whitespace checks passed. Live Kapa sidebar verification is blocked by the runtime network policy.
What changed: apply repository formatting to the resumable ToC checkpoint and pending handoff test. Why: retain formatter output in the pushed branch. Impact: behavior and pending verification remain unchanged. Verification: Markdown formatting checked with the pinned Remark tool; staged hooks run on this commit.
jstirnaman
changed the title
What changed: Add shared article/API navigation, the composer and unified widget lifecycle, and a scoped nonmodal desktop adapter. Why: Keep article navigation usable beside chat and preserve drafts across widget failures. Impact: Desktop chat reserves a separate column; narrow layouts retain modal behavior. Preserve widget configuration and API anchors. Verification: Production Hugo build, 15 Cypress tests, three native browser tests, TypeScript, and targeted ESLint pass. Real answer and retained history checks are deferred to a new environment session.
jstirnaman
marked this pull request as draft
October 11, 2026 04:25
Contributor
📦 PR Preview — Preview Bot
Preview auto-deploys on push. Will be cleaned up when PR closes. |
What changed: Add theme colors, rounded corners, a chevron, hover and focus states, and a subtle drawer border and shadow. Why: The default browser button and uncolored border clash with the site UI. Impact: Styles only; heading navigation and responsive behavior stay intact. Verification: Hugo testing build passed. Chromium checks passed in light and dark themes for hover, keyboard focus, toggle, Escape, narrow-screen overflow, and desktop visibility. Screenshots reviewed at the reported tablet width.
What changed: Give the header Ask AI button independent flex alignment. Preserve right alignment in the narrow-screen column layout. Why: Opening the product selector stretched the button to the menu height. Impact: Header alignment only; product selection and chat behavior are unchanged. Verification: Reproduced 32px to 800px growth before the fix. Hugo rebuilt successfully. Chromium checks passed on home and article pages at 375px, 1032px, and 1440px in both themes; button height stays 27px or 32px.
jstirnaman
marked this pull request as ready for review
October 11, 2026 04:59
What changed: Replace the two navigation and Ask AI plan files with ADR 0008. Update the product spec status and decision-record link. Why: Preserve the major decisions and turning points without stale execution steps, checkpoint logs, or duplicated plans. Impact: Documentation only; the product spec remains the behavior reference. Verification: Prettier, relative file links, and whitespace checks pass. Vale reports no errors and one spelling warning for the vendor name Kapa.
jstirnaman
changed the title
jstirnaman
changed the title
This branch has not been deployed
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.
Related: #7706. This PR does not close the issue.
Screenshots
What changed
Why
Readers need consistent section navigation and access to chat without losing their place in an article. The shared layout preserves both controls on desktop while keeping narrow screens usable.
Impact
Readers can navigate sections while desktop chat stays open. API navigation retains operation order, anchors, and method badges. Failed submissions preserve drafts.
The adapter depends on vendor shadow DOM and needs live regression checks when the widget changes. Cross-page conversation persistence and a Chat SDK migration remain outside this change.
Verification
Recorded implementation validation includes a production Hugo build, 15 Cypress checks across
ask-ai.cy.js,ask-ai-sidebar.cy.js, andpage-toc.cy.js, three native browser tests, TypeScript, and targeted ESLint checks. The repository runs end-to-end tests throughyarn test:e2e.Recent preview fixes passed a testing Hugo build and Chromium checks in both themes at phone, tablet, and desktop widths. The ADR update passes formatting, relative file link, whitespace, and commit-hook checks.
Live query acknowledgment passes. Completed-answer and retained conversation history checks remain pending because the environment blocks required reCAPTCHA resources. Network policy changes require a new session.
The dependency audit reports 65 findings in the unchanged dependency tree under the repository's warning-only policy for non-default branches.
Preview pages
/influxdb/v2/get-started/process/Expected: Section links follow rendered headings. The narrow-screen drawer uses theme colors. At desktop widths, navigation remains beside chat.
/influxdb3/core/get-started/write/Expected: Shared-content headings appear in the table of contents. The composer submits the question once and hands off to chat.
/Expected: No table of contents. The Ask AI button keeps its normal height when the product menu opens.