Add Sanity CMS integration for blog content management #9
Conversation
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
Integrates Sanity.io as the headless CMS for blog content, replacing static content with dynamic content management capabilities. This enables easy blog post creation, editing, and management through Sanity Studio. Key additions: - Sanity client configuration and schema types - Blog post document type with rich text support - Dynamic blog routes with static generation - Portable Text rendering component - Integration tests for CMS functionality - Build validation for static site generation - Environment configuration and documentation Technical implementation: - Next.js 14 App Router with generateStaticParams - Sanity client with proper TypeScript types - Portable Text to React component rendering - SEO metadata from Sanity documents - Image optimization via Sanity's image pipeline Testing coverage: - Sanity integration tests (runtime) - Build validation tests (static output) - Updated GitHub Actions workflow with new test suites Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This commit fixes multiple build issues that were causing GitHub Actions to fail:
1. **Upgrade Next.js 14 → 15**: Resolve peer dependency conflict with next-sanity@11.6.12
which requires Next.js 15+
2. **Handle Next.js 15 breaking changes**:
- Update blog/[slug]/page.tsx to handle async params (now Promise-based)
- Add `export const dynamic = 'force-static'` to robots.ts and sitemap.ts
for static export compatibility
3. **Fix image handling**: Add proper null checks for featuredImage.asset
to prevent build errors when images don't have asset references
4. **Update .gitignore**: Add .env and /dist to prevent committing sensitive
config and build artifacts
The tsconfig.json changes were automatically applied by Next.js 15 for
top-level await support (target: ES2017).
Note: A sample blog post was created in Sanity to satisfy static export
requirements (dynamic routes need at least one static path).
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add null checks for featuredImage.asset in blog listing page to prevent build errors when images don't have asset references. This matches the fix applied to the blog post detail page. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Next.js 15 changed the static export structure:
- Blog listing: out/blog.html (was out/blog/index.html)
- Blog posts: out/blog/{slug}.html (was out/blog/{slug}/index.html)
Updated the validation test to check for the new file structure.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR integrates Sanity.io as a headless CMS for managing blog content on the Good Robot Co. website. The implementation enables dynamic blog post creation and management while maintaining the static site architecture through Next.js static site generation.
Key Features
/blog/[slug]) with static generation at build timeTechnical Changes
blogPostdocument type with rich content supportRichTextcomponent for Portable Text renderinggenerateStaticParamsfor SSGConfiguration
.env.local.examplefile for local developmenttests/config.jsto include new blog routesSANITY_SETUP.mdfor CMS configurationTesting
Test Plan
Prerequisites:
SANITY_PROJECT_ID)SANITY_DATASETvariable (defaults to 'production')Local Testing:
.env.local.exampleto.env.localand add Sanity credentialsnpm installto install new dependenciesnpm run devand verify:/blog/blog/[slug]npm run test:smoke- All smoke tests passnpm run test:sanity- Sanity integration tests passnpm run build- Build completes successfullynpm run test:build- Build validation passesout/blog/contains generated HTML filesCI/CD Testing:
Sanity Studio Testing:
npm run sanity:devto launch Sanity Studio locallyDeployment Testing:
Documentation:
SANITY_SETUP.mdfor detailed CMS configuration instructionsPLAYBOOK.mdfor development workflow and best practices🤖 Generated with Claude Code