Wisp CMS Corporate Blog Template

Wisp CMS Corporate Blog Template is a Next.js 15 starter kit that combines Tailwind CSS and Shadcn UI with the Wisp headless CMS to deliver a server-rendered corporate blog.

What is the Wisp CMS Corporate Blog Template?

The Wisp CMS Corporate Blog Template is an open-source blog starter kit built on Next.js 15 that uses the App Router, TypeScript, and Turbopack for fast server-side rendering. It pairs Tailwind CSS and Shadcn UI for styling with the Wisp CMS to manage blog content, and it outputs a fully responsive corporate blog with automatic table of contents, tag filtering, and full-text search. The template is maintained by Wisp, a CMS company focused on medium-like editorial experiences.

Key Features

• Multi-theme support — Choose from a range of themes or generate your own; apply one by copying the Tailwind class into the FullWidthHeader component.
• Automatic table of contents — Each article gets a generated TOC for quicker navigation; no manual anchor setup needed.
• Tabbed category navigation — Top-level tabs let readers browse posts by category, ideal for news portals and multi-topic blogs.
• Full-text search — Search across every article in the blog without a third-party search service (built into the template).
• Related posts with AI — Uses Wisp's content recommendation to suggest related posts alongside each article.
• SEO automation — Automatically generates sitemap and Open Graph images for each post, plus an RSS feed.
• Custom React components — Render arbitrary React components from CMS content via Wisp's custom component feature.
• Responsive layout and tag filtering — The blog adapts to mobile devices and posts can be filtered by tags.

Who is it for?

• Corporate marketing teams that want a polished blog with minimal maintenance and built-in SEO features like sitemaps and Open Graph images.
• Publications and news sites that need tabbed category navigation and a dynamic table of contents to handle many articles across topics.
• Next.js developers looking for a reference implementation that integrates Wisp CMS, Tailwind, Shadcn, TypeScript, and ESLint in one starter kit.
• Content editors who prefer a medium-like writing experience in Wisp over raw markdown.

What can you do with the template?

• Publish SEO-friendly articles: Write in Wisp's editor, and the template automatically generates sitemap entries, Open Graph images, and an RSS feed from your posts.
• Search and filter content: Readers can use full-text search, click category tabs, or filter by tags to find relevant posts quickly.
• Customize the look: Swap themes by changing a Tailwind class, or extend the blog with custom React components rendered from the CMS.
• Deploy instantly to Vercel: Use the provided Deploy button to clone the repo with environment variables and get a demo blog running immediately.

How does the template work?

The starter includes a Quick Start flow: install dependencies with npm i --legacy-peer-deps (required because next-themes has not been upgraded to React 19), copy .env.example to .env, and set NEXT_PUBLIC_BLOG_ID to the ID from a Wisp account. Running npm run dev starts a local server at http://localhost:3000. When deploying to Vercel, the install command must also use the legacy-peer-deps flag.

FAQ

Is the template free?

Yes, the starter kit is open source and free to use. You'll need to create a Wisp account to obtain a Blog ID for content, but the template itself has no license fee.

Why do I need --legacy-peer-deps?

The project contains a dependency (next-themes) that hasn't been upgraded to React 19. Using npm i --legacy-peer-deps installs the packages while skipping strict peer dependency checks, and the same flag must be used in Vercel's install command.

Can I use my own domain?

Yes, the template uses NEXT_PUBLIC_BASE_URL for canonical URLs and sitemap generation. Set that environment variable to your production domain when deploying.

Does the template support multiple themes?

Yes, you can preview many themes at https://corporate-blog-demo.wisp.blog/theme, and then apply any theme by copying its Tailwind class into the FullWidthHeader component.

Alternatives

For starters that use other headless CMSs, consider Astro with Decap CMS or Hugo with Forestry; each offers a different approach to static site generation rather than a fully server-rendered React blog.