> So instead of an introduction, I would recommend you to complete the tutorial in the online version of Webcodesk. Click on the link below.
Please put a GIF of your tool in action on your github page instead of this message.
By all means though, embed the video onto the page -- it's at least a start. IMO it's not really reasonable to expect busy devs to sit through 1 minute of silent sped-up introductory content.
Here are some examples of what I mean (I searched "wysiwyg react" and "page builder react" on github and picked some good examples):
I say this only because it seems to be a trend in some software dev circles where people post 15-30 second instructional animated GIFs to demonstrate something. It's incredibly frustrating to watch. If you miss something you're stuck either downloading the GIF into an editor or having to watch the whole thing again.
Blocks is alpha
Grapes is ok, but the repo maintainer is not the greatest
Asking people to upfront invest their time into something without first selling them on that thing is a big no no.
Yes even/especially for tech projects and libraries.
...and I am even this guys target audience, a React developer who makes a living with it.
Your project appears to be generating a static SPA, but if you wanted to consider making this a full-fledged CMS you could look into using gold or something similar.
graphql really shines on the CMS side where your Component schemas practically write the cms UI for you. Your cms UI can leverage introspection to make for a really intuitive and efficient experience - especially considering that your atomic component library will grow very large over time.
I like how you split up component types (atoms, layouts, functions) and nest that under the app component types (pages, templates, flows) Is this done in code or are you using proptypes or some schema to manage the organization?
And I'm thinking of a data modeler  in this way too
[EDIT] I'm talking about situations like "we need an ugly informational page here for an hour" and all or some part of it would look better centered, or if I'm throwing up a placeholder page on a personal site. Those kinds of things, I'm not gonna google "what's the correct 2020 CSS to do what <center> does" and end up with a bunch of caveats and gotchas when I could just <center> and move on with my life.
The best way to tell about Webcodesk is to let you try it in action.
So instead of an introduction, I would recommend you to complete the tutorial in the online version of Webcodesk. Click on the link below.
Or does your company not use any propriety tools at all? (It's alright if they don't; being 100% reliant on permissive open-source licenses is a nice achievement in-and-of-itself).