Skip to content

fix: use Docusaurus Link component for pathname:// booklet links - #10

Open
nerdalert wants to merge 1 commit into
praxis-proxy:mainfrom
nerdalert:fix/booklet-links
Open

fix: use Docusaurus Link component for pathname:// booklet links#10
nerdalert wants to merge 1 commit into
praxis-proxy:mainfrom
nerdalert:fix/booklet-links

Conversation

@nerdalert

Copy link
Copy Markdown
Member

Summary

Fixes the homepage visual-guide card links so Docusaurus resolves the pathname:/// static-file URLs correctly.

The guide cards in src/pages/index.tsx were using plain <a> tags, which rendered pathname:///... directly into the DOM. Browsers treat pathname: as an unknown protocol, so the booklet links did not navigate correctly. Docusaurus’s <Link> component understands this escape hatch and renders the expected static-file paths.

Also fixes an unrelated broken docs anchor by pointing the payload-processing reference at the dedicated architecture page.

Changes

  • Import Docusaurus’s <Link> component on the homepage
  • Replace the visual-guide card wrapper <a> tags with <Link>
  • Keep the existing pathname:/// hrefs unchanged
  • Fix [payload-processing] reference from system-design#payload-processing to architecture/payload-processing

Test plan

  • npx docusaurus build succeeds
  • Built homepage renders booklet links as /praxis-core-booklet.html, /praxis-ai-booklet.html, and /praxis-grid-booklet.html
  • Build no longer reports the broken payload-processing anchor warning

Plain <a> tags don't understand the pathname:/// protocol — switch to
Docusaurus's <Link> which resolves it correctly.

Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant