All Collections
Getting Started with Hashnode
Getting started with Hashnode Headless CMS: Starter Kit Guide
Getting started with Hashnode Headless CMS: Starter Kit Guide
Updated over a week ago

Hashnode Headless CMS empowers you to build a blog from the ground up using Hashnode's innovative GraphQL APIs. However, we recognize that many users and teams may not have ample time to construct a blog from scratch at the outset. Therefore, we have developed an open-source starter kit, which you can use to customize and directly deploy to your domain. This starter kit integrates with Hashnode's new GraphQL APIs and is powered by the Next.js framework and TailwindCSS for styling.

You have the freedom to deploy it on your preferred cloud hosting provider, and host it on any custom domain or custom domain sub-paths, such as '/blog.' Best of all, you can continue to leverage Hashnode's authoring tools, including the editor and dashboard, to publish, manage, and collaborate with your team effectively.

Please note: Hashnode Headless CMS is free for independent bloggers or personal blogs. To create a team blog for your product or company, get in touch for access and pricing info.

Follow the steps to start a headless blog on Hashnode:

  1. Create a new personal blog or a team blog on Hashnode if you don't have one already.

  2. Head over to the blog dashboard. You can access the dashboard by adding /dashboard to the blog URL or click on dashboard icon on "Manage Blogs" page.

  3. Go to "Advanced" tab inside the dashboard.

  4. Select "Enable headless mode".

  5. Enter the domain URL where you plan to build and host your custom blog. It can be a custom domain or a sub-path of a custom domain like /blog.
    โ€‹

  6. Fork our open source Blog Starter Kit and deploy it under your custom domain or domain subpath.

  7. Now you are all set. You can now use Hashnode's editor and dashboard to manage your content and fully customize the blog frontend using our starter kit.

  8. Follow the instructions on the GitHub repo's Readme to deploy on custom domain and custom domain sub-path like /blog.

Did this answer your question?