Calling this a CMS platform I think is misleading me into wondering what a graph database's use is in something used to "just show content".
It sounds like it's able to do fancy things with rendering pages quickly, but...so what?
The Github explanation says "It was designed to simplify the creation of complex graph database applications" - a generic platform built around a graph database makes more sense.
So my question is - Is this a CMS or a platform for building applications? Is the graph database cool because it can do fancy things for rendering content, or because you can use it to build relationship models for users of applications using Structr for RAD-style dev?
True, it's hard to find the right category for it, so we call it "Data CMS". For some people, the CMS part might just be a nice add-on and the real value is the embedded graph database and the in-graph data model. Many web applications are 80% CRUD-style pages and maybe 20% (complex) queries, so using Structr for the CRUD pages and Neo4j's Cypher for the queries is a perfect fit imho.
It sounds like it's able to do fancy things with rendering pages quickly, but...so what?
The Github explanation says "It was designed to simplify the creation of complex graph database applications" - a generic platform built around a graph database makes more sense.
So my question is - Is this a CMS or a platform for building applications? Is the graph database cool because it can do fancy things for rendering content, or because you can use it to build relationship models for users of applications using Structr for RAD-style dev?