A good Content Management system must have some sort of publishing pipeline concept. JustWebsite.eu can't be different here. The "simple websites" principle mainly relates to what this project offers: a good way of making simple websites. Good means, editors must feel they control the entire editing process.

Hence, say hello to first feature in this direction.

Deployments

UI is, as usual, still unpolished, and the concept took ages, but it works, is simple and relatively easy to understant.

Technicalities

Before this concept went live, under the hood, there was a simple collection of pages that kept components. Easy as is. You save a page, page renders on your website.

In order to make this somewhat architectually sound, in the end, it settled on making entire copies of all pages under a special deployment entry.

So, long story short, when you click "deploy", the CMS creates new deployment for that website, copies entire pages entries of that website over to deploymentPages and switches the current deployment to that newly created one, essentially publishing whatever was in the pages collection.

It ain't perfect, we still need some published vs draft states of the pages itself to reach a full nirvana, but it's already something.

The impact

When I wrote last blog post, I had to write it all, save (publish) and see how it work.

This time, I can write it, save, preview how it actually looks like on my website, and then when I will be happy with what I did, I'll deploy that entire thing to you and brag about it on Mastodon.

One last thing

Speaking of Mastodon… if you would like to be invited to a private beta (early birds) once this project matures enough, sign up to a waitlist with your email giving a code that you will find on a pinned post on my Mastodon. Invite codes are a must-have, otherwise I'd get tons of malicious sign ups with emails of real people who never did that (bots sending garbage).

Cheers!