https://www.geekskai.com/

This is a Next.js, Tailwind CSS blogging template. Version 2 is based on Next App directory with React Server Component and uses Contentlayer to manage markdown content.

Probably the most feature-rich Next.js markdown blogging template out there. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.

Check out the documentation below to get started.

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!

• Next.js with Typescript
• Contentlayer to manage content logic
• Easy styling customization with Tailwind 3.0 and primary color attribute
• MDX - write JSX in markdown documents!
• Near perfect lighthouse score - Lighthouse report
• Lightweight, 85kB first load JS
• Mobile-friendly view
• Light and dark theme
• Font optimization with next/font
• Integration with pliny that provides:
  • Multiple analytics options including Umami, Plausible, Simple Analytics, Posthog and Google Analytics
  • Comments via Giscus, Utterances or Disqus
  • Newsletter API and component with support for Mailchimp, Buttondown, Convertkit, Klaviyo, Revue, Emailoctopus and Beehiiv
  • Command palette search with Kbar or Algolia
• 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
• Github alerts via remark-github-blockquote-alert
• Automatic image optimization via next/image
• Support for tags - each unique tag will be its own page
• Support for multiple authors
• 3 different blog layouts
• 2 different blog listing layouts
• Support for nested routing of blog posts
• Projects page
• Preconfigured security headers
• SEO friendly with RSS feed, sitemaps and more!

1. Clone the repo

npx degit 'geekskai/blog'

2. Personalize siteMetadata.js (site related information)
3. Modify the content security policy in next.config.js if you want to use other analytics provider or a commenting solution other than giscus.
4. Personalize authors/default.md (main author)
5. Modify projectsData.ts
6. Modify headerNavLinks.ts to customize navigation links
7. Add blog posts
8. Deploy on Vercel

yarn

Please note, that if you are using Windows, you may need to run:

$env:PWD = $(Get-Location).Path

First, run the development server:

yarn dev

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

Edit the layout in app or content in data. With live reloading, the pages auto-updates as you edit them.

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

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

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

data/headerNavLinks.js - navigation links.

data/logo.svg - replace with your own logo.

data/blog - replace with your own blog posts.

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

tailwind.config.js and css/tailwind.css - tailwind configuration and 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.

contentlayer.config.ts - configuration for Contentlayer, including definition of content sources and MDX plugins used. See Contentlayer documentation for more information.

components/MDXComponents.js - pass your own JSX code or React component by specifying it over here. You can then use them directly in the .mdx or .md file. By default, a custom link, next/image component, table of contents component and Newsletter form are passed down. Note that the components should be default exported to avoid existing issues with Next.js.

layouts - main templates used in pages:

• There are currently 3 post layouts available: PostLayout, PostSimple and PostBanner. PostLayout is the default 2 column layout with meta and author information. PostSimple is a simplified version of PostLayout, while PostBanner features a banner image.
• There are 2 blog listing layouts: ListLayout, the layout used in version 1 of the template with a search bar and ListLayoutWithTags, currently used in version 2, which omits the search bar but includes a sidebar with information on the tags.

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

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

Content is modelled using Contentlayer, which allows you to define your own content schema and use it to generate typed content objects. See Contentlayer documentation for more information.

Front matter follows Hugo's standards.

Please refer to contentlayer.config.ts for an up to date list of supported fields. The following fields are supported:

title (required)
date (required)
tags (optional)
lastmod (optional)
draft (optional)
summary (optional)
images (optional)
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`)
canonicalUrl (optional, canonical url for the post for SEO)

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

---
title: 'Introducing Tailwind Nexjs  Blog'
date: '2021-01-12'
lastmod: '2021-01-18'
tags: ['next-js', 'tailwind', 'guide']
draft: false
summary: 'Looking for a performant, out of the box template, with all the best in web technology to support your blogging needs? Checkout the Tailwind Nextjs  Blog template.'
images: ['/static/images/canada/mountains.jpg', '/static/images/canada/toronto.jpg']
authors: ['default', 'sparrowhawk']
layout: PostLayout
canonicalUrl: https://geekskai.com/blog/js/how-to-remove-milliseconds-from-timestamp-in-js/
---

A pages.yml workflow is already provided. Simply select "GitHub Actions" in: Settings > Pages > Build and deployment > Source.

The easiest way to deploy the template is to deploy on Vercel. Check out the Next.js deployment documentation for more details.

Netlify’s Next.js runtime configures enables key Next.js functionality on your website without the need for additional configurations. Netlify generates serverless functions that will handle Next.js functionalities such as server-side rendered (SSR) pages, incremental static regeneration (ISR), next/images, etc.

See Next.js on Netlify for suggested configuration values and more details.

Run:

$ EXPORT=1 UNOPTIMIZED=1 yarn build

Then, deploy the generated out folder or run npx serve out it locally.

$ EXPORT=1 UNOPTIMIZED=1 BASE_PATH=/myblog yarn build

Consider removing the following features that cannot be used in a static build:

1. Comment out headers() from next.config.js.
2. Remove api folder and components which call the server-side function such as the Newsletter component. Not technically required and the site will build successfully, but the APIs cannot be used as they are server-side functions.

• How can I add a custom MDX component?
• How can I customize the kbar search?

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

MIT © geeks kai