Matt Reiner _K15t_ Atlassian Partner

@ArtWithJohn Are you using Scroll Versions or Comalla Document Management, per chance?

Hi Abid, While you can't create folders in Confluence, you can create a Space and build a similar structure using the page tree. You could create a page with sub-pages for each capability. You can then grant space permissions to give the right people access.

You could check out my team's app Scroll Documents, which has versioning and a comparison view. Here's how it works: https://help.k15t.com/scroll-docs/latest/server/compare-versions-172596662.html

Hmm, I would add a comment, since the team will most likely be in the best position to fix multiple issues with the include macro within the same issue.

The only solution I could think of would be to copy the space from time to time to get a snapshot of what the page tree looked like. But I don't believe there's a feature for this.

@[deleted] I totally forgot about this, but my team also has a "Labs" app for this: https://marketplace.atlassian.com/apps/1215816/scroll-wp-publisher?hosting=cloud&tab=overview Seems like you have a few great options. :)

In that case, you could use the in-app help feature in Scroll Viewport to embed your release notes in an iFrame in Wordpress.

Hi @[deleted] You might be able to use my team's app Scroll Viewport for this purpose. It's intended for creating whole online help center sites, but you could use it with a very simple space and then link to the site from your main site. We're using it here: https://k15t.scrollhelp.site/scroll-viewport/

Hi @Megan Stanage I think my team's app Scroll Viewport might be helpful for you. We're using the in-app help feature to bring help content write into our app UI using iFrames.

@Nick Davies You could use my team's app Scroll Viewport. We have a Confluence Server and Cloud variants of the app that both offer the ability to render your page content within an iFrame in your app. Let me know if you have any questions.

Hi @Dominic Lagger Here is a custom user macro definition that might be helpful for you. Placing it on any page will render a table with all pages with keys, their keys, and the versions for the current space. You can restrict the page to not interfere with the rest of your documentation. To re-create it in your instance,…

We just started using See All Unresolved Comments and it seems to help with this issue.

Hi @Peter Teekens My team makes and app called Scroll Versions which does this very thing on Server, but it's not on Cloud. :( That said, we're exploring a Cloud solution now, and if you'd be interested, I'd love to connect you with our user researcher so we can better understand your needs. Also, in the interim, you could…

Here's a link to Rock the Docs, which I mentioned at the end of the talk.

Yeah, Linkable Headings is the replacement feature, as far as I've heard.

@Robert Are you seeing this in the new editor? If so, there are current issues with how page inclusions are displayed.

You have my vote! 😀

@John M You could use my teams' app Scroll Viewport, which displays space content as a help site, so no comments are displayed.

@Ebrahiem Kippie While Confluence provides the Page History, there isn't full version control. For that, you can check out my teams' app Scroll Documents. Learn more about versioning here: https://help.k15t.com/scroll-docs/latest/server/document-versions-160661996.html

@Joshua Sanders Are you saying you don't have the feature when you use the "legacy template" as mentioned here? https://community.atlassian.com/t5/Confluence-questions/I-have-the-new-editor-is-it-possible-to-have-the-legacy-editor/qaq-p/1372761

Here's a bit of info on the new editor. Based on this article, it looks like you should be able to revert the page to a previous version created in the old editor: "If the user is not satisfied with the migration experience, they will have the ability to revert the migration to the legacy editor by reverting to the…

@Rachel Gies Here's a bit of info on the new editor. Based on this article, it looks like you should be able to revert the page to a previous version created in the old editor: "If the user is not satisfied with the migration experience, they will have the ability to revert the migration to the legacy editor by reverting…

Another option would be if you can get your documentation in Word format either by exporting or using an HTML to Word converter. Then you could upload it using the built in importer. You might also want to check out my team's app Scroll Viewport to turn your documentation into a help center. You can see this in action…

Here are some resources based on some of your questions: * Rock the Docs * Intro to Content Reuse * Intro to Workflows

And also here: https://community.atlassian.com/t5/Confluence-questions/I-have-the-new-editor-is-it-possible-to-have-the-legacy-editor/qaq-p/1372761

Hi @JaredH This behavior doesn't seem normal, so what you're looking to doo should be possible. Some thoughts that come to mind: * Is there any custom CSS implemented on your Confluence that could be interfering? * Have you added the macro on a line that's formatted in the editor as a heading?

@Vlado You might also want to try out my team's app Scroll Translations. While the app doesn't offer machine learning based translations, it does offer a side-by-side translation view in Confluence and the ability to export the content of a space in the XLIFF format, enabling you to do the translation in a third party…

This is great news @Traci Wilbanks! Thanks for improving the editor for the power users. 😀

I'd suggest creating 10 spaces, 1 for each product. That's how we structured things on our help site, and it really helps users narrow in on what they're looking for. Also, I'd recommend checking out the Creating Topics section on Rock the Docs as well, there might be some handy tips for your work.

Hi Rachel, thanks so much for this article. It's really insightful, and I'm motivated to give more feedback now. :) Keep spreading the knowledge!