building-blog

What building-blog Does

Building Blog is a comprehensive skill that streamlines adding a production-ready blog to Next.js and Sanity CMS websites with SEO optimization and internationalization (i18n) built-in from the start. It guides you through a 40-question intake process that captures your blog’s unique requirements, then generates a detailed one-page implementation plan and a 20-section technical specification. This skill is designed for web development teams and digital agencies that need to launch blogs quickly without sacrificing best practices around search engine optimization and multi-language support.

The skill is particularly valuable for teams building content-heavy websites where blog performance directly impacts organic traffic and user engagement. By automating the planning phase and generating AI-powered hero images, it reduces the time from concept to launch while ensuring your blog follows industry standards for discoverability, accessibility, and global audience reach.

How to Install

1. Access the skill through cload.cloud’s Claude skills directory or visit the GitHub repository at https://github.com/BuildShipGrowRepeat/nextjs-sanity-blog-skill

2. Prepare your environment

   • Ensure you have a Next.js project initialized
   • Have a Sanity CMS workspace set up and accessible
   • Node.js version 16+ installed on your machine

3. Run the intake questionnaire

   • Execute the skill to begin the 40-question guided intake process
   • Answer questions about your blog’s purpose, audience, design preferences, and technical requirements
   • The questionnaire covers content strategy, SEO priorities, language requirements, and performance goals

4. Review the generated plan

   • The skill produces a one-page implementation plan summarizing your blog architecture
   • Review sections covering data models, routing strategy, SEO structure, and i18n approach
   • Make adjustments if needed and confirm to proceed

5. Generate the technical specification

   • The skill outputs a comprehensive 20-section spec document
   • This spec includes API endpoints, component architecture, database schemas, and deployment considerations
   • Use this spec as your implementation guide

6. Generate AI hero images (optional)

   • Leverage the built-in AI image generator for blog post hero images
   • Customize prompts based on your content topics
   • Use generated images to enhance visual appeal without custom design overhead

Use Cases

• SaaS company blog: A B2B SaaS platform needs a blog to drive organic search traffic and establish thought leadership. The skill generates an SEO-optimized structure with proper schema markup, internal linking strategy, and meta tag templates, while i18n support lets them serve content in English, Spanish, and German to different regional markets.

• Multi-language digital agency: An agency manages client websites across 5+ countries. Using this skill, they standardize their blog implementation approach, ensuring every client gets a production-ready blog with consistent SEO fundamentals and language switching capabilities without rebuilding from scratch each time.

• E-commerce educational content: An online learning platform adds a blog to support product education and SEO. The skill’s specification ensures blog posts integrate cleanly with their course catalog, include rich snippets for search visibility, and support their planned expansion into new languages and markets.

• Startup MVP launch: An early-stage startup needs a blog quickly to compete for organic search visibility. The 40-question intake process captures their specific needs faster than extensive discovery calls, while the pre-built specification reduces development time by 60%.

• Enterprise website redesign: A large organization is migrating content from an old WordPress blog to Next.js + Sanity. The skill’s comprehensive spec helps their development team understand the architecture upfront and ensures no SEO performance degradation during the migration.

How It Works

Building Blog operates as a structured planning and specification generation system that translates high-level requirements into actionable technical documentation. The process begins with the 40-question intake form, which systematically captures information across four major dimensions: business goals (target audience, content themes, traffic expectations), technical preferences (performance budgets, deployment platform, analytics tools), content strategy (publishing frequency, content types, keyword focus), and internationalization needs (supported languages, regional variations, cultural considerations). This questionnaire ensures nothing is overlooked and creates a shared understanding between stakeholders before development begins.

Once the intake is complete, the skill analyzes responses and generates a one-page plan that distills the key decisions into an executive summary. This plan covers the recommended blog architecture (headless CMS approach with Sanity), routing and URL structure optimized for SEO (such as /blog/[slug] patterns), multi-language implementation strategy (using Next.js i18n routing or Sanity’s language field approach), and performance targets. The one-page format forces clarity and prevents over-specification, making it easy for stakeholders to review and approve before moving to implementation.

The 20-section technical specification serves as the actual development blueprint, detailing everything from Sanity schema design (blog post documents with SEO fields, author references, and category taxonomy) to Next.js page components, dynamic routing logic, and metadata generation for search engines. The specification includes sections on content modeling, API query optimization, image optimization strategies, canonical URLs for multi-language posts, structured data implementation, caching strategies, and monitoring approaches. Additionally, the skill includes an integrated AI hero image generator that uses DALL-E or similar to create on-brand visual assets based on post titles and topics, eliminating the bottleneck of sourcing or creating custom images for each blog post.

Pros and Cons

Pros:

• Dramatically accelerates the planning phase—converts weeks of discovery into hours of structured intake and specification
• Ensures SEO best practices are baked in from the start rather than retrofitted, improving organic search performance
• Built-in i18n consideration prevents costly rewrites when expanding to new languages or markets
• Reduces architectural decisions through guided intake, minimizing scope creep and stakeholder disagreement
• The one-page plan and 20-section spec create clear alignment between product, design, and engineering teams
• AI hero image generator eliminates bottleneck of sourcing or commissioning blog post images
• Applicable to both startup MVPs and enterprise redesigns

Cons:

• Requires Next.js + Sanity stack—not applicable if you’re committed to other technologies
• Generates specification, not code—your team still must implement the spec, requiring development effort
• The intake process, while comprehensive, may feel rigid if your requirements don’t fit the standard dimensions
• I18n support requires additional configuration beyond the spec (translation management, language-specific content workflows)
• AI hero image generator quality depends on how well post titles and topics map to visual concepts; some content may need manual image sourcing
• The skill assumes you’re building a blog as a feature within a larger Next.js + Sanity site; standalone blog platforms may be overkill

Related Skills

• Next.js Performance Optimizer: Complements Building Blog by identifying and fixing performance bottlenecks in your deployed blog, ensuring fast page loads that improve both user experience and SEO rankings.

• Sanity Schema Designer: Helps structure your content models before using Building Blog, or refine the CMS schema recommendations generated by this skill to match your specific content types and metadata needs.

• SEO Audit & Schema Markup Generator: Works downstream from Building Blog to validate that your implemented blog meets SEO best practices and generates proper structured data for search engines.

• Content Strategy Advisor: Complements the intake process by helping define your blog’s editorial calendar, topic clusters, and keyword strategy before Building Blog generates your technical architecture.

• Multi-language Content Manager: Extends the i18n capabilities to help manage translation workflows, editor assignments, and publishing coordination across supported languages.

Alternatives

• WordPress with Next.js Frontend: Using WordPress as a headless CMS with a Next.js frontend provides flexibility but requires you to handle architectural decisions, performance optimization, and SEO setup yourself without the structured planning that Building Blog provides.

• Strapi + Next.js: An open-source headless CMS alternative that gives you more customization than Sanity but requires more configuration and doesn’t include the strategic planning and intake process that Building Blog offers.

• Custom-built solution: Hiring developers to design and build a blog architecture from scratch gives you maximum flexibility but is significantly slower (weeks vs. hours), more expensive, and prone to missing SEO or i18n best practices without a structured process like Building Blog’s intake and specification approach.