![](\"/public/subtle_gltch_logo.png\"){kind=logo}
\n\n\n\n\n\n
with the simplicity of Ghost's Content API.
\n\n\n \n ![\"NPM](\"https://img.shields.io/npm/v/@agency-kit/notion-cms\")
![\"workflow\"](\"https://github.com/agency-kit/notion-cms/actions/workflows/main.yml/badge.svg\"){kind=icon}
\n \n \n ![\"NPM\"](\"https://img.shields.io/npm/dm/@agency-kit/notion-cms\")
![\"commit](\"https://img.shields.io/github/commit-activity/m/agency-kit/notion-cms\")
\n docs |\n quickstart\n
\n\n## Features \n\n🏗️ Framework agnostic - it’s just JS. \n🌲 Build a collection-based CMS tree from your Notion database. \n🎚️ Leverage database structure to control your routing structure. \n⚙️ Geared for Static Site Generation. \n📑 Transform Notion blocks → Markdown, plaintext, and (customizable) html. \n🗃️ Optimized Content Caching for super fast builds. \n🧩 Plugin ready with some powerful core plugins on the way. \n🦾 Tagging, filtering, path queries, and tree-walking utilities. \n⌨️ Totally Typesafe. \n\n## Install\n\n``` npm install @agency-kit/notion-cms ``` \n```pnpm add @agency-kit/notion-cms``` \n```yarn add @agency-kit/notion-cms``` \n\n## Why.\n\nNotion excels at managing content. It also has a great API and SDK. But why is it so challenging to _actually_ leverage Notion as a CMS (Content Management System) in production? \n\nUntil recently there wasn't support for sub-pages (sub-items in a database) in Notion. So most existing Notion-as-a-cms solutions don't provide a way to leverage this new feature, which turns out to be crucial for building a collection-based CMS. Another barrier is that pulling content from Notion can be time consuming. Responses can take a few seconds at times, the API provides a lot of data to sift through, and multiple calls to different endpoints are required in order to go from CMS database to the content for each page. All of this together results in a less than excellent developer experience when using a static site generator that often makes requests on each build.\n\nNotionCMS exists to address each of these issues and provide an excellent developer experience while using Notion as your Content Management System.\n\n## The Database Structure\n\nIn order to make use of NotionCMS, you have to subscribe to a specific database structure. Its an extremely generic design that gives you all the things you need for basic sites but lends flexibility for types of content other than the standard web page, blog post etc.\n\nSee the structure in this template [this template](https://cooked-shovel-3c3.notion.site/NotionCMS-Quickstart-Database-Template-719f1f9d1547465d96bcd7e80333c831?pvs=4).\n\n## Basic Usage\n\n```javascript\n\n// initialize\nconst myCoolCMS = new NotionCMS({\n databaseId: 'e4fcd5b3-1d6a-4afd-b951-10d56ce436ad',\n notionAPIKey: process.env.NOTION,\n // Other options\n})\n\n// Pull down all Notion content\nawait myCoolCMS.pull()\n\n// Access the routes here:\nconsole.log(myCoolCMS.routes)\n\n// Access the page content here:\nconsole.log(myCoolCMS.data)\n\n// Access paths like this:\nconst postA = myCoolCMS.data['/posts']['/how-to-build-a-blog-with-notion']\nconst postB = myCoolCMS.data['/posts']['/how-to-use-notion-cms']\n\n```\n\n## Advanced Usage\n\n```javascript\n\nconst customPlugin = () => {\n return {\n name: 'my-custom-plugin',\n hook: 'pre-parse', // other option is 'post-parse'\n // list of blocks to transform.\n // If hook is post parse, its the string of html parsed from blocks\n exec: (blocksOrHtml) => {\n // do some transformations,\n const transformedBlocksOrHtml = someXform(blocksOrHtml)\n return transformedBlocksOrHtml\n }\n }\n}\n\nconst myAdvancedCMS = new NotionCMS({\n databaseId: 'e4fcd5b3-1d6a-4afd-b951-10d56ce436ad',\n notionAPIKey: process.env.NOTION,\n rootUrl: 'https://mycoolsite.com',\n localCacheDirectory: `${process.cwd()}/localcache/`,\n refreshTimeout: '1 hour',\n plugins: [customPlugin()],\n})\n\nawait myAdvancedCMS.pull()\n\n```\n\nSee the full [API reference](https://www.agencykit.so/notion-cms/guide/api/).\n\n## Some Helper methods\n\n```javascript\n// returns page reference\nmyCMS.queryByPath('/full/path/to/page')\n\n// returns an array of only child pages of a page looked up using the key.\n// This runs queryByPath under the hood so you can save a step\nmyCMS.filterSubPages('/full/path/to/page' /* or Page reference*/)\n\n// returns page object without any children - just the content. Useful for serializing and sending a\n// single pages data to the client.\nmyCoolCMS.rejectSubPages('/full/path/to/page' /* or Page reference*/)\n\n// Get tagged collections this way or by passing a single tag:\nconst tagged = myCoolCMS.getTaggedCollection(['blog', 'programming'])\n\n// walk the CMS from the root node and perform some operation for each node.\n// the node parameter will be of type PageContent so you have access to all of the page data\nmyCoolCMS.walk(node => console.log(node), '/partial/path/to/start')\n\n// for async callbacks\nawait myCoolCMS.asyncWalk(async node => await asynchronousFunc())\n```\n\n## Project Stats\n\n![Alt](https://repobeats.axiom.co/api/embed/c2535fbb6cbc2731c212c332d5bc6cd695c32e0a.svg \"Repobeats analytics image\")\n","readmeFilename":"README.md"}