Re:Static site generators need less rigid content APIs
by jypepin on Thursday October 11, 2018 @05:53AM
(#18192137)
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.
Re:Static site generators need less rigid content APIs
by jypepin on Thursday October 11, 2018 @07:46AM
(#18192656)
yes 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 :)
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.