Create a Table of Contents in Confluence that spans child pages AND displays H2 and H3 titles

Is it possible to have a table of content (or other similar system) that displays the H1, H2, Hx titles for the root page and children pages? I would like to have something like this:

HOME PAGE

  * Introduction

   *FAQ

    * Contact Us

CHILD PAGE 2

    * How to Find Us

     * Requesting Support

      * Holiday Hours

CHILD PAGE 3

      *About our Staff

           – Administration

            – IT

             – Billing and Inquiries

 

The CHILDREN MACRO and PAGE TREE MACRO display the pages:

  • Home Page
  • Child Page 2
  • Child Page 3

And the TOC displays the subheads of the current page:

HOME PAGE

  • Introduction
  • FAQ
  • Contact Us

But I don't see anything that combines the ability to drill down to the subheads as the TOC can on the children pages.

 

Any suggestions? I am not looking for a complex, custom macro (out of my skillset) but was wondering if there were a solution I had overlooked.

 

Thx!!

 

 

6 answers

I am curious about the use model.

Hi Bill,

You mean why do I want to do this? Fair enough inquiry and I admit this may not be a common situation.

My company wants to organize the content of various team within a common Confluence look and feel, if you will. Each team uses Confluence but in its own way, but generally populating Confluence with the same type of information.

The idea I am playing with is to have "one page to rule them all and in the darkness bind them" meaning I would like to have one page that is essentially an index page to all the subordinate content.

So you may have one doc that has a team calendar, another with Retrospective or meeting notes, and so forth.

For example then, I would have a page "Staff". On the page "Staff" I would have an H2 (or whatever) for "Director" and below that the director contact info. Another would be "Technical Support" and below that the tech support contact person. A third might be "Writer" and below that would be the contact info for the team writer.

Or if there is a longer, say requirements doc, then I would have a "Requirements" page that would contain headings for say, "Summary", "Business Impact", "Budget Analysis", "Time and Manpower Estimates" and so forth.

 

Now, back to the "one page to rule them all..."

 

The index or TOC or Child Pages list or whatever would now display in one place all the team's content:

Calendar

       *January

        * Februrary

         * March.....

Retrospective

           *Sprint

            * Starfish

Meeting notes (stand-alone series of pages)

Staff

.      * Director

        * Technical Support

         * Writer

Requirements

          *Summary

           * Business Impact

            * Budget Analysis

             * Time and Manpower Estimates

NOW, some of this can be accomplished by just having a TOC that reports out child page names. And this approach is not totally fleshed out yet.

BUT, since there is a macro for child pages, and a macro for a heading-based TOC, it seems to me (with no knowledge whatsoever) that one could have the two outputs combined to have a TOC reporting child pages that have a sub-entries, the heading level content.

 

The advantage for ME (since it is all about ME) is that content won't get lost. The "index" page will now dynamically update as new content is added, and there  will be a fair degree of discrimination with what that content on the page actually is, since the H2, H3 or whatever topic heads are selected, also are reported back and displayed. If people want to find something, they can hit the "index" page, scan a rather comprehensive TOC-style list, then click directly to the desired content.

 

Thx!

 

Don Wallbaum

 

Bill, I ended up replying to my original post - error on my part. Please scroll up to see my response to your question.

 

Thx.

 

Don

My instinct is to just assign each team a space, then set the left-hand navigation to Page tree display. Lastly, on the space home page, insert a search box macro, restricted to that space.

You wont have a display showing headings on the page, but you will have a restricted page tree and search box. With search, nothing will get lost.

I have the same requirement as I am generating the PDF document, It's needed to display the contents of H1, H1, H3 styles in the TOC as subsections.

0 vote

Great idea Don. Very similar requirement here which also would be solved by a solution to your issue. In our index page we can use a child-pages macro but it'll only list child pages. If headings on any of them are of interest to people consulting the index -- which high-level headings invariably are -- then they're invisible because the child-pages macro doesn't display them. A composite which could list child pages and their headings down to a selected level would be very useful.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

373 views 20 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you