This repo is what I use to power my personal blog / portfolio site tempstuff.com.
It uses Notion as a CMS, fetching content from Notion and then uses Next.js and react-notion-x to render everything.
The site is then deployed to Github Pages.
- Setup only takes a few minutes (single config file) 💪
- Robust support for Notion content via react-notion-x
- Next.js / TS / React / Notion
- Excellent page speeds
- Sexy LQIP image previews
- Embedded GitHub comments
- Automatic open graph images
- Automatic pretty URLs
- Automatic table of contents
- Full support for dark mode
- Quick search via CMD+P just like in Notion
- Responsive for desktop / tablet / mobile
- Optimized for Next.js and Vercel
- Nodejs ~ v12.22.9
- Yarn > 1.22.4
- Git
- Notion public page ID
All config is defined in site.config.js.
- Clone this repo
- Change a few values in site.config.js
yarn installnpm run devto test locallynpm run deployto deploy to vercel 💪
I tried to make configuration as easy as possible.
All you really need to do to get started is edit rootNotionPageId. It defaults to rendering my site's public notion page 22566b6acda44c21b1b59d90827e6928.
You'll want to make your root Notion page public and then copy the link to your clipboard. Then extract the last part of the URL that looks like 22566b6acda44c21b1b59d90827e6928, which is your page's Notion iD.
In order to find your Notion workspace ID (optional), just load any of your site's pages into your browser and open up the developer console. There will be a global variable that you can access called block which is the Notion data for the current page, and you just have to type block.space_id which will print out your page's workspace ID.
I recommend setting up a collection on your home page (optional; I use an inline gallery here) that contains all of your articles / projects / content. There are no structural constraints on your Notion workspace, however, so feel free to add content as you would normally in Notion. There are a few parts of the code with logic to only show comments on blog post pages (collection item detail pages).
The app defaults to slightly different pathnames in dev and prod (though pasting any dev pathname into prod will work and vice-versa).
In development, it will use /nextjs-notion-blog-22566b6acda44c21b1b59d90827e6928 which is a slugified version of the page's title suffixed with its Notion ID. I've found that it's really useful to always have the Notion Page ID front and center during local development.
In production, it will use /nextjs-notion-blog which is a bit nicer as it gets rid of the extra ID clutter.
The mapping of Notion ID to slugified page titles is done automatically for you as part of the build process. Just keep in mind that if you plan on changing page titles over time, you probably want to make sure old links will still work, and we don't currently provide a solution for detecting old links aside from Next.js built-in support for redirects.
See mapPageUrl and getCanonicalPageId from for more details.
NOTE: if you have multiple pages in your workspace with the same slugified name, the app will throw an error letting you know that there are duplicate URL pathnames.
All CSS styles that customize Notion content are located in styles/notion.css.
They mainly target global CSS classes exported by react-notion-x styles.css.
It should be pretty easy to customize most styling-related things, especially with local development and hot reload.
Dark mode is fully supported and can be toggled via the sun / moon icon in the footer.
All extra dependencies are optional -- the project should work just fine out of the box.
If you want to copy some of the fancier elements of my site, then you'll have to set up a few extras.
Fathom provides a lightweight alternative to Google Analytics.
It's optional, but I really love how simple and elegant their solution is.
To enable analytics, just add a NEXT_PUBLIC_FATHOM_ID environment variable.
This environment variable will only be taken into account in production, so you don't have to worry about messing up your analytics with localhost development.
Utteranc.es is an amazing open source project which enables developers to embed GitHub issues as a comments section on their websites. Genius.
The integration is really simple. Just edit the utterancesGitHubRepo config value to point to the repo you'd like to use for issue comments.
You probably want to read through the Utterances docs before enabling this in production, since there are some subtleties around how issues get mapped to pages on your site, but overall the setup was super easy imho and I love the results.
This is a really cool feature that's inspired by Medium's smooth image loading, where we first load a low quality, blurred version of an image and animate in the full quality version once it loads. It's such a nice effect, but it does add a bit of work to set up.
If isPreviewImageSupportEnabled is set to true, then the app will compute LQIP images via lqip-modern for all images referenced by your Notion workspace. These will be stored in a Google Firebase collection (as base64 JPEG data), so they only need to be computed once.
You'll have to set up your own Google Firebase instance of Firestore and supply three environment variables:
# base64-encoded string containing your google credentials json file
GOOGLE_APPLICATION_CREDENTIALS=
# name of your google cloud project
GCLOUD_PROJECT=
# name of the firebase collection to store images in
FIREBASE_COLLECTION_IMAGES=The actual work happens in the create-preview-image serverless function.
Open Graph images like this one will be generated for each page of your site automatically based each page's content.
Note that you shouldn't have to do anything extra to enable this feature as long as you're deploying to Vercel.
By default, every article page will have a table of contents displayed as an aside on desktop. It uses scrollspy logic to automatically update the current section as the user scrolls through your document, and makes it really easy to jump between different sections.
If a page has less than minTableOfContentsItems (default 3), the table of contents will be hidden. It is also hidden on the index page and if the browser window is too small.
This table of contents uses the same logic that Notion uses for its built-in Table of Contents block (see getPageTableOfContents for the underlying logic and associated unit tests).
- create this file (In my case it was not necessary 🤷
// next.config.js
const isProd = process.env.NODE_ENV === 'production'
module.exports = {
assetPrefix: isProd ? '/your-github-repo-name/' : ''
}
- Place a .nojekyll file in the /public directory to disable Github Pages from trying to create a Jekyll website.
The tree should look like this:
├── pages ├── public │ └── .nojekyll │ └── CNAME ├── styles ├── next.config.js
Generate deploy key:
ssh-keygen -t rsa -b 4096 -C "$(git config user.email)" -f gh-pages -N ""
Upload Public into Settings > actions > deploy keys
Upload Private into Settings > actions > secrets
delete them from local
Run the action