Sorry to be "the guy", but what unique thing does this do? I see that you build a page by linking nodes together. That is about all I could glean by scrubbing the 45 min talk.
On the CMS side, the page rendering process is a graph traversal and thus very fast (just a couple of milliseconds), and Structr doesn't need any caching of intermediate results during page assembly, so it can render protected/private pages as fast as public ones.
And you can create mobile backends and web apps in minutes, using the schema editor to define a custom data model.
The screencast is based on a talk I gave at NoSQL matters in Cologne this year. I know we need to add better videos, but we're just hackers. Will do our best.
This is great. I was just looking at building a conceptually similar backend on Neo4j. You guys have saved me months of work and have allowed me to jump into the meat of the project.
One issue: subscribing to your newsletter takes me to a page with a message in German -- not an error, it's just telling me to click a link in my email, but presumably not the language intended given the site is in English?
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.
Seems like it's trying to do too much. Webdav/CMIS feels dated, let alone for a roadmap. Widget exchange can require a huge community to be worth the effort. However, the performance and data binding really stand out and could have huge value.
Thanks! Structr is actually much more than a CMS; it has evolved into a Rapid Application Development Platform with a visual schema editor and an integrated JSON/REST server, so it can even be used for database-as-a-service projects etc.
It looks like it is open source, but I feel that the structr.org website should talk more about the open source project, and a structr.com website should focus on the business. Right now, looking at structr.org, I don't see anything about the open source project. It just looks like a sales pitch to me.
It is open source, and we changed the frontpage to make it more clear.
Regarding structr.org/structr.com, I agree. We will make structr.com the commercial site in the future while turning structr.org into a site for the community.
And on the sales pitch: It's somewhat intended as we need some commercial customers from time to time, not being backed by big investors.
