When you describe this as a CMS, I compare it to systems like Wordpress or Drupal. I realize you're selling this as a developer-friendly CMS. But seems like this is a developer-only CMS. How would a non-developer use this system to manage content?
Webiny is a CMS that allows you to build pages, similar like any other CMS. But the unique thing about Webiny is that it's designed to run inside a serverless environment like Lambda, plus the fact it uses ReactJs, Node and GraphQL.
Webiny is aimed at developers, but we do also offer a managed hosted version, which any non-developer can use, as you don't need to install of configure anything. Just follow the get started link on our homepage.
In case you try it out and have any feedback to share - I would love to hear it, since we are a new project launched just few weeks back.
Building pages is different than managing the content. That's the CM in CMS. You've built a page builder not a CMS.
There is one recommendation I'd like to make however. In the README, it might be nice to display some sample configuration and/or possibly a diagram explaining how all the pieces fit together. I'm most interested in learning how to get started with Webiny and what are the various cloud things I'll need to configure to get an operating system.
In terms of getting started as in installing the and configuring the required dependencies locally, we have a get started tutorial https://docs.webiny.com/docs/developer-tutorials/local-setup. In case you don't wanna bother installing all that locally, you can just click the get started button on our website, and register for a managed hosting option - which is currently free during our beta period => https://www.webiny.com/pricing/
The readme on github is just a short summary, but it points you to the docs portal for more info. Since it wasn't clear to you, others might be also bit lost there, so it's something we might need to review :)
I actually wrote my own CMS for GitHub Pages .
By serverless they mean they use AWS Lambda:
> API layer works as a Lambda function with Apollo-Server handling all the GraphQL-related stuff.
1) Many web sites can logically be built using a static site generator (e.g. Gatsby), from content managed some other way.
2) There are great headless CMS out there (e.g. Strapi), but it seems silly to keep a virtual server running a CMS all the time, when you're probably editing content only 1% of the time.
Scaling lambdas is so much faster when compared to an auto scaling zone.
Strapi is a headless CMS - meaning there is no presentation layer where you can view your content. You just get a JSON back. Webiny comes with a visual page builder, as well as a presentation layer. At this moment Webiny doesn't have a headless module - but that's something we are working on.
Keystone is more a web framework with a base set of modules, so I would say it's similar to Webiny. However Webiny is designed and built from ground up to run inside a serverless environment.
Webiny uses MongoDB, for the manage hosted versions, we actually run on AWS DocumentDB.
Hope this answers your question.