CMS 3.0 looks much cleaner visually, but some of the workflow changes feel like a step backwards from a UX perspective.

Previously, import/export actions were easy to access directly from the CMS interface. You could go into the CMS, use the relevant plugin, and import or export content from the same place where you manage your collections.

That workflow made sense because import/export is a CMS management task. It belongs in the CMS backend, close to the collections and content it affects.

In the new workflow, you have to leave the CMS, return to the main canvas, search for the plugin, select the correct collection, and then run the import/export action. That adds unnecessary steps and makes a simple backend task feel disconnected from the CMS itself.

The same applies to rich text editing.

Being able to edit rich text live on the canvas is a great feature, and I can see why it was added. But removing the ability to properly edit rich text fields directly inside the CMS feels like a downgrade. Both workflows serve different use cases.

For quick content management, bulk updates, structured editing, and working through multiple CMS items, editing directly inside the CMS is much faster and more logical. Canvas editing is useful for visual context, but it should be an additional option, not the only practical way to edit rich text content.

Suggested improvement:

Bring key CMS actions back into the CMS interface, including:

* import/export plugin access from inside CMS collections

* full rich text editing inside CMS items

* canvas editing as an optional visual editing workflow

The issue is not the visual update. The new CMS looks good. The problem is that core content management actions now require more context switching, more clicks, and a less intuitive workflow than before.