How do I do document versioning using Spacecraft ?
Asked by Vasudha_bhakri:

How can we do versioning while using Spacecraft?  
How can we use scroll documents and Spacecraft at a time?


Answers:
author: Laura Campbell _Seibert Media_
body: Hi [@Vasudha_bhakri](/t5/user/viewprofilepage/user-id/5329231) , the Spacecraft team would love to learn more about your needs for versioning. Please [book a call with the Product Mange](https://calendly.com/spacecraft-app)r so we can take a closer look at your use case.

comments: author: Vasudha_bhakri
body: Our case is very specific per-say.  
Within one space that we are using, we have documented our APIs.   
We wanted to give our users a way to do a hands-on with them. For the same we tried using "Swagger Macro for Confluence" in a Viewport Published page, which did not work.   

So, we are looking for an alternate method to make this work using any other publishing mechanism which can also include versioning.   

Since our problem is very simple....  

1. Scrollviewport has versioning but does not support "Swagger Macro for Confluence".

2. Spacecraft has support for "Swagger Macro for Confluence" but does not support Versioning.  

What we are looking for is an amalgamation of all 3 things.


author: Kristian Klima
body: Hi [@Vasudha_bhakri](/t5/user/viewprofilepage/user-id/5329231)

a) Thanks for bringing Spacecraft to my attention :)

b) I can't imagine it would work unless you find a way how to create a space out of a version created by Scroll Documents and use that space to feed Spacecraft. But that would create another site.

Spacecraft, like Refined, seems to be working directly with your Confluence content and permissions and is thus limited in what it can do.

If you want to take the advantage of versioning within Scroll Documents, you have to use Scroll Viewport which has the direct support for Scroll Docs versioning built right in (it's the K15t's ecosystem).

<https://help.k15t.com/scroll-docs/3.16/server/> - see the two switchers in the top right corner. One is for versions, the other for variants (conditional content).

The added benefit of Viewport is that it can create doc sites even from Confluence spaces that are not public. It builds the site away from Confluence.

Disclaimer: I'm not working for K15t but I am using their apps.

comments: author: Vasudha_bhakri
body: Thanks for the prompt reply.   

I have another question.   
How can I use something like "Swagger Macro for Confluence" in a Viewport Published page and make it work?   

As far as I have tried it seems it is not supported. I mean after adding the Macro to the page and publishing it through Viewport, the output is a blank page, with just the Heading.   

Is there an override? If not then anything other than this Macro, which allows similar functionality to test and hands-on APIs.?


author: Marc - Devoteam
body: Hi [@Vasudha_bhakri](/t5/user/viewprofilepage/user-id/5329231)

Macro's from different 3rd party developers most likely won't work together as that is not why the developer build them, but from their perspective to add extra functionality to the Confluence product

You could reach out to both developers and see if there are options to integrate, but that would give them dependencies on each other in developing their product.

We can't assume in any way that it is just possible to combine any functionality from any app vendor.


author: Kristian Klima
body: [@Vasudha_bhakri](/t5/user/viewprofilepage/user-id/5329231) - about that Swagger

Viewport supports OpenApi

<https://help.k15t.com/scroll-viewport/api-references>

<https://goodsoftware.k15t.dev/wiseapp-for-developers/v3/api-reference#id-(v3)WADAPIReference-APISpecification>


author: Vasudha_bhakri
body: [@Kristian Klima](/t5/user/viewprofilepage/user-id/5074962) Sure. We would try it. And hope it works the way we want it to. Will keep you posted.


Tags: cloud

confluence-cloud