Replies: 2 comments 1 reply
-
Hey 👋 Feature requests usually live in the |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks, didn't see that 👍 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Blueprints can be used to add different types of entries in the pages collection. These blueprints let you define a template and fields that differ from the default page.
I'm proposing to add some fields or yaml properties to limit page creation and position.
max_num
andmax_num_per_parent
This limit should let you set a maximum number of pages with that blueprint that can be added in the pages tree or under a specific parent.
For example:
max_num
of 1, since it should be added only once.max_num_per_parent
of 1, since there could be only one addendum per service.After that it should no longer be visible in the create new entry and add child entry menus.
parent_types
andchild_types
This limit should let you set child blueprint types and parent blueprint types.
For example:
child_types: []
parent_types: ['service']
child_types: []
parent_types: ['!folder']
child_types: ['!folder']
This should remove the options in the "create new entry" if the blueprint type cannot be added under the root entry, and from the "add child entry" menu if the blueprint doesn't support that kind of parent or if the parent doesn't support that kind of child.
This should also limit drag and drop of the entries with these blueprint in the tree view.
Beta Was this translation helpful? Give feedback.
All reactions