Content blocks with role-based visibility or page-to-page relationships

Outline already works well for organizing documentation by collections, pages, and permissions, but some documentation needs go a step further: different audiences may need different levels of detail within the same topic structure. For example, a documentation set may need to stay organized by the same category tree while still offering different layers of information for different readers. In one use case, that could mean keeping a single canonical page structure while adding extra details for support teams, engineering notes for technical readers, or age-sensitive content for specific audiences. But this pattern could also apply to many other scenarios where content needs to be shared, adapted, or hidden depending on the reader's role or context. What would help It would be valuable to support one or more of the following: • Content blocks with role-based visibility within a page. • Stronger page-to-page relationships than simple inline links. The c…