- Issue created by @ressa
- 🇺🇸United States drumm NY, US
For the modern version of the site, we are not using OG for this. Instead just a straightforward entity reference to the parent guide, and building customization around that.
I agree we should consider merging the content types into just documentation pages. There isn’t much practical difference between the two content types. And any amount of planning guide hierarchy upfront will still want guide/page switches as the content evolves over time.
This is not something we could do in D7, the OG Menu setup is already not scaling well. One menu per page would not be workable.
- 🇩🇰Denmark ressa Copenhagen
Thanks for a fast reply, explaining the future plans for the documentation @drumm.
I do hope the "add to menu" permissions will be relaxed in the new system, so that ordinary users can create, publish and add them to the menu, to prevent new pages to stay semi-hidden. As I see it, weeding out occasional spam in the documentation is a smaller task, compared to the damage of great, new documentation pages in limbo.
Since there is a plan for a simplification, there's nothing more to do here, so closing.