Fragmenta – A Golang CMS
fragmenta.eu
fragmenta.eu
If I'm just a guy who needs a CMS, then I really want to know what this offers as a CMS vs any other solution. I don't think it would really matter to me whether this was written in Golang or PHP or Python since I'd want to use the system to manage my content, not be writing code for it.
The tagline "build websites with Go" is even a bit scary because it makes it sound like rather than being a CMS, this is something where I need to know how to program in order to use it.
But everything else on the page is very dev-oriented... but in that case, as a dev, I'd really rather have the install, capabilities, requirements, etc. up front in a clean table rather than the CMS GUI demo.
Maybe I'm alone in feeling this way, though. :)
To your point, they could just advertise the advantages instead of using "Go" as a proxy term, but it does draw me in a bit more since I'm already familiar with Go.
> The tagline "build websites with Go" is even a bit scary because it makes it sound like rather than being a CMS, this is something where I need to know how to program in order to use it.
This isn't a CMS for non developers, obviously. This isn't Wordpress.
If you are not a developer and don't need advanced features like a comment system, you'd be better of with a tool like "Hugo" which generates static HTML files from manifests that you can then upload on any cheap host via SFTP. It's more secure and performs better than a solution running its own server.
I attempted to build something that fits the bill by building a self-hosted Git powered CMS that publishes with Hugo.
That could be emphasized. "Set of libraries by which devs can quickly create robust and performant CMS providing a UI that content editors love to use."
I’m about to move my site over to Wordpress and deploy it using one of the static site generators. With ACF everything is so easy and quick.
[0]: http://cppcms.com/wikipp/en/page/main
[1]: http://cppcms.com/wikipp/en/page/faq#If.CppCMS.is.not.a.CMS.....
I have to say though, the "What doesn't it do?" section seems like an extension of the "What does it do?" section. A "What doesn't it do?" should list what the CMS actually doesn't do instead of listing things nobody wants anyway. Who wants "hundreds of complicated back-end screens"? No-one. So no need to say that the CMS doesn't do that.
My first glance looks seems to suggest no, but I want to be wrong.
This is where I hope some package is really good and makes it into core.
Agree with the other points on the focus on Go vs functionality.