nextjs-notion-starter-kit VS react-notion-x

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

Formatting the API response (eg. from https://developers.notion.com/reference/retrieve-a-block) is tough, so I want to use a community-maintained package like https://github.com/NotionX/react-notion-x. Most Notion API users use Notion as a website builder so almost all the packages are in React.js or Next.js

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

Using this library, you can easily get data from Notion Pages.

I used an open source Notion library that I'm a main maintainer of called React-Notion-x. It takes Notion data and turns it into html blocks that you can add to your website.

Long: Looks like he is using Notion as a CMS (using something like https://github.com/NotionX/react-notion-x) for his site and not the actual Notion share feature, seen by that the page names are not included in the urls (and that he is using NextJS for his site).

For reference, we're using the notion-compat tool from the react-notion-x package.

There are already existing libraries that wrap it, you can search them on Github, for example this one https://github.com/NotionX/react-notion-x

In my previous article in this series, I had created my own react components to work with the Notion API due to the lack of a recognized renderer that works with Official Notion API. I came across the react-notion-X library but that did not use the Official Notion API then so I chose to create my own renderer. But soon after I published that article, Travis Fischer (creator of react-notion-x and a couple of really handy tools) added support for the official Notion API with notion-compat (still a WIP) which allows you to use react-notion-x’s powerful react renderer with the official API. So I replaced my renderer components with the react-notion-x renderer which gave me a huge performance boost.

Yes, it's using Notion as a CMS + react-notion-x (1) + some custom styling.

(1) https://github.com/NotionX/react-notion-x