I'm writing a space blueprint module where the page hierarchy that it create is defined by user input on the wizard. I can't find any information on how to achieve this, all the documentation I've seen create a static hierarchy from nested <content-template> tags in the <space-blueprint> tag.
Is it possible to provide this <content-template> structure programmatically?
Community moderators have prevented the ability to post new answers.
For example, in this module descriptor from https://developer.atlassian.com/confdev/confluence-plugin-guide/confluence-plugin-module-types/space-blueprint-module <space-blueprint key="my-space-blueprint" i18n-name-key="confluence.hello.space.blueprint.name"> <content-template ref="hierarchy-blueprint-content-template"> <content-template ref="hierarchy-child-a-content-template"/> <content-template ref="hierarchy-child-b-content-template"/> </content-template> <dialog-wizard key="my-space-blueprint-wizard"> <dialog-page id="spaceBasicDetailsId" template-key="Confluence.Templates.Blueprints.CreateSpace.createSpaceForm" title-key="confluence.hello.blueprint.dialog.choose.title" description-header-key="confluence.hello.blueprint.dialog.choose.heading" description-content-key="confluence.hello.blueprint.dialog.choose.description"/> </dialog-wizard> </space-blueprint> The 3 <content-template> define a structure of one page with 2 child pages nested below. I do not know in advance what the structure will be, that is known only at run-time during the wizard. Using the Space Blueprint API, can I provide this structure at run-time?
Can I ask what you mean by "Is it possible to provide this <content-template> structure programmatically"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.