New version questions & thoughts (v4)

Discussions
3

Thanks for the clarification on the question of the connection of the design language and the technical foundation. All Keynote had given me the impression that you’d change the technical aspects and the UI at the same time and call it v4.

My questions around v4 are mostly centered on the integration parts:

Graphql

  • Will the graphql output be the same between v3 and v4 or do you expect many changes there?
  • Do you think it will be possible to disable the graphql Pagination?
  • Do you expect performance improvements for graphql?

Plugins

  • Do you aim for a stable plugin system with v4, or do you consider it a draft?
  • Do you expect live reload / HMR for plugin developers?
  • Since you create a nice way to add custom fields: are you planning on supporting custom fields in the i18n plugin?

Database Layer

  • Do you think about global content-type wide lifecycle hooks? (for plugins like algolia, which want to synchronize content or create revisions of everything …)
  • Do you think you can offer a nice migration path, or do you expect a lot of manual labour?
  • Will it be possible for custom fields to store data in different DB columns or as Database Level data formats? (Storing JSON for example)
  • Are you planning on having validations in the CMS UI?

Design System

  • Do you have some drafts, how the dynamic zones will look like? For our editorial team this is a crucial area and currently very hard to work with, if content pieces become long. I’d be happy to provide some design feedback as soon as you have something there … Main issues are visual hierarchy (find a component with a certain name) and controls (insert a new component anywhere, move components around …)
  • Do you plan on having a spacing system here? Currently plugins need to hard-code a lot of spacings. Would be nice, because it would blur the boundaries of core and plugins.

Apologies if these are too many :slight_smile:

In general from what you have shown already about the new design language I’m very excited. It looks way more modern. Also I really appreciate you are taking a11y serious in the new component library! I’m disappointed that you didn’t use the chance to introduce a responsive UI (which I’d say is mandatory in 2021), but I also see that you need the amount of changes under control …

8 Likes