The most interesting Computer Science problem I've ever encountered 🤯

[@keithwjones]

The project marches on, watch this space. It will happen.

[@TheMaartian]

In for a penny, in for a pound! 👍

[@ikemkrueger]

That would lead to a lot of custom admin panels. And for each admin panel you need a custom documentation.

[@TheRealPearsonified]

While that's theoretically possible, it's not how the ecosystem will end up working (and precisely for the reasons you mentioned). It's untenable to have a bunch of different admin panels working in different ways; as a result, 99% of people will use the default admin. But this also misses the real magic. Each Theme can be "skinned" to look different, without modifying templates or affecting underlying display behaviors. This will end up being the go-to for people who want to modify the admin beyond the built-in customization capabilities. In addition, if you've used Thesis or Focus in the past 12 years, then you're familiar with Display Options, which can be used to modify what appears in a Theme without modifying templates directly. Bottom line: While your concern is legitimate, there are lots of other options within the system to avoid the undesirable outcomes you've mentioned.

[@Slyndc]

To be clear, this new project will not require Wordpress to be installed correct ?

[@TheRealPearsonified]

Correct, the entire point of this project is to leave WordPress behind. (But really, it's just about moving to something that's built the right way, works better, is easier to use, and serves pages faster.)