You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We want to create a new Space Blueprint on a Confluence Cloud instance.
Currently all we can do is disable different Space Blueprints.
I've looked at the community and found some posts, but most answers are either for Atlassian Server, for using existing Space Blueprints, or for making Page Blueprints.
The closest we have in Confluence Cloud to the space blueprint functionality in Confluence server is Multi-page blueprints with Confluence Connect. Please note that page and space blueprints for Confluence are plugins and require development skills to produce.
We had a suggestion open to include the ability to create space blueprints in Confluence Cloud, but it was closed as "won't fix". You can read the explanation from the development team on: Support creating space blueprints in Connect
Hi @AnnWorley, I went through the Multi-page blueprints tutorial, but when I tried going through it just by following the instructions, running npm start caused an error in one of the dependencies. I also looked at the repository that the tutorial is based off of, and the code is over two years old at this point.
Furthermore, I went and modified some of the dependencies in the package.json and updated the app.js file to use the correct instantiation for the middleware when using a higher version of Express. When I did this, I was able to at least install the plugin, but noticed that it would hook into the job that was running on my computer. As a result, if I stopped the process running the npm job, the plugin would no longer work. Even when I restarted it, it would look for the old hook, and the job that I restarted would be using a different hash as an identifier.