release: v0.1.0#12
Merged
Merged
Conversation
# Vercel Web Analytics Installation
Successfully installed and configured Vercel Web Analytics for this Next.js project.
## Changes Made
### 1. Package Installation
- Added `@vercel/analytics` package (v2.0.1) using pnpm
- Package was installed following the latest official Vercel documentation
### 2. Code Changes
**Modified: `src/app/layout.tsx`**
- Added import: `import { Analytics } from '@vercel/analytics/next';`
- Added `<Analytics />` component inside the `<body>` tag, after the `</ThemeProvider>` closing tag
- Placement ensures Analytics loads on all pages while respecting the existing provider hierarchy
### 3. Dependencies Updated
**Modified: `package.json`**
- Added `@vercel/analytics` to dependencies
**Modified: `pnpm-lock.yaml`**
- Lockfile updated to include @vercel/analytics and its dependencies
## Implementation Details
Following the official Vercel Analytics quickstart guide (https://vercel.com/docs/analytics/quickstart), the implementation uses the Next.js App Router pattern:
1. The Analytics component is imported from `@vercel/analytics/next` (the framework-specific export)
2. The component is placed inside the root layout's `<body>` tag
3. This ensures analytics tracking is active on all pages across the application
## Verification
- ✅ No linting errors introduced in `src/app/layout.tsx`
- ✅ Package successfully installed via pnpm
- ✅ Import statement follows Next.js App Router conventions
- ✅ Component placement preserves existing layout structure
- ✅ Lock file updated correctly
## Notes
- The build step requires Ghost blog environment variables (GHOST_API_URL, GHOST_CONTENT_API_KEY) which are unrelated to this change
- Once deployed to Vercel, analytics will automatically start collecting data
- No additional configuration is required in the code
- Analytics can be viewed in the Vercel dashboard after enabling the feature
## Post-Deployment Steps
After deployment, you should:
1. Enable Analytics in your Vercel project dashboard (Analytics → Enable)
2. Verify implementation by checking the Network tab for requests to `/_vercel/insights/*`
3. View analytics data in the Vercel dashboard
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Each docs section layout passes nav={{ enabled: false }} to fumadocs
DocsLayout to avoid duplicating the site Navbar. That also removes
fumadocs's mobile SidebarTrigger, which lived inside the disabled nav,
leaving the sidebar drawer (section picker + page tree) unreachable
below the md breakpoint.
Add a DocsSidebarTrigger client component that calls useSidebar() from
fumadocs's RootProvider context, and render it in the site Navbar's
existing mobile cluster. It only mounts on /docs routes and only at
viewports below md, where the desktop sidebar is hidden.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Reworks the mobile nav pattern on /docs so users get one hamburger trigger instead of two stacked icons. The site hamburger opens the fumadocs sidebar; inside it, a "Main menu →" button overlays the site nav drawer on top. Closing peels one layer at a time. On non-docs routes the hamburger behaves as before. While in there, two real bugs: - The site drawer used to render as a child of <header>. When the header gets backdrop-blur (scrolled state), it establishes a new containing block for position:fixed descendants — the drawer's inset-0 collapses to the header's tiny vertical box and renders invisible. Drawer now portals to document.body via createPortal. - Scroll lock used overflow:hidden on <html>, which strips position:sticky of its scrolling ancestor and drops the header out of the viewport when the menu opens after scrolling. Switched to overflow:clip — same lock, no scroll container established, sticky preserved. Plus a 1rem top-padding rule on #nd-sidebar-mobile (banner was flush against the header) and a small MobileNavProvider context so the "Main menu →" button inside the docs sidebar can drive site-drawer state from inside <main>. Deletes the standalone DocsSidebarTrigger introduced in #9 — that dual-icon approach is superseded by the stacked-drawer pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Rename package.json from "plasma-nextjs-template" to "fleetbase.io" and reset version to 0.1.0 (first Fleetbase-versioned release). - Add CHANGELOG.md following Keep a Changelog conventions. - Add .github/workflows/release.yml — pushing a vX.Y.Z tag publishes a GitHub Release whose body is the matching CHANGELOG section. Validates package.json version matches the tag and refuses to release if no CHANGELOG entry exists for the version. Pre-release tags (e.g. v1.0.0-rc.1) are auto-flagged as pre-releases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
First Fleetbase-versioned release of fleetbase.io. Bundles three pending PRs and establishes versioning conventions going forward.
Bundled PRs
bcf6078→08ef607)Each was merged with
--no-ffso the original PR commits are preserved in history.Conventions established
plasma-nextjs-template→fleetbase.io, version reset to0.1.0.## [X.Y.Z] - YYYY-MM-DDsection per release..github/workflows/release.ymltriggers onv*.*.*tag push. It validates the tag matchespackage.jsonversion, extracts the matching CHANGELOG section, and publishes a GitHub Release. Pre-release tags (-beta.1,-rc.1) are auto-flagged.Cutting future releases
release/vX.Y.Zbranch frommain.package.jsonversion. Add a## [X.Y.Z]section toCHANGELOG.md.main. Review, merge.git checkout main && git pull && git tag vX.Y.Z && git push origin vX.Y.ZPost-merge follow-ups
🤖 Generated with Claude Code