I’m Ryan and I commented on your Elmstatic thread a few days ago in the #elm-dev channel! Thanks again for sharing it with the community!
For us, it was also important for us to provide a solution like Netlify CMS so that our client could easily update content through a UI. For this project, we’re using Forestry, but it does the same thing. (I’ve used Netlfiy CMS on my last project, and they’re both great tools!)
Instead of using Elmstatic (which you taught me about a few days ago ), I decided to use a slightly more popular static site generator called Hugo.
Hugo turns the markdown files into HTML and JSON API endpoints for me, and passes the content in as flags to the Elm application. Having the JSON API allows me to do client-side navigation and cool things like page transitions!
The site build is still in progress, so the repo is private for now. but if you’re interested in learning more, I’d be happy to walk you through how I set it up!
Just reach out on the Elm Slack
Long term, I’d like to share my experience with the rest of the Elm community. Maybe that’s a blog post or YouTube tutorial, but I want to wrap up the project first haha.
I figured your use case was more time sensitive so I should post here!
Here’s the stack I’m using:
Have a great day!