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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey everyone! Product Manager on the Confluence team here, we’re in process of working on some major fixes & improvements to PDF exports that will be released in the next few months.
For those of you that use space PDF exports we are looking to get insight on how you’re currently using it and how existing functionality works for you - specifically:
What’s the main purpose that you’re using space level PDF exports for?
Does the current default space PDF export behavior match what you expect?
Header Demotion (Headers are demoted depending on each page’s depth in the page hierarchy. e.g. Header 1 in the top page will be header 1, but Header 1 in a page 1 depth below will be converted into Header 2)
Page Concatenation (each Confluence page is not started on a new page, but instead starts right after the previous page ended)
Do you use custom headers/footers/stylesheets? If so, what do you use these for?
Do you do any post processing on your space PDF exports that are generated from Confluence?
Do you see gaps in space PDF export functionality you’d like addressed?
We may reach out to a few of you to get more in depth details 🙂. Looking forward to hearing from you all!
Thanks @RPT Admin for your answer - the issue you reference is one of the top priorities that we're looking to fix for PDF Export.
We are looking at ways to get our improvements out faster - you mentioned "easy to read and to navigate" - do you & team use the table of contents as essential functionality for these space level PDF exports?
Yes we do. Some of our pages are 20,000 words or longer. I know, I know! We tried short pages but they didn't survive UX testing. Our users like to see the whole of a complex topic dealt with on one page. So the TOC is vital for navigating an individual page.
I just checked one of our biggest pages - it's a 43,000 word behemoth about a piece of legislation which our knowledge workers interact with on a daily basis. The TOC displays 15 headings and 16 sub-headings. The actual instructions - how to "do stuff" - aren't until the 9th heading.
I run semi-regular webinars where I help people find their way around the knowledge base, and many of my users routinely use CTRL-F on complex pages. But it's no substitute for a well-laid out TOC. So yes, it's widely used in my main space.
Thanks @RPT Admin !
Just to confirm - the ToC you're referring to is on a page level correct? Are you utilizing the ToC generated for a space export?
I'm referring to the page level TOC. I wasn't even aware there was a TOC generated for the space export. My main knowledge base has a comprehensive site map on the front page which my users are used to using, so they continue to use that to navigate the PDF.
I'm aware my use-case is probably an outlier, but I guessed that was was why it might be interesting.