Five-level nesting cap in Sulu content node tree

Sulu's content node tree enforces a maximum nesting depth of five levels, with the admin interface reportedly silencing any nodes placed beyond this boundary. Authors constructing deep category hierarchies may find deeper levels omitted from the tree without explicit notification, raising questions about whether this constitutes a hard constraint, a configurable threshold, or an undocumented behavior.

The configuration key max_depth in config/sulu/content.yml is referenced in the codebase, yet its exact interaction with the admin UI and published content remains ambiguous. It is unclear whether increasing the value is supported, whether truncated nodes are merely hidden or cause rendering issues downstream, and whether multi-language installations experience consistent enforcement across locales.

• Can the max_depth limit be adjusted through configuration without adverse effects on the admin interface or published pages?
• Does the truncation affect only the tree display or also the availability of child nodes in queries and routing?
• Are there recommended patterns for organizing content that exceeds five hierarchical levels within Sulu's data model?