3 ms·
To address OP's point about the need to have a bit more control and freedom in the complexity of the content (instead of having only markdown etc), Next.js offe
by jypepin 8y ago
To address OP's point about the need to have a bit more control and freedom in the complexity of the content (instead of having only markdown etc), Next.js offers an "export" script that will export the app as a static asset.
I made a static website with it recently and found it very quick to use, assuming you know React.
No config or setup required (something rare on js projects nowadays), really just "npm install react react-dom next" and you are good to go.
Build a react component at "pages/about.js" and boom, yoursite.com/about routes to this component.
- icemelt8 8y agoThe boom becomes real fun when you realize you can't have nested pages. yoursite.com/profiles/jyepin
- mlcdf 8y agoAnd with that about page comes a bundle of several kb of Javascript... (At least, that how it used to be last time I used it)
- jypepin 8y agoyes it does indeed. I'm not saying it's perfect, but it is a very convenient way of generating a static site with more complex content than simple markdown :)