Tailwind Nextjs Hyperse Blog

This is a Next.js, Tailwind CSS blogging starter template. Probably the most feature-rich Next.js markdown blogging template out there. Comes out of the box configured with the latest technologies to make technical writing a breeze. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.

Facing issues? Check the FAQ page and do a search on past issues. Feel free to open a new issue if none has been posted previously.

Feature request? Check the past discussions to see if it has been brought up previously. Otherwise, feel free to start a new discussion thread. All ideas are welcomed!

Examples

Demo Blog - this repo with latest code
My personal blog - modified to auto-generate blog posts with dates

Be interested in the template? Contactus via github issue, or join dicord community

Features

Easy styling customization with Tailwind 3.0 and primary color attribute
Near perfect lighthouse score - Lighthouse report
Lightweight, 45kB first load JS, uses Preact in production build
Mobile-friendly view
Light and dark theme
Self-hosted font with Fontsource
Supports plausible, simple analytics and google analytics
MDX - write JSX in markdown documents!
Server-side syntax highlighting with line numbers and line highlighting via [rehype-prism-plus]
Math display supported via KaTeX
Citation and bibliography support via [rehype-citation]
Automatic image optimization via next/image
Flexible data retrieval with mdx-bundler
Support for pageable tags - each unique tag will be its own page
Support for multiple authors
Blog templates
TOC component
Support for nested routing of blog posts
Newsletter component with support for mailchimp, buttondown and convertkit
Supports giscus, utterances or disqus
Projects page
Preconfigured security headers
Next.js app-router
Next.js App Router Internationalization (i18n) - next-intl
SEO friendly with RSS feed, sitemaps and more!
Chinese & English language support
sitemap.xml
robot.txt
multiple post layouts support banner|default|simple
typescript support
Kbar search support
computedFields support

Sample posts

Quick Start Guide

Ts (official support) - (community support) -dicord community
Personalize data/siteMetadata.ts (site related information)
Modify the content security policy in next.config.mjs if you want to use any analytics provider or a commenting solution other than giscus.
Personalize data/authors/default.mdx (main author)
Modify data/projectsData.ts
Modify data/headerNavLinks.ts to customize navigation links
Add blog posts
Deploy on Vercel

Development

First, run the development server:

npm start
# or
npm run dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

Extend / Customize

data/siteMetadata.ts - contains most of the site related information which should be modified for a user's need.

data/authors/default.mdx - default author information (required). Additional authors can be added as files in data/authors.

data/projectsData.ts - data used to generate styled card on the projects page.

data/headerNavLinks.ts - navigation links.

components/icons/Logo.tsx - replace with your own logo.

data/article - replace with your own blog posts.

public/static - store assets such as images and favicons.

tailwind.config.ts and css/global.css - contain the tailwind stylesheet which can be modified to change the overall look and feel of the site.

css/prism.css - controls the styles associated with the code blocks. Feel free to customize it and use your preferred prismjs theme e.g. prism themes.

components/SocialIcon - to add other icons, simply copy an svg file from Simple Icons and map them in index.ts. Other icons use heroicons.

components/MDXComponents - pass your own JSX code or React component by specifying it over here. You can then call them directly in the .mdx or .md file. By default, a custom link and image component is passed.

layouts - main templates used in pages.

app - pages to route to. Read the Next.js documentation for more information.

next.config.mjs - configuration related to Next.js. You need to adapt the Content Security Policy if you want to load scripts, images etc. from other domains.

Post

Frontmatter

Frontmatter follows Hugo's standards.

Currently 10 fields are supported.

title (required)
series (optional)
date (required)
tags (required, can be empty array)
lastmod (optional)
featured (optional)
draft (optional)
summary (optional)
images (optional, if none provided defaults to socialBanner in siteMetadata config)
authors (optional list which should correspond to the file names in `data/authors`. Uses `default` if none is specified)
layout (optional list which should correspond to the file names in `data/layouts`)
bibliography(optional)
canonicalUrl (optional, canonical url for the post for SEO)
language(required)

Here's an example of a post's frontmatter:

---
title: Introducing Hyperse Blog Features
series:
  order: 1
  title: 'Blog Starter'
date: '2024-08-10'
lastmod: '2024-08-10'
language: en
tags: ['guides', 'series', 'next.js', 'tailwindcss', 'app-router']
authors: ['default']
images:
  ['/static/images/canada/mountains.jpg', '/static/images/canada/toronto.jpg']
draft: false
summary: Explore the features of the Hyperse Blog template, built with Tailwind CSS and Next.js. This template is designed to be high-performance and easy to use, providing everything needed for modern blogging.
---

Deploy

Vercel
The easiest way to deploy the template is to use the Vercel Platform from the creators of Next.js. Check out the Next.js deployment documentation for more details.

Netlify / GitHub Pages / Firebase etc.
As the template uses next/image for image optimization, additional configurations have to be made to deploy on other popular static hosting websites like Netlify or GitHub Pages. An alternative image optimization provider such as Imgix, Cloudinary or Akamai has to be used. Alternatively, replace the next/image component with a standard <img> tag. See next/image documentation for more details.

The API routes used in the newsletter component cannot be used in a static site export. You will need to use a form API endpoint provider and substitute the route in the newsletter component accordingly. Other hosting platforms such as Netlify also offer alternative solutions - please refer to their docs for more information.

Support

Using the template? Support this effort by giving a star on GitHub, sharing your own blog and giving a shoutout on Twitter or be a project sponsor.

Licence

Hyperse.net