I want to make this live on production for a certain group of users.
I know that the pattern library can affect the site it's on because you can execute Python from templates so it's a security risk. Documentation could state that and this could be an opt-in only.
Describe the solution you'd like
Create a custom Django permission to restrict who can see the pattern library as part of the package.
Add Wagtail hooks for permission and maybe a Wagtail menu item for the pattern library as well. Probably a separate issue but would follow from this as we'd first want to restrict access.
Describe alternatives you've considered
Creating a permission decorator in my own project and guarding the URL paths.
Is your proposal related to a problem?
I want to make this live on production for a certain group of users.
I know that the pattern library can affect the site it's on because you can execute Python from templates so it's a security risk. Documentation could state that and this could be an opt-in only.
Describe the solution you'd like
Describe alternatives you've considered