[WimLeers]

https://raw.githubusercontent.com/relax/relax/gh-pages/asset... shows the key features are WYSIWYG-style building of entire HTML pages.

This is not a Content Management System, but a Page Management System. A CMS works with structured content and the relations between those pieces of structured content. It allows you to model the data it needs to store, receive (forms) and render. So you can then reuse, combine and display that data in any way you need.

(Many projects/people conflate "page builder" with "CMS".)

That being said, this looks very nice :) There totally are use cases for an easy-to-use page builder :)

[andybak]

> Many projects/people conflate "page builder" with "CMS"

That's because there's no clear bright line between the two. I've created systems that lie on many points between these two extremes.

Sometimes the page metaphor is as simple as it sounds. Sometimes pages pull in structured content or are placeholders for a subtree of structured content. Sometimes the page structure plus metadata IS the structured content.

[WimLeers]

True, there's not always a clear distinction.

But giving lots of WYSIWYG-esque options to the content creator is a sure way to end up with unstructured content that cannot be reused, because it's got so much garbage HTML in it, and so few semantics.

[bruno12mota]

Relax actually acts as a complete cms, it is not just a page builder, check our schema feature. You can even create templates for the schemas you create on the page builder and link data to components with drag and drop :)

[WimLeers]

Could you add screenshots for that too?

Sounds interesting! :)

[bruno12mota]

Will do after the refactoring I'm doing now to use GraphQL with Relay and React 0.14, will take a few days but will definitely raise the bar