GitHub - loriscomba97/publish-from-notion
Write and edit in Notion. Keep your site’s design, URLs and hosting. This kit connects the two through the official Notion API, without making your database public.
Spots 
39 seconds in this recording, on the Free
39 seconds in this recording, on the Free Notion plan with connection webhooks. The wait is accelerated in the GIF; delivery times vary.
Open Every block, rendered to see an article
Open Every block, rendered to see an article with headings, lists, tables, toggles and images. Connect your own database to try publishing.
Requires Git and Node.js 22.18 or later. Start
Requires Git and Node.js 22.18 or later. Start with the local demo; you do not need a Notion account or token for this step.
Open localhost:3000, choose All posts, and open an
Open localhost:3000, choose All posts, and open an article. You should see built-in sample content, including a page demonstrating the supported blocks.
Create a database with Name (title), Slug (text)
Create a database with Name (title), Slug (text) and Published (checkbox). Create a read-only internal connection in Notion and give it access to that database.
Copy .env.example to .env.local. Fill in NOTION_TOKEN and
Copy .env.example to .env.local. Fill in NOTION_TOKEN and NOTION_DATA_SOURCE; keep the local SITE_URL for development. Restart the server. Add a page with a title, a slug such as hello-from-notion, some text and Published checked. Open /blog/hello-from-notion to read it on your site.
The setup guide covers every field, permissions and
The setup guide covers every field, permissions and the optional database setup command. It also explains where to put secrets when deploying.
Use Notion as your editor. The website selects
Use Notion as your editor. The website selects published rows and renders their blocks as HTML. Your database can stay private, and the API token stays on the server.
Update without rebuilding. Signed connection webhooks notify the
Update without rebuilding. Signed connection webhooks notify the website about page edits. The receiving route invalidates cached data so later requests can render the update.