Skip to content

docs: adopt the theme-owned navbar (docusaurus-theme 0.5.0) - #14

Merged
jamesbeedy merged 2 commits into
mainfrom
docs/theme-0.5.0
Sep 11, 2026
Merged

jamesbeedy merged 2 commits into
mainfrom
docs/theme-0.5.0

Conversation

@wardbryan3

Copy link
Copy Markdown
Contributor

Summary

Part 4 of the shared theme's migration guide, for the 0.5.0 release that makes the theme own the navbar and drop the footer (vantagecompute/vantage-docusaurus-theme#11).

  • Removes themeConfig.navbar and themeConfig.footer, and the navbarLogo / footerLogo imports that 0.5.0 no longer exports.
  • Passes the GitHub button through the theme's navbarLinks option and drops the .github-button styles. The left-hand Docs and API Reference items have no equivalent by design; both remain in the sidebar.
  • Bumps @vantagecompute/docusaurus-theme to ^0.5.0. This repo carries both package-lock.json (what CI installs with) and yarn.lock; both are regenerated so neither goes stale.

Verified locally

Built against the published 0.5.0: brand link is https://docs.vantagecompute.ai/developer/, the site title is centred with the version badge beside it, the button(s) open in a new tab with the external-link icon, and there is no site footer. Any files the reference-generating plugins rewrote during the local build were reverted; nothing under docs/ changes here.

🤖 Generated with Claude Code

Bryan Ward added 2 commits September 10, 2026 12:00
…eme 0.5.0

Part 4 of the theme's migration guide. The theme now renders the navbar
itself (developer variant, since this site publishes under /developer/)
and renders no footer, so the site's navbar and footer blocks go, along
with the navbarLogo and footerLogo imports that 0.5.0 removes. The GitHub
button moves to the theme's navbarLinks option and its styles go with it.
The install step is lockfile-exact, so the caret range on
@vantagecompute/docusaurus-theme alone never picked up a newer 0.5.x:
the site sat on whatever release the lockfile was last regenerated
against, and every theme patch meant a lockfile commit in every spoke.
Upgrade the theme within its declared range after installing, the way
the theme's own docs site already does. The lockfile change stays on the
runner.

@jamesbeedy jamesbeedy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@jamesbeedy
jamesbeedy merged commit 69d891e into main Sep 11, 2026
1 check passed
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.

2 participants