notion-sdk-js VS nextjs-notion-starter-kit

Here is an example of how to create a new page in your Notion workspace with the blocks converted from the original HTML. We use the @notionhq/client library and you'll need to have a valid Notion API key and database ID:

Provides data fetching functions that add some utility to the notion-sdk

Thousands of great APIs run their developer hubs on ReadMe, where our customers are already documenting every little detail about their API using the OpenAPI Specification. This got us thinking: “the OpenAPI Specification already provides a ton of valuable information about an API, what if we use this to generate an SDK that’s as good as Notion’s JavaScript SDK”?

The official guide actually suggests to poll all the time and compare to local DB to imitate webhooks.

Here are the links if you need them JavaScript https://github.com/makenotion/notion-sdk-js

Hey, I created a Notion automation in Python that sends an Email to a given recipient when the value of a select property in a Notion database is changed. To send the Email, the SendGrid API is used. I inspired myself at the official Notion node.js implementation.

Go To Documentation

I love coming across a great blog like this an realizing it was built using two of my open source repos:

- https://github.com/transitive-bullshit/nextjs-notion-starter...

- https://github.com/NotionX/react-notion-x

Here is a repo I used as a starting point before (repo is not mine) https://github.com/transitive-bullshit/nextjs-notion-starter-kit

The github page: https://github.com/transitive-bullshit/nextjs-notion-starter-kit

Most of services tried to take money from me for custom domains, sitemap, theme etc. Sorry, I don't have enough money for that. 2. nextjs-notion-starter-kit This was the second for me. ① Cannot handle path well It is OK to map your page to /one but it throws 404 error when path is /one/two or /one/two/three. Since I have to map URL like /category1/subcategory2/sub-subcategory3/sub-sub-subcategory4/page5, this is serious problem. Other than that, it seems quite nice. 3. loconotion ① Does not sort pages in directories I tested this without mapping pages to path, but it seems it doesn't sort pages in directories when processing Notion pages. I found python script that sort those pages, but it doesn't support Windows, the only OS I use for general use. ② Slow generation If my site have few pages, it might be good choice, but my site has ~100 pages and a lot of pages will be added in near future. If it converts every pages whenever I launches it, it would take a lot of time. 4. Fruition I think it is just converting Notion page URL into mapped URL. Kind of nice, but still slow as Notion's shared page is. But I think it is doing some 'magic'. I didn't know that CF Worker can do such job. I'm currently using this.

If you want more control over your website via React, then we recommend checking out the accompanying Next.js starter kit, which is free and uses react-notion-x under the hood.

https://transitivebullsh.it

It's powered by Notion as a CMS, react-notion-x, Next.js, and Vercel.

I published an open source starter kit so anyone can easily create similar sites: https://github.com/transitive-bullshit/nextjs-notion-starter...

source code