What do you put on a Confluence space home page?

[Julien Morel]

I keep seeing Confluence spaces where the home page starts as a helpful entry point, then slowly becomes a dumping ground for every important link.

The structure I like is fairly simple:

1. A short purpose statement for the space.

2. Links to the 4 or 5 pages people need most often.

3. Ownership and review notes, so people know who maintains the space.

4. A separate index page for the long list of reference pages.

I am curious how others draw the line. What belongs on the space home page, and what should move into child pages, labels, or an index page?

[Jason Krewson]

For my Confluence Space home page I have the team name, about section, mission and vision, then under that I have a 3 column layout.

For the layout its:

• Meet the Team on the left, this has each team members profile pics (its just my boss, someone that manages time tracking in our Tempo Timesheets apps, and then me). 
• Get Help in the middle, this has Start with Rovo info panel macro that sends people over to all the Rovo agents we created. Then it has a Need Support section under Rovo, this just lists out how to contact the team. 
• Quick Links on the right, this brings you to my Jira Space, my Team Dashboard, all my documentation hidden under an expand macro, active Jira work and Completed Jira work under expand macros. 

And that is it. I try to keep the home page pretty clean. 

On the left had side I do have some short cuts added to my Jira space, my SharePoint site I used for monthly newsletters, my Jira dashboard, and my MS Teams helps channel. 

Under that I have everything organized by folders. My folders are Jira & Confluence Guides, Rovo & 3rd Party AI Guides, Atlassian Goals and Projects, Atlassian Team Newsletter, Training, Jira Sandbox, Admin Guides, and then a folder that holds test and example pages. 

[Jay Maechtlen]

We have a lot of different spaces, each dealing with some part of our organization. 

Some include a roster of team leaders, many of them offer some combination of links and resources.

A few of them still show the default placeholders from space creation.

Thanks for the suggestions!

[Rob Hean]

For me it depends on the purpose of the space. For example a "team homepage" may benefit from having a "meet the team" section that includes who's on the team and what they do. A project homepage could benefit from having metrics or project goals.

Personally I tend to shy away from index pages as I find search and/or guidance to be more useful (plus I find index pages basically reflect the content hierarchy, which is already on screen).

Most of the time I see groups basically ignoring the homepage and leaving it templated, so honestly I'm happy whenever a group does anything to change it from the template :D

[Barbara Szczesniak]

My space contains the documentation for our application.

Originally, my home page contained several paragraphs describing the documentation, with links to the main sections—like you would have in the introduction to a user guide.

Then, we decided to use K15t's Scroll Viewport (now Scroll Sites), which converted this page to a short "statement" on the landing page of the site, so I pared it down to one sentence that fits in the space available.

[Anwesha Pan]

Hi @Julien Morel 

We have 2 spaces in my org, one is for Knowledge Base and another is for my team. So based on the spaces, I have organized the Home pages accordingly. 

For KB space :

• Spotlight - added Welcome section
• Page Search - for easy search on the page
• Background - to highlight what, why, who's
• Child pages - to include links to subpages under the home page

For Team space:

• Welcome
• 3 columns layouts - Vision, mission, norms
• Meet the team
• 2 column layouts - Additional contact & squad ownership details