Dev journal is live!
Welcome!
If you’re seeing this, it means spashii.dev is finally live.
So, what is a dev/tech journal?
Think of it as a collection of notes… just don’t expect anything super polished.
How it works?
The site uses Notion as a datasource for content, which Next.js statically renders everytime I deploy through version control. The server refetches content every 1800 seconds and invalidates any stale content. I can also manually invalidate content whenever I update my Notion using a sneaky serverless function. (Go ahead, try to find it) An RSS feed is also generated as a part of the build process.
Related: Rendering a Notion Page
The birth ~
First, I forked https://github.com/Wisp-CMS/nextjs-blog-cms-wisp. This gave me a good starting point for my tech journal. A good starting point, but let’s just say it came with a few “features” like random 500 errors. Kudos to the Wisp dev for the generous free tier, though.

I also didn’t want to duplicate my notes both on Notion and Wisp. I messed around with the Notion API and found cool examples of other people who also made websites using the Notion API. Replacing Wisp SDK with Notion equivalents did the trick.
What’s next?
- Render page
- Tags and tag counts
- Comments (via Git? or Notion)
- More dev journals
- Analytics (vercel analytics)
- Navigate within pages?
- Fork
react-notion-x - Images - favicons, cover images etc
- fix rss
- Dark mode fix
- Fix related posts
- Share item
- Meta tags and SEO and lighthouse?
- Pinned/featured section
- Search
- About page :p
- remove # on /tags
- revalidate button on my notion or apple shortcut
- how rate limiting would work????
- clean up dependencies
- some three js
Built with Notion, Next JS, Tailwind CSS and lots of other open source tools.