Teams often mix draft content and production content in the same space because it is convenient early on. The result is messy navigation, unclear ownership, and risky publishing behavior.
A better approach is to separate documentation by environment or workspace. Keep authoring and review work in draft or dev, then promote content into a production workspace when it is ready.
The value is not just cleanliness. It makes role-based access, review gates, and post-release monitoring much easier to reason about.