An operating system for web applications.
Declare your applications in YAML. You get a console shell — windows, files, users, permissions — plus the backend that serves them and the public site that renders them.
One blueprint compiles into three things: the admin console, the backend's data contract, and the public site's read schema. Change the model once and all three follow.
| framework | The frontend — a library of de-* web components and the console shell that composes them into apps. No UI framework, no build-time template language. Also home to the blueprint compiler. |
| api-node | The Node backend — console and public API, plus an image processor. Agnostic to any one project: everything a project is arrives through a single seam. |
| api-php | A planned PHP backend. Same contract, same blueprint output, different runtime. |
| demo | The live reference project — console, public site, API and sign-in, all from one blueprint. |
Because the problems are the same ones. Applications need a shell to run in, windows to live in, a filesystem, users and permissions, settings, and a way to extend them. So that is what is there — and an application is a declaration, not a codebase.
It is not limited to content. The reference project runs a website, a ticketed event, orders and transactions, user administration and file management through one model.
In active development. The repositories are private for now.
Built by Paul Smiechowicz — paul@designofadecade.com
