I wonder if it would make sense to package a kind of "standard" version of the app, with the most-used / most important extensions, content types and whatever configured, as a Sandstorm [0] app. That way you could even make the "needs to by set up by a programmer" part optional, and target a larger user base. And you'd have a demo instance right away! [1]
It wasn't absolutely clear to me what this is. The front page (project page) doesn't have a simple, clear description of the application. Or is it a "platform"?
Documentation page has a list of features - but they are all quite technical, not end-user helpful in general. The "getting started" page says :
"rapid development of robust and highly performant websites with content management functionality."
Wordpress is mentioned a lot so I assume it is a "blogging" platform to a major degree. A demo site might help but first, a better description I think.
I know this is not directly related but I've been looking at cms design lately and I was wondering what different approaches people have come across to store documents and content in a structured, hierarchical way? And if there is an accepted 'best' way of doing it.
From what I find documents are mostly in a table, and hierarchy is provided by another one, like a `categories` table, in which a `parent_id` column is used to refer to itself and form a tree. It helps a lot to cache that tree, as it usually is often used, not too big, rarely changes, and needs more then one query (mostly).
In Postgress there is the `ltree` extension, but then the solution is Pg specific.
Looks like an interesting project. I'm not entirely sure that you're prioritising the right information though - almost all of the text on your site is about Haskell / the technology stack you're using; but for a CMS, most people care about the admin UI / features and how they simplify the process of managing a website's content.
I think it'd be useful to show some screenshots / examples of how it works, in order to immediately engage potential users, and then lead on to the benefits of using Haskell etc.
Thanks for the feedback. Screenies are in the process of being added. For this CMS we to target programmers, as it needs to be setup by a programmer. Once setup an enduser can manage content on the site; but not change themes, install extensions, or add fields to content types... a programmer is needed for that.
> While this CMS has a very end-user friendly administrator interface (think WordPress), a programmer is required set it up (unlike WordPress which could be set up by non-programmers).
So creating boring and unnecessary jobs for programmers is a good thing, while letting each user install the software by itself is a bad thing?
[0] https://sandstorm.io/
[1] https://blog.sandstorm.io/news/2015-02-06-app-demo.html