Confluence Folders Landing Pages

[#1]

To whomever implemented this thing of beauty:

YOU GUYS.

You should put this in a release note so you can take credit for it and get a bonus or promotion or however people advance inside of Atlassian.

So what you're looking at is the perfect answer to my "meh" response to the original introduction of Folders.

• They didn't really have permanent links - if you did manage to find the Copy Link option for a folder, going to that link redirected you to the first page in the folder.
• You didn't get a list of child pages/folders, so it was actually worse than creating a "parent page" with a pagetree macro.

This is GREAT new functionality for folders:

• Folders have their own unique URL and "landing page"
• They have graphical headers (removable and customizable)
• They list all TOP LEVEL pages and folders (also databases, whiteboards) in the folder
• You can also list the objects in a Grid!
  
  (Hrm, the Grid option does not stick, but maybe it's just as well as I would think they should instead show a thumbnail of the page header instead of that weird whiteboard-looking thing.)

But at any rate, great improvement! Whoever implemented it should get credit!

But um, also: Why was this not in any of the 3 different release notes?

• Community [sic] Release Notes 
• Atlassian Cloud Documentation blog posts
• Cloud Roadmap

Also not tracked by any of the third-party Atlassian release notes trackers:

• Cloud Changelog from @Jens Schumacher - Released_so 
• The Unofficially Unofficial Atlassian Cloud Changes Roadmap from @Patricia Francezi_iDev_ 
• Unofficial Atlassian Release Tracks Notes from me

C'mon, you create something great that is NOT AI-related and doesn't change existing how we work, and you don't let us know about it ahead of time?

I guess surprises can be nice, but still! Get your props!

[Liam Do - DevSamurai]

Totally agree, @Darryl Lee !

I noticed this update a few weeks ago and have been loving it. The new folder view and functionality are a huge improvement. Kudos to the team for pulling this off 👏

[Rob Hean]

10000% agree... this drastically improves the usefulness of folders!

[Jamie Zeidler]

Haven't seen this yet. Our sandbox also has the latest release track rolled out and does not have this functionality.

Maybe its some sort of limited beta feature release being tested on a limited user set?

It looks like a much-needed improvement to folders, so hopefully it will be something we will all soon get to enjoy.

[Tomislav Tobijas]

You should put this in a release note so you can take credit for it and get a bonus or promotion or however people advance inside of Atlassian.

Yes this!! 👆

I was also surprised by this when our interns showed me this. I was like... "Wow, this definitely wasn't announced anywhere, and yet it's such a cool improvement!"
And I've been waiting for this for a while now. There's just one more thing I'm missing now, and that's the folder 'emoji' - with that, the feature would be ideal 🙂

[Darryl Lee]

@Jamie Zeidler Ah right, I should note that while my screenshots are of a test site on Continuous Track, I am also seeing it on our production instance which is on the latest Bundled (not Preview) Release from July 14, 2026.

[Becker_ Rene]

I noticed it last week.

My thoughts: Why?

1) The pictures are atrocious (anyway to disable or at least replace them?)

2) Folders already had content ID and were supposed to get rid of an "in between page". Now we are back again.

And as always: No switch to turn the function off centrally (that I know of) and of course all folders that existed have been migrated automatically. And since there was no announcement, users pointed it out an we had to shrug because we weren't informed.

So all in all: We are back to where we started except for that we can have pages with the same name twice (which should've been able without folders anyway)

The way I see it:

Folders: great function

Folders that act like pages: We have pages for that

Sorry guys but I am not with you at all.

---

[__ Jimi Wikman]

My view on this is: https://jimiwikman.se/content/videos/my-videos/atlassian-videos-by-jimi-wikman/atlassian_teamwork-collection/confluence-playlist/confluence-folder-pages-explained-should-you-use-them-instead-of-parent-pages-r110/

Summary:

• Limited functionality for handling headers = broken design
• Unclear reason to use over pages with cards or page property reports.
• Complicates navigation flow (two functions now instead of one)
• Looks nice as new function
• Feels like a MVP experiment, not enterprise grade functionality.

[Rune Rasmussen]

I noticed this yesterday, but have also not seen any notice of this. Which is very much in line with Atlassian communication strategy of non-communication.

I'm on the same page as @Becker_ Rene on this one.

We're back to the old ways of having a parent page containing the /child items macro.

And we should be able to have pages with duplicate names. They have a unique ID after all, so the display name shouldn't matter. Not in 2026.

[Patricia Francezi_iDev_]

I saw in a production instance, but didnt have the time to figure out how to change it. 

anyway - yeah, I didnt see in the release tracks (none of them) - and we really need to keep pushing atlassian to centralize ALL even what they think are MINOR....