2 ms·
We're building a WordPress-like CMS for Hugo sites. I'm curious if this would improve the Hugo experience for you (commits to your repo, supports media uploads,
by sgallant 9y ago
We're building a WordPress-like CMS for Hugo sites. I'm curious if this would improve the Hugo experience for you (commits to your repo, supports media uploads, Markdown, etc).
https://forestry.io/ https://forestry.io/
We're rolling out a feature soon that will allow you to specify the version of Hugo you're running.
- veidr 9y agoI'm curious, since you have experience supporting both Hugo and Jekyll: which would you recommend? Say I have a personal blog I've been maintaining for 15 years in BlogMaster 3000 for Windows 95, and now I want to make it modern and static and use forestry.io to handle the editing and publishing parts. Are there significant differences in terms of capabilities or ease of use depending on which static blog engine is used for the build step?
- sgallant 9y agoTLDR; If you care about build times, Hugo. Otherwise, Jekyll. For instance, we had a user who had a Jekyll site with 2000 pages. It took Jekyll about 5 mins to compile/build it. After migrating to Hugo it took < 1 second to build. If you don't care about build times, Jekyll has a great community, plugins, and IMO, superior templating syntax (liquid).
- osteele 9y agoMy “learn go” project was a Jekyll clone with fast build times https://github.com/osteele/gojekyll https://github.com/osteele/gojekyll It uses liquid for templating, and emulates a few plugins. It currently works on some sites, not others – YMMV.