Hi,

I am proposing radical changes.

First of all the core principle is "Moving Forward", a radical shift from granularly making nit picking changes as that current path is leading to Squarespace, Wix and Shopify taking even more of the market.

The other core principle is that everything should be aimed at the core client and consumer, the average Joe, not the geek/coder/developer. The end goal is to make more regular people using the CMS, not geeking the geeks to use the product in a geeky way.

Branding

Changing of WordPress.org to Gutenberg and leaving WordPress.com to be the only "WordPress". The Gutenberg itself to be renamed to Gutenberg Editor.

For years people are getting confused between .org and .com. I am talking about the average user. That confusion is still not solved to day. That requires the step necessary to change that.

WordPress.org Web site

The website should be radically transformer in an Apple style of simplicity in order for the most important things to be more prominent and to increase the desired action.

No more third party stuff all over the place and confusing navigation. Clear top navigation of the new Gutenberg.com or whatever the domain would be that aims to provide clear Download, clear "Features", clear Block, Plugin & Theme directory.

Gutenberg.com should feature refactored legal pages with privacy policy that is aligned with the laws of First World countries, including the EU with user-friendly human-centric documentation.

Gutenberg.org should be simple and use the current version of the current default theme of the CMS. What more better advertising than using your own theme?

Heavy utilization of white-space just like the Gutenberg Editor in order to provide a conformist branding look that is cross service.

Development

Clear separation of Blocks and Plugins. A prominent equal level style of presentation of plugins, blocks and themes.

Blocks would be the new default way to enrich your content, while plugins remain a more system level stuff that is more like behind-the-scenes enhancement.

Blocks are separate from plugins and don't clutter your database with additional junk like the current method.

Apple-style of App Store management of the Gutenberg Store - the new place for blocks, plugins and themes. A special internal handle of in-store purchases so that the plugin/theme/block developers don't have to have a third party payment processor etc. A small flat fee of 10% with 0% on the free item is a reasonable way of dealing with the infrastructure costs.

People should feel more secure to purchase things from the Gutenberg Store rather than going to a third party website and handle things there.

Rigurouse clean up of the junk that was collected through the years on unmaintained plugins and themes, that are still in the repository for some reason. These should be deleted in order for the most important ones to shine.

Gutenberg Editor

Heavy emphasis on making it a real drag 'n' drop WYSIWYG editor using well known workflows, UI and UX from other well known text editors and mail clients. Anyway who was familiar with Microsoft Word, OpenOffice, Google Docs and a regular email client, should feel comfortable using the Gutenberg Editor.

The Gutenberg Editor should take into account that people use different devices, including wide screen displays, desktops, touch enabled laptops and 2-in-1s, mouses, not just trackpads and make the interface in accordance to that.

Again, the editor should be tailored at the average consumer and the average Joe, not just to geeks/coders/devs using laptops with small screen and trackpads.

Google Docs are a perfect example of how one text editor could work well on wide screen displays on devices with mouses and on touch enabled laptops.

Complete overhaul of the way all the quirky ways of the UX and the UI, which are unfamiliar with other services and software, I am talking about things like page velocity scroll on drag and drop etc.

Centering the idea that a good WYSIWYG editor is a drag and drop editor, not a 6-click editor to accomplish something simple.

Gutenberg Editor - Two Separate Modes

One mode for building a page, this is suitable for primarily static 20-30 page sites of small businesses.

Text mode editor - this is suitable for news, magazine and blog style sites that need to constantly have fresh new content and are in a stage where the core design and layout of the site was already build. Now it is time of the content producer to produce regularly fresh new content, not to handle block customizations and layout changes.

Performance & Security

The WordPress database become like a Windows registry, as soon as you uninstall a plugin, you have that massive amount of data cluttering up the database just like a Windows registry.

This must stop now. Embrace a core-level way of monitoring of what happens throw the install and handle the uninstall on a core level. Two places to put the clutter in the database - settings and temporary items. Upon uninstall request the user if he wants to save the settings or completely uninstall the plugin. This must be handled on a core level, plugin devs won't respect a guideline.

That would save tons of people from blaming WordPress / Gutenberg of being slow and even accusing their hostings for that.

Same should happen on a file level. Completely isolating the WP core from the user side of installed blocks, plugins and themes. These must be separate. One should be read-only image-like within its own directory and the rest should be separated in a better way than the current. Some hostings are already implementing such structure on their own.

That would potentially have a huge security impact.

Introducing of iFrame lazy load as Chromium now supports that as well.

Admin Area

2FA built-in with a companion phone app.

Customization of the branding of the admin area and the colors of the admin area with custom hex codes.

New modern style home screen focusing on the important stuff and not the clutter.

A strict new enforced place and the only place where Plugins could put stuff - A-Z ordered single menu per plugin inside Plugins. No other place, no root menu level etc could be populated with plugins. This must be restricted from the core.

Core level management of the top menu items if you want to enable or disable a shortcut there for clearing cache and others.

Notifications basked like what we have in Windows, MacOS, Linux/BSD, Android, iOS, ChromeOS etc. One place to manage them all. Restricted on a core level, so no plugin, block or theme devs could circumvent this. Silencing of these notifications and nagging screens just like in any OS.

Privacy

Core level control of the data that's being processed from a plugin. No more sending of private data and strict control as iOS style of privacy control.

Dev Handeling

Stop pretending that everything is open and democratic. Yes, it is open, but 90% of the staff that is working on this is Automattic employees, do not hide this, embrace it. Hire more people.

Simplify hierarchy.

Embrace one single place for all tickets. Clean up the ever growing WordPress track system. As much as it grows, the harder is to see the real issues. Some are not even relevant as being associated with something ancient. Going through rigorous filtering, merging and closing so that the open ones become less and less and not more and more.

More staff, more people and more effort on clearing tickets for the Gutenberg Editor and the core. We need to push and move forward.

Yes, we'll lose many devs doing all this, but yes, the platform would become much stronger.

Human progress is not build throw evolution, but throw revolutions. A huge leap forward is always built throw revolution - e.g. making something completely new and moving faster, not throw nit picking small issues and fixing them just to count a ticket number for the new version.