constate VS react-notion-x

Another one I like is https://github.com/diegohaz/constate, also <100 lines, but it makes contexts much easier to use. FB also uses mostly contexts for state management.

Github

constate - React Context + State

Constate hook provides lifting local state to React Context Level. So you can access/update state variables anywhere in the application with few lines of code. This is useful when you use the same state in multiple components. For example, you have Themes, Colors, Fonts used in multiple components, Users are allowed to change at one place and it should be reflected in the whole application. Package written in TypeScript and very compact.

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