Support permissions for guides / manuals & Table of Contents

[LukeTowers]

We should support documentation to be locked behind permissions, both on the overall guides / manuals as well as on the individual permissions.

This will make it a lot easier for developers to automatically scope the content that is presented to the end user because they can reuse the same permissions that any given functionality is locked behind in order to block access to the documentation for that functionality; thus ensuring that users without access to do a given action won't have to see the documentation for something they cannot themselves do. We can also make this system optional by way of a winter.docs.view_all permission that can bypass any permissions set on the documentation content if desired.

[bennothommo]

This is kinda sorta already in place with the documentation types - the intention is that there will be permissions to limit accounts to a certain type of documentation. For example, a developer may want access to all types, but the client should only see the "user" documentation, not any technical documentation.

But your idea sounds cool too. :)