Export a Confluence document created as 100+ different pages in single export process

[Rossella Capobianco]

Hi all,

my Client wants to optimize a long doc in Confluence (100+ pages) so to easily read it AND having chance to export it (.PDF file) in just 1 export process/execution

• doc has 100+ pages
• ease read for users: 
  1. create 100+ different Confluence pages - but how then to collect them for the ENTIRE doc export?
  2. create only 1 Confluence doc using anchor [see bottom link b) ] to easily access topic theme? - each time anyway you have to scroll-up to the top for the theme anchor list (NOT QUICK, DESIRED) >> how to be re-direct to doc top first page?
  3. create different single/short Confluence pages and add a Related article tag [see bottom link c) ] to link to the following one/theme?  - but how then to collect them for the ENTIRE doc export?
  4. create different single/short Confluence pages and add a link to the following one/theme?  - but how then to collect them for the ENTIRE doc export?

Aswered question to the community (year 2016!!) seems not being the case [see bottom link a) ]:

eventually:

• how to download free and install/configure the "WebDAV" plugin?
• how to install/configure "Scroll Export add-on" including "bulk-export functionality"?

Please reply me as soon as for your availability (due date with client 2 working days!!)

thanks a lot,

regards,

Rossella

a) Is there a method to export all the pages as individual word documents?

b) Link to an anchor

c) How-to article template_Related articles

[Bill Bailey]

We use the K15t Scroll PDF Exporter (v3.x - for a number of reason), and have a doc sourced from 570+ Confluence pages that we can generate from a REST URL saved at the top of the page (in an export ignore macro). Takes a bit of time (a couple of minutes), but always works, is reliable, and creates a pretty good looking PDF. It is how we generate nearly all of our docs for customers.

[Rossella Capobianco]

thank you @Bill Bailey

for the details. I have any skill with the exporter. How to install and configure it in Confluence?

may you provide a "guide" to follow then to use it for a file .doc?

[Bill Bailey]

it is a paid plugin, and I suggest going with the older version, but you may want to read the docs before making that decision. Plus there is a limitation as to what version of Confluence is supported.

In general, K15t's documentation is pretty good, and their support is excellent.

You can find v3.x docs here - /legacy/scroll-pdf-exporter

Docs for the latest version are here - /latest/scroll-pdf-exporter-documentation

In general, the latest version is easier for new users. The older version (3.x) has many power user features not found in the latest version.

[EPS Software Engineering AG]

Hi @Rossella Capobianco 

Our OneOffixx Exporter could be a solution. We have a specification in Confluence with 368 pages (structured as a page tree) which generates a word with 346 pages.

You can find the OneOffixx Exporter on the Marketplace. And here are our LIVE EXAMPLES.

Regards,
Stephan (CEO of EPS Software Engineering AG, the vendor of the OneOffixx Exporter)

[Rossella Capobianco]

Hello @EPS Software Engineering AG 

I had a look on the links provided, anyway it seems only a plugin to export content in PDF or .doc format, already present in my Client Confluence settings.

the aim is creating different Confluence pages/spaces from the original big local .doc to let navigation and access to content easy in Confluence.

then we aim at having just 1 doc export of all so to export again the entire .doc from Confluence, hence we don't know:

- how to link each page/space to the all the other ones

- ho and from where launch the only one export of the entire file .doc

thanks

[Nils Bier _K15t_]

Hi @Rossella Capobianco

Could you elaborate a bit more on the structure of the pages? Are the pages in question all stored within the same space? Are they in an hierarchical order (i.e. all stored as child pages underneath a certain page)?

You could try our Scroll Exporters to either export the pages in question based on a certain label, or export a whole subtree of pages (if you want to export _all_ pages under a specific page).

Best,
Nils

[Rossella Capobianco]

Hi Nils, thank you.

- No, the pages of the original "big doc" are in different confluence pages/spaces.

- yes, they have a dedicated hierarchy (each paragraph con have sub-paragraph of different levels)

the aim is have just 1 doc export of all (as if being in the same big space/page/doc Confluence).

how to access to Scroll Exporters?

ho to use it?

thanks

[Bill Bailey]

@Rossella Capobianco, you may have to build a pseudo doc in a single space to make this all work. What I am suggesting is that you use the include page macro in a new space to create your superdoc in a single space. Yes, it will take time to set up, but that is probably the most maintainable solution, plus gives you control on the page hierarchy. And once done, you wont have to touch it unless you add a new page.

Note: you can have more than one include page macro on a page to make this easier.

Otherwise, you would have to generate a bunch of PDFs from each space branch, then use Adobe Acrobat to assemble all the PDFs into a single doc. Besides being a manual process and not maintainable, it also means your page numbering is off, and building a ToC would take work.

[Nils Bier _K15t_]

Hi @Rossella Capobianco

You can evaluate Scroll PDF Exporter (or Scroll Word Exporter, if you want to create a *.doc file) via the Atlassian Marketplace with a free 30 day trial license. During this period you can extensively test the app to see if it fits your needs.

The documentation can be found here:

• Scroll PDF Exporter docs
• Scroll Word Exporter docs

Our Scroll Exporters allow you to export single pages, or subtrees and whole spaces into the wanted export format.

Collecting pages from multiple spaces into a single document is currently not supported. The workaround Bill mentioned above would be an option, but would require some manual effort: As the include macro does not include the page title, but only the page content, you might need to recreate the structure in a single space (i.e. create the pages, and include the page content on each of those pages using the Confluence include macro).

An alternative would be to restructure your spaces content, and have the document structure also in your online content in Confluence (which, depending on your use case, might be the better and more future-proof solution).

Hope this helps - if you have questions during your evaluation of any of our apps, please do not hesitate to get in touch with us via support@k15t.com. We'll be happy to help.

Cheers,
Nils

[Rossella Capobianco]

Hello Nils,

I've already a draft of the .doc also in Confluence (different pages/spaces created from the .doc itself written locally).

I'll verify with my Client if those spaces have been created from a source doc already present in Confluence (containing all the pages in the same space) as test, eventually I'll discuss with him the workaround proposed  by Bill for both PDF and .doc export.

Hi Bill,

I'm thinking to suggest to the Client , is having the whole .doc in a space on Confluence with 2 sections:

        1. anchor : to see content of section of interest directly in the whole doc         file/Confluence space

        2. a second different section with the list of the hyperlinks of all the Confluence spaces/pages related to the sections of the whole doc and created to ease document reading (optimizing hence the actual use of Macro "anchor").

the export of the whole doc from Confluence has to be launched from the Confluence space having the 2 sections mentioned above (hence the whole doc content). 

What do you think? 

[Bill Bailey]

Sorry I am not clear what you are proposing.

Yes, moving the entire doc to one space is a good idea, but is a lot of work (and you have the issue with name space collisions). And the client may not want to go that route. This is why I suggested creating a page structure you want, and the include the content via the include page macro.

And any place where you have to create a long page title to avoid namespace collisions, you can use the scroll page title macro to create the title you want to appear in the PDF.

And for Confluence, you can create links to other pages directly, rather then by using anchors. These links are dynamic, do more durable.

If you are trying to create a ToC for the doc, that can be automatically generated by Scroll PDF exporter.

You can also have a listing of related pages based upon labels by using the Content by Label macro.

[Rossella Capobianco]

thank you Bill!

I'll then discuss your suggestion to my Client.

To be sure I've got it correctly I'll summarize below:

1. Once the whole doc structure is defined (conceptually), I'll create one whole doc/Confluence space reflecting it and filling the body using "include page macro" to insert all the different separate pages/Confluence spaces

2. for eventual long sections titles name, or in general as best practice, I'll use "scroll page title macro" to customize the title name of each section

3. I'll do not use then "anchor macro" as suggested, but to reflect the summary (the same table of contents usually present if you use "anchor macro") of the whole doc at the top I'll list all the section titles and as direct links to the dedicated separate page/Confluence space existing. Is that right?

4. I'd a look in " Content by Label macro" suggested, I'll check with the Client if he's interested in collecting different Confluence spaces with "similar" themes/words/.. (example "all pages that have the label 'feature-shipped' and include the word 'Blueprint', or to list any pages with the label 'meeting-notes'" mentioned). Have I got it right?

Final question:

What "a ToC for the doc" is/means?

thanks a lot for support and availability!

[Bill Bailey]

ToC =  table of contents. ;-)

If you use the Scroll PDF exporter, you do not need to create this for your doc. It is autogenerated. The Scroll engine is very smart in being to autolevel headings (H1s on child pages are below H1s of parent pages). So as long as your headings and page structure is good, you will get a nice ToC without having to try to maintain one in Confluence.

This also goes for front matter (title pages, copyright notices, etc.). With the proper structuring and design, you only need to have content in Confluence.

[Rossella Capobianco]

thanks Bill, I'll discuss the buy of Scroll PDF exporter to the Client, eventually use it to obtain the doc as a test with the 30-days free trial.

May I then proceed with/do you confirm me the process steps I've summarized you before (1-4) considering only change for doc summary at the top?

thank you!

[sara]

WebDAV plugin is bundled and comes with confluence.There is no need to install this.You can use webdav client to connect to confluence from local.

[Rossella Capobianco]

thanks Sara, how to retrieve/access to the plugin in Confluence?

I can't find plugin section dedicated.

How to use it?

thanks in advance