Revenge of the JavaScript: Moving from Hugo to Next.js

[giscus[bot]]

Revenge of the JavaScript: Moving from Hugo to Next.js

The next chapter in this website's history of overengineering, from static HTML with Hugo to React everywhere with Next.js.

https://jarv.is/notes/hugo-to-nextjs/

[lbliii]

Hi Jake! I'm a huge Hugo fan and have used it to run a few large-scale documentation sites, however I've been NextJS curious for a while and sometimes get asked to build a NextJS docs site. I'm wondering what you think about NextJS for large scale docs? (Think 4000 articles, toggling 2-3 product versions). I'm struggling to find an example of a NextJS docs site that is at that scale that has 3+ level nesting. Also, at a glance it seems like NextJS sites require manually defining which category/subcategory an article is in -- is there a way to handle it like Hugo where you just have the nav map to the folder structures and recognize the pattern of _index.md > child-pages.md ?

[vargalas]

You’ll have to build the hierarchy processing yourself. Next is just a framework, not a cms. But I’m
working on a similar project in Mextjs and I think, it is the(or a) perfect tool for the job @Ibliii

[i-bsd]

A lot of this post resonated with me, but I'm looking at returning to Hugo after 4 years of building Gatsby and recently Next sites. I miss the minimalism of Hugo.

Main reason being dependency hell, and I can't develop Gatsby/Next sites properly on FreeBSD and OpenBSD. Hugo's portability and simplicity (if you keep it simple) is second to none.