Next.js for static websites

Table of Contents

More freedom to do different things with the content like CSS, search functionality, etc.
Real life experience with using JavaScript, React and Next.js

Generating the markdown files in a way that the application expects is a pain in the butt. The image tags in markdown files are messed up and they needed to be carefully cleaned up before each commit.
Need to put in a little bit of work upfront. Writing javascript code to parse through the files is more involved than using something like Hugo that take a plug and play approach.

Done using ox-hugo

This will be automatic if we build a NextJS application.

This will be automatic if we build a pipeline for the NextJS application.

Working with third party libraries don’t always result in the output that one would expect. You could be expecting one thing when you start the project and when you implement it, the results may not make much sense at all. In my case, I was supposed to use a library called markdown-to-jsx to render markdown files as html content. But the results were a disaster. The raw md content was shown in the browser - even when I followed the documentation to a T.

If you cannot write all the pieces of code yourself, don’t trust the javascript approach.