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
My team and I are potentially migrating to confluence for technical content creation (migrating away from word), and a consistent question from independent alpha groups is:
If I have 100 headers, how do I navigate to each one like in Word (see image)
There is some user angst when working/navigating such large pages. Google results are all geared towards "pages" but this would be specific to editing a specific page.
Does anyone have any suggestions/guidance on this feature request?
But really, Word and Confluence are not the same thing. You'll have a lot more freedom in how you are able to display and get to content in Confluence. It's not all just one really long document anymore.
It'll take users a little time to change the way they think/behave, just like with anything else new. But the thought of having to use Word documents to find content makes me cringe vs. all the possibilities in Confluence.
@WW I'm with you! Word is dated and we spend considerable amount of time trying to manage the weird quarks that are endemic with the software. So far I prefer confluence to any other tool we've used, but it's missing some critical tools (or what we as a working group deem "super necessary").
That said, I'm nervous to break sections into a separate pages as Confluence treats each child page as an appendix on export. I also never want that content to exist outside of the parent.
Do you know of a way to control/mitigate the above concerns?
Appreciate any guidance you'd be willing to share
Again, it's a change of mindset and culture on how you'll organize your information.
Each page has a parent page, so you can keep your pages under a parent page if you want. It doesn't really matter though since you can point to pages in your space in different ways and even in other spaces.
You can also use the Include macros (Include page, and Excerpt and Excerpt include macros) to put content where you want it to go. I wouldn't "Include" hundreds of pages or it'll take forever for the page to load if it does.
I would explore the list of built-in macros available.
Exporting is also a mindset change. You shouldn't need to export pages unless it's for someone who doesn't have access to your Confluence instance.
If you really need to export pages, then just keep your pages in whatever order you need. You can edit the PDF export stylesheet, but I don't think that'll make a difference in the order in which each page is exported.
If you're talking about exporting multiple individual pages at the page level, then there's a way to export them together. Users with the space Export permission, are also able to export multiple pages at a time through Space tools -> Content tools.
Hopefully some of that helps.
Confluence has "macros" which add functionality to pages. One such macro is the "Table of contents", which is extremely configurable and can easily handle the requirement you mention. More about it here:
Hello @Mykenna Cepek ! Appreciate the response. Gave it a try and noticed is only works in preview or when published. Is there something that works while a page is in the process of being authored?
We need a tool to help content creators navigate their drafts.
Any guidance is appreciated
A feature request page for Confluence Server/Data Center. :D :D :D :D
There are feature requests that have literally been sitting out there since 2011. I wouldn't bother.
They'll most likely tell you to get a plugin. You can explore the Atlassian Marketplace for all sorts of additional functionality.
As WW alludes to, Atlassian does have a way to contribute feature requests (more here). But many of us feel that's a broken process, overly relying on votes to put things on their radar.
If you've got support, I would engage them. Get your money's worth from talking to someone at Atlassian about your needs. On a good day they can point you to something, either in the Marketplace that might help, and/or in their product backlog that you can vote for.