minimal-mistakes VS nextjs-notion-starter-kit

My starting point was the Minimal Mistakes theme. From there, I copied the theme repository and meticulously removed everything I didn't need. This left me with the bare essentials, allowing me to build OneFlow from the ground up, but with some basic styling and features already at hand, which Michael Rose (the creator of Minimal Mistakes) has masterfully created.

cf.: https://github.com/mmistakes/minimal-mistakes/issues/2361

https://www.vladsiv.com/

Recently started a personal blog. The plan is to blog about Data Science/Engineering and implementation of modern data solutions in scientific research.

The blog is hosted on GitHub pages using minimal mistakes theme [0] (which I had to customize a lot to suit my needs [1]).

[0]: https://mmistakes.github.io/minimal-mistakes/

Thank you! As for the fonts: I user Jekyll and minimal mistakes for this site, and I just looked it up to verify: By default the theme uses system fonts for all of the font stacks (serif, sans-serif, and monospace). This is done in part to provide a clean base for you to build off of and to improve performance since we aren’t loading any custom webfonts by default. See: here. So it might have to do with the system fonts that you currently have set.

Link to the repository: [https://github.com/mmistakes/minimal-mistakes]

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