How can we merge Confluence spaces in cloud with Scroll tools, and embed docs on our site?

Navira Zainab

Hi Community,

We are struggling with managing content across multiple products and service documentation. Right now, we handle each release for each product separately using Scroll Documents and publish them via Scroll Viewport/Scroll Sites.

We now want to merge documentation from different Confluence spaces into a single cloud-based platform to simplify management and deliver a better reader experience with minimum clicks.

Additionally, we’d like to know how we can embed this documentation into our main site so that users don’t have to navigate away or click through multiple layers.

Question:
Using Confluence, Scroll Documents, and Scroll Viewport/Scroll Sites, what are the recommended approaches to:

• Consolidate documentation from multiple spaces into one unified cloud platform
• Manage releases effectively in this setup
• Optimize navigation for readers with minimum clicks
• Embed documentation seamlessly into our main site for a consistent user experience

Kris Klima _K15t_

Hello @Navira Zainab 

There's a lot to unpack there but it's also an intriguing use case  

Disclaimer: After using and deploying Scroll apps as a user for over decade, I joined K15t in September this year.

 

Based on what I know from your message:

You have multiple spaces and scroll documents and you publish them using Scroll Sites. Do you publish all spaces/documents to a single site or multiple sites?

Publishing multiple content sources into a Single Scroll site would meet the goal of creating a single cloud-based platfrom. Scroll Sites would create a Landing Page for the entire site. That landing page would act as an intersection for your specific product sub-sites.

Users would be able to search either thw whole site or the specific products.

You would be still able to handle releases for individual product separately, in line with their respective release cycles, so there'd be no dependencies that would prevent you from publishing Product A because Product B is not ready.

Back in my Emplifi days, I combined Scroll Documents with workflow and space syncing apps to have a more detailed control over the release process (effectively, I could publish any page at any time to any site).

As for embedding your documentation into your main (corporate, I presume) site. Scroll Sites allow you to embed your documentation directly in your product.

We also offer Scroll HTML exporter so you can export your Confluence content and embed it anywhere - but that would have to be done programmatically on your end. Personally, I'm not a fan of putting everything into a single corporate site - typically, accessing and consuming docs requries a different experience than navigating a corporate site and what you end up doing is recreating a your doc site (Scroll Sites site in this case) somewhere else. With extra dependencies - would you be able to update your docs whenever you need to? Or would you have to wait for the website team to rebuild the site?

In Emplifi, we actually hooked up Open AI API to Confluence API and served answers (and links to our Scroll Site) to our users directly in the product.

 

Anyway, if you want to add more details - or correct my assumptions, feel free to do so here or get in touch and we can arrange a call to discuss your use case in detail.