Define and establish best-practice CE naming pattern

This would be a breaking change for existing Nuxt projects. One would have to move components in Nuxt projects in a sub-folder "Drupal" or write additional component config in nuxt config file or have prefixed component names with "Drupal". It adds another layer to think about when developing frontend, I don't like that.

What I'm doing right now in a Nuxt 3 project is, I put all drupal custom-elements in a subfolder "global". That way the components are grouped and are global (Dynamic Components) without the need for additional components config and can be rendered with Vue Render Function API (nuxtjs-drupal-ce renderCustomElements helper uses it). Other components, that are not rendered with Vue Render Function API, don't need to be global.

yes, existing projects would have to follow, but only once the new naming pattern is adopted. with CE-UI configuration projects should be able to use whatever naming patterns are desired. still, we should define good defaults.

Adding some proposal. I think it's not necessary to prefix all content entities with "drupal-" - that makes things to verbose and content-entities names are just a hand-full in Drupal sites, so those would be known and associated with drupal entities easy enough. The drupal- prefix would be there and used for everything which is not an entity, thus more drupally.

Added related 📌 Make providing customized CEs easy Active

This will be part of CE-3.x - see 🐛 drupal prefix is added to configured custom element names Active

This is done. So what's missing is changing the remaining custom-element names to follow this pattern:

drupal-markup: DONE
drupal-layout-section -> drupal-layout (it's not a section in drupal speak so let's not invent that here)
drupal-form-FORM_ID
drupal-view-VIEW_NAME

📌 Rename layout-section element to drupal-layout Fixed was done in CE version 3.

implemented and tested changes for both forms and views.

the change is trivial, but for views its a backwards compatibility breaking change for existing frontends. It's easy to account for, but still something people will run into. so let's create a change record. Also it would be nice to be able to configure the custom element name in a view. Added issue.

fago → closed merge request !93

change record + feature-request created, remaining MRs merged - thus all done!

Automatically closed - issue fixed for 2 weeks with no activity.