Buffalo VS Hugo

You should probably stop because this is not a Go-way. And you wan't find anything with "batteries" other than https://github.com/gobuffalo/buffalo and https://github.com/beego/beego

Haven't see anyone actually using them in production though.

No default. There is Buffalo which is modeled after Rails, haven't used it in anger though.

https://gobuffalo.io

In general, no. But if you do seek for one, I think https://gobuffalo.io is very good.

There is https://gobuffalo.io/ and there is https://github.com/livebud/bud. Both are interesting approaches, but sadly, without real business interest from the community. See, 90% of what makes Laravel Laravel (or Rails Rails) is business adoption. And, as you will sadly find out, the business adoption for traditional Web applications is exactly zero. If you don't want to make the same mistake as I did, and spend 3 years of your life searching for it, do as the others advised - just use the tools and frameworks that have already been built to solve the problem you need.

If you like Ruby on Rails, there is Buffalo.

Buffalo is currently built on Gorilla which complicates building a business on it right now as Gorilla has shifted to public archive since it has no maintainer. https://github.com/gobuffalo/buffalo/issues/2360

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Hugo

Hugo is a popular static site generator specifically designed to create websites and documentation lightning-fast. Its minimalist approach, emphasis on speed, and ease of use have made it popular among developers, technical writers, and anybody looking to construct high-quality websites without the complexity of typical CMS platforms.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.

Doing this made me appreciate existing SSGs like Hugo and Next.js even more👏👏

I suggest hugo: https://gohugo.io/

Generates a completely static website from MD (and other formats) files; also handles themes (including a lot of them rendering well on mobile), and different types of content - posts, articles, etc. - depending on the theme.

It's open source and, being completely static, cheap as fuck to self host.

I would suggest looking into static site generators. Some popular examples, which are used myself are: - Hugo: https://gohugo.io/ - Jekyll: https://jekyllrb.com