Hey DN! We created Elemeno because we were sick of fighting with different CMS tools, their templates, plugins, and never ending server maintenance.
With Elemeno you can use your favorite programming language, framework, or library to build your sites and apps. Elemeno is cloud based so there is no software to install, and no servers or databases to maintain.
Take a look and let us know what you think, we would love to hear from you.
So I could have a static site built on jekyll or middleman and you guys could handle all the dynamic content?
Yep you could do that. We have plans to build libraries for some of the more popular static site generators which would make it much easier to build a site like this.
A Grav plugin would be awesome!
Like the first experience. But somehow I'm missing a hierarchy. E.g. I was thinking about creating a simple static page for our internal compay structure. Departments > Teams > Member. And on each level a title, description and a image for example. But somehow I don't see how can accomplish that in Elemeno. Am I missing something?
It's a difficult thing to explain because it's such an abstract thing, we definitely need to find an easier way to explain the differences between our two content models.
Essentially we have two different types of content models, and the only real difference is how many items you can create with that content model:
Singles: Content Model used to create One single item
Collections: Content Model used to create Many items
So for your example you might create:
Content Model Type: Single
Description: Content model used to create a single unique Departments page/screen which lists your various teams.
Content Model Type: Collection
Description: Ability to create many different teams all using the same content model
Content Model Type: Collection
Name: Team Member
Description: Ability to create many different team members all using the same content model
The key ingredient to link all this together is the input that we're calling the "Relationship" input which allows you to include items from another collection in your content items.
For example, your "Teams" content model could have a relationship input which would allow you to include items from the "Team Member" collection. This allows you to create a simple hierarchy like you described.
If you have any other questions, suggestions, or issues please reach out any time, we're more than happy to help any way we can.
Ok, I see where you are going... I'll try it out. Nevertheless as you mention: you need to find an easier way to communicate this. I consider my use case as the most straight forward thing (top page > sub page > sub sub page) and I was not able to figure it out in the first glance :/
Maybe take a look at Kirby2? A file-based CMS... I like their idea of setting up "blueprints" to define what fields are shown when adding a page and then a simple tree-structured admin panel
But you api's are nicer and setup is faaar easier! So continue the good work! :)
Hiya Chris! Elemeno looks great. What separates it, in your mind, from companies like Prismic and Contentful that offer similar products?
Thanks Alec, we really appreciate it.
We've used both Prismic and Contentful in the past and we loved those products but we felt there was room for improvement. We found both the UI and the API for those products frustrating and limiting, especially when other non-technical members of the team were using the product.
We certainly don't have feature parity with either Contentful or Prismic, but we feel our core product is quite robust and much more user friendly. Things like our drag and drop content model creator make it really easy for anyone to define content models. And our API follows RESTful principles which makes it very easy to navigate and use.
We have a long roadmap with lots of exciting features and tools which we will continue to roll out over the coming months. We would love to hear if there is anything you would like to see, we truly value our user's feedback.
Awesome! Love to see products focused on non-technical users in fields that are largely focused on developers. I think headless CMSes have huge potential, and their developer-centric documentation (and interfaces for the most part) is one of the things holding them back.
I was about to check up on Contentful since I have a colleague using that, but now I'll try this out too probably to see which fits me the best. Thanks for sharing!