- Issue created by @_doyle_
- 🇨🇭Switzerland berdir Switzerland
entity.path_alias.collection is in core, not in pathauto.
pathauto patterns are config entities, so views is not an option. Not sure if it really makes sense to replicate the full functionality in a dashboard, because it needs quite a bit of UI space to show the patterns, what they apply to and so on. Some kind of summary/suggestions block might make more sense? (like, X patterns, things without pattern found, but that likely requires some hardcoded assumptions).
- 🇺🇸United States _doyle_
Thanks for the feedback! Let me remove the path_alias collection from the request.
From a user point of view, especially users coming from other CMS's having insight into Pathauto patterns is really important. They work differently in other CMS's and Drupal actually has a lot of power. Exposing the initially configured Drupal CMS patterns would be very useful contextual information for this dashboard, but I fully understand the size constraints. I don't think the full functionality should be there as you, we can link back to the main URL to manage them.
What do you think about an informational block for Automated URL Patterns.
1. Title: Automated URL Patterns
2. Description: Automated Path Settings provide a powerful way to control the structure of URLs across your Drupal site, ensuring they are both user-friendly and optimized for search engines. This feature automatically generates URL aliases based on customizable patterns, reducing the manual effort required to manage URLs and helping to maintain consistency across the site.
3. Pattern Name | Pattern | Type
4. Add a CTA link at the bottom to "Configure Your URL Patterns"This gives content editors/site builders the understand that this is here, its easy to use and configure without having to "know".