undefined | Better HN

0 pointsjdnordy6y ago0 comments

The rendering process happens at build time, so the extra step on rendering isn't affecting performance in production (https://nextjs.org/docs/basic-features/pages#static-generati...).

And it allows me to dynamically "fetch" my writings as I add more. I don't have to create a whole new html file. I simply write a markdown file, add it into the repo on github (I use slackedit which syncs directly to the github repo), then the website gets rebuilt with HTML, and then deployed.

Making the code base more maintainable and better suited for my purposes.

On the other hand, I do agree with you. React is a bit heavy weight for a static website. Next.js still ships the whole react bundle in production. So, while time to first paint is the same speed as a simple html, js site, the time to interaction is much slower and the network load higher.

Trade-offs for sure.

0 comments

gregjor6y ago

I do something similar to publish my site/blog. I write in Markdown, then push to GitHub, which converts the Markdown to HTML and serves it through GitHub pages. I have my own URL but the site actually runs on GitHub. There's a build step but it's handled automatically in GitHub. I'm just writing Markdown.

https://pages.github.com/

That way I'm just maintaining a repo of Markdown files, though I could write HTML files too.

My site is "lightning fast" except for the cursed Disqus plugin, which I want to remove.

https://typicalprogrammer.com

j / k navigate · click thread line to collapse