- 🇳🇿New Zealand quietone
The Ideas project is being deprecated. This issue is moved to the Drupal project. Check that the selected component is correct. Also, add the relevant tags, especially any 'needs manager review' tags.
This originally came from a discussion [years ago] on this issue #252846: Add XML Sitemap to Core → , the original discussion on that issue no longer seems to be relevant but the ideas it spawned here are. Those relevant ideas are:
It would be the goal of something like a "structure.module" or "relationships.module" to manage and maintain the different kinds of relations between Entities (mainly Nodes). If the relations are hierarchical, they could be offered to something like "book.module" that handles displaying the structure to users.
This new mechanism would not be a subset of Menu, Taxonomy, Books or another Core Module since this API and the relations it establishes would have to be more low-level and not specific to one modules data structure or workflow, as well as providing the ability to *all* content a Drupal site consists of so that moules like Menu, Taxonomy and Books could be based on this API.
Drupal Core does not know much about the relations of content in a Drupal site; some "connections" are created through taxonomy, others through the menu and book modules. Also, there is a plethora of contributed modules trying to add this information about parent-child-relations, etc.. All those modules try to solve similar problems and to generate similar data, thus multiplying the effort to maintain this knowledge about a site's structure. Additionally, most of those approaches do not make good use of data already available in other modules. When building a site, this can lead to unnecessary complex site structures with different navigation themes, different hierarchies, performance issues, etc. We all know these problems. That's the reason, why a solution in Core is needed.
Many contributed modules try to add knowlede about a Site to Drupal; some examples:
There are many more modules with similar requirements.
These modules have completely different goals, and different "targets":
IMHO it's as simple as this: Drupal is a framework offering an infrastructure to build intelligent websites. Knowledge about structural relations between nodes is such an infrastructure.
I'm searching for quite some time for solutions to the described problems; so far, I only discovered approaches targeting parts of it. This feature request is intended to
[Thanks & Greetings, -asb]
Active
11.0 🔥
entity system
It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The Ideas project is being deprecated. This issue is moved to the Drupal project. Check that the selected component is correct. Also, add the relevant tags, especially any 'needs manager review' tags.