Content Editing XP

We are currently working on a brand new version of Strapi including two exciting new features: Draft & Publish — Write a draft version of your content parallel to the published one. Content History — See the previous versions of your content and roll back if needed.

Allow users to manage content by having a published and draft content at the same time.

We want to update the interface to be able to nest more than 2 levels of components in the administration panel. This feature is supported if you update your Content-Types schemas manually. We want to ease everyone's life by supporting this natively from the UI. -- Original post: Currently while building websites with Strapi as a back-end it annoys us as developers that we cannot use more than 2 levels deep of nesting components in the newer versions of Strapi. Take for example a Hero component including a set of cards, and a set of cards also includes buttons which link to different sections in your website. This is simply not possible with newer versions in Strapi. See: https://github.com/strapi/strapi/issues/11319

The current date/time picker does not allow keyboard input or copy and paste of the date/time (even when properly formatted) https://design-system-git-main-strapijs.vercel.app/?path=/story/design-system-components-v2-simplemenu--with-iconbutton It would be handy to have a date range, however this feature is perhaps more related to type suggestions for custom fields

see: https://github.com/strapi/strapi/issues/2166

Track version history of content: view the different iterations of a piece of content.

Manage your content review process Stay aligned and collaborate better with review workflows. A convenient way to coordinate work seamlessly across teams — from first draft all the way to publication. ✅ Fully customizable review stages Different content requires different processes. Build custom flows to review and validate the content through various stages, whether it’s an extensive 8-step legal review or a simple 3-step editorial process. ✅ Assign teammates Give review stages a clear owner, so everyone knows who’s responsible and you keep the content flowing across the content lifecycle. ✅ Support for Webhooks Automate various actions triggered by stage changes, such as updating external systems or notifying stakeholders. Say goodbye to manual processes and hello to efficiency! ✅ Manage user permissions for specific review workflows Integrated with the roles and permissions system, you can easily tailor permissions to the specific roles of your team members, giving them precisely the level of access they require at every stage of the workflow. ✅ Create multiple workflows Design and manage multiple content approval processes. Whether you require a multi-stage review process or different workflows for different content types, we've got you covered! 🔜 Next up, we’ll introduce Role-Base Access Control for individual stages — to give you full control at every level! With this feature, you can go a step further and easily tailor permissions for the specific roles of your team members at each review stage.

In 4.5.5, FontAwesome was removed from the codebase. This mean we can no longer use FA Icons for our components. This is a request to reinstate a mechanism to add icons to components, since it gave a lot of visual benefits for the content editors.

Summary The current and previous (v3) WYSIWYG editor are more so basic markdown editors and while markdown is awesome (since I'm writing this feature request in markdown smile ) I believe there is room for improvement and we could swap the default editor shipped with Strapi for something more feature rich and complete. There is already community options in both v3 and v4 such as CKEditor 5, React MD, Toast UI, and Editor.js I do think we should ship something more feature complete then forcing everyone to install one of the community options. If anything we could also make it easier to swap out our editor by standardizing methods to build new editors into the Strapi interface. Why is it needed? Our current editor only supports the bare minimums in terms of markdown support (eg no tables, ect) and support for things like inline youtube video previews, ect are a bit more complex to handle properly. Likewise not all non-technical content editors are familiar or like markdown. Likewise in many frontend frameworks a library is required to convert markdown to html. I believe it could be possible to handle this type of conversion server side and maybe caching those outputs (or pregenerating them). see: https://github.com/strapi/strapi/issues/12440

We are excited to announce our upcoming Releases feature. Set to debut by the end of Q4 2023, this feature is designed for our Enterprise users. It will allow them to group multiple content entries together, regardless of their content type or locale, into a single cohesive release for a more organized and coordinated rollout. Whether you're aiming to publish a new article, unpublish an outdated post, or roll out changes – everything can be orchestrated within the same release. This ensures a more harmonized, cross-platform content update, elevating the consistency and precision of your deployments. And there's more! By the end of Q1 2024, we'll be enhancing Releases with a scheduling layer, giving you the power to pre-set your content deployments. Say goodbye to manual interventions and streamline your content publishing workflow like never before!