It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Creating a folder?

How does one create a folder in Confluece?

6 answers

Folders you say? Well, look no further! Confluence makes it easy to leverage this most basic feature of computing that has been in existence since before the assembly language in ONLY 5-7 easy steps!

1. make sure your pages are in the hierarchy you want them:

1a. Navigate into the space you want to act as a file system and select the menu

SpaceMenuButton.PNG1b.

ViewInHiearchyPNG.PNG

1c. Click and drag these into the structure you want:

click-drag-these.PNG

 

 

2.  Use the instructions in the link below to add child-lists to your "Folder" documents so that you can view their child-"contents" with one click:
https://confluence.atlassian.com/doc/children-display-macro-139501.html

...and TA DA, just like that the MIND BENDING power of folders is yours to harness and direct at your most complex tasks thanks to forward-thinking at Confluence!

That's not "folders", it's just one way of using the natural structures within Confluence.  The nature of Confluence data tends to make folders a redundant concept, but you can mimic them if you want.  It's not that useful in Confluence, but it doesn't stop you.

Like Stefan Daut likes this

"The Nature of Confluence data tends to make folders a redundant concept" 

Could you please expand on that? I would love to know how this post-folder world works and leverage its powers of efficiency.

Like # people like this

Folders work for structured classifications like file systems.  Confluence is a wiki, not a file system.  It's not like sharepoint where documents go to die, it's supposed to be a living collaborative space where the structure is more usefully classified by content than location. 

I was wondering what the format was. I've used wiki's before and I didn't even realize that's what this was (Only been using confluence for a week.)

However, as we may think the kool-aid is the best drink we ever tasted and evangelize on anyone who wishes for a sip of water - I'd like to put forth that, in a situation in which someone is specifically asking for water, that giving them a cup is probably the best idea.

Take my case for example, I DO just want some documents to die, but, I would also like them to be in existence, accessible, and within the same silo as my other documentation in case of the worst. I am just a nice guy like that. Hence, the need for a folder every now and then.

Like # people like this

Anytime some open source software doesn't do something, the true believers turn that from a bug into a feature.  

Re: 1. make sure your pages are in the hierarchy you want them:

But they're not.  How do I create a new entry in the hierarchy? 

And what is "hierarchy" here?  A hierarchy of "spaces"?

Like # people like this

Ah, you create a new space, then click on ... in the upper right, the "move".   Hmm, but I can't seem to move the new space to under my Confluence home page.    I think I'll just use Notepad.

I don't think you've grasped what the software does.

There is a hierarchy, which makes "folders" redundant (at best, a primitive way of thinking).  Go to a page anywhere (let's call it page A), hit "create page", put something in it and save it as Page B.  You now have page B in the hierarchy under Page A.  You can move it within the space in the space's tree under tools, or move it and give it a new page, or even space.

Like Jeffrey Leupp likes this

Re:  I don't think you've grasped what the software does.

I've used a lot of software over many years.  In design reviews, when developers blame the users, experienced managers will usually ask if the UI could be made more intuitive.

Re: create new page B under existing page A

Ah, so I need to create a dummy page to hold subpages, because there's no concept of a directory entry.   Got it. 

Like # people like this

Correct, because you don't need one.

Most people grasp that intuitively when introduced to Confluence.  It's not a developer blaming the user, it's another user pointing out that you've misunderstood something.

"There is a hierarchy, which makes "folders" redundant (at best, a primitive way of thinking)."

Only in the mind of an Atlassian developer would a blank confluence page be a reasonable substitute for a simple folder to better organize content.  If you genuinely can't picture why a user would "need" a folder, you lack imagination.

Like # people like this

Boy, I couldn't agree more. I spend some quality time looking for a way to start a "container" of pages.

It is beyond ridiculous that the evangelists in this thread would say that I should "intuit" that my 2 dimensional "sheet of paper" (page) will magically gain another dimension and become a "box of paper" when I click CREATE.

What garbage thinking is this. The mere fact of this thread should be informative to the designers that there is a problem.

<sigh> So you're suggesting that software that does "folders" two different ways is simple?  Really?

I am sure I was too heavy handed with my remark. It came after trying to figure out how to do something in Confluence that I and others have been doing for decades readily in other tools.

I am not suggesting that the software should do folders two different ways. I am suggesting that -

If a number of people repeatedly have a problem with how something is done with an app, it is reasonable to think that the app needs to adapt to the people as much as the people need to adapt to the app. It could be anything from hints to doc to whatever that can convey answers and alternatives. App adoption sometimes means the app isn't being used the way its creators and evangelists envisioned.

Nah, I'm the heavy-handed one.  I apologise for that.

How would you "fix" it?  Have folders that aren't pages as well as pages that already do the job of a hierarchy?  Throw away pages as containers completely so you have to build a hierarchy separately and then put pages into them independently (you can almost do this already - create "folders" as pages with nothing more than the {children} macro on them)?

Yes, that is what I would suggest they do.

Ok, why?  Why would that be better than what we have now?  How would you suggest your average user decides whether to use a folder or a page hierarchy?

Please, explain the benefits?

Obviously you haven't read this thread in detail, so I'll explain.  Unlike most technologist who believe their solution, although technically correct, is the best solution I'm looking at what the users need to do their job.  My job is not to force an unwanted solution on users because it's "technically" correct but to give them the solution that helps them best to do their job and in turn benefits the company.  I've explained to my employees they are similar to snowplow drivers.  They're job is to clear the road so others can get to where they need to go.  The level of arrogance in this thread demonstrates why the technologist shouldn't make business decisions.  Everyone is asking for folders but Atlassian fights it for what reason?  Because they know how to do my job better than me?  There's enough reasons suggested in this thread to argue for folders but at the end of the day it's only folders and we've wasted too much time already discussing it.

Please don't accuse me of doing what you have done.  Read the thread.  Especially the parts where I ask how folders should be implemented, how they would be different to the existing hierarchy, and, most importantly, how they would be of any use?

Just saying "I want folders" is no good.  You need to explain how you would expect them to work and why that would be useful alongside the existing hierarchy.

And, why the simple "create an empty page with no detail (or a child page macro maybe)" does not make it work the way you want?  (Other than being pretty poor use for the reader)

Wow, once again you prove my point. Your thinking like a technologist and not a business person.  This is a waste of time.  If giving the user a folder saves them time then just do it.  Look how many people have wasted valuable company time researching this issue.  But you don't think in the business sense because it's not your money or time.  I'm done wasting my time with you.

Nic,

Mark is accurate in his remarks. You are missing our shared point. It is up to you to provide a solution that makes this whole thread unnecessary. It is up to the designer to predict the problems of adoption (like: I am used to folders, where are they??). After "getting it" - just create a page and make it look like a folder - I moved on. But, it should not have take me the time it took to find that solution. The designers job is to predict and prevent these adoption problems. Here's an example - have an item under CREATE that is "Folder" but when someone clicks, create page with something in it that explains that a page can be a folder. I could work on that for a couple of days BUT IT'S NOT MY JOB, IT'S ATLASSIAN'S JOB. Do you get that when a lot of people have difficulty - IT'S NOT THE PEOPLE, IT'S THE APP.

In a way, I want to write "Please don't respond." because we've belabored this to death. Time is precious. Move on.

...barney

Like Greg Lyon likes this

I think you're still not understanding, but we'll have to agree to differ.

I'm not a designer, a "technologist" or an Atlassian, just someone who likes simple systems that work. Most people who adopt Confluence do not have a problem with wanting "folders", the hierarchy of pages works fine for what the system is for.

All I've asked for is an explanation of how folders would work and how they would be better than a useful page hierarchy. With nothing of any use coming back, there's not a lot more to say.

I'm glad you worked out how to make low-content pages that give you a folder structure that's already there - I'd recommend that if you create templates for them with that name. (And keep an eye on how much they get used as folders because most people won't)

It is indeed time to move on, as I'm clearly not going to get a useful answer to my questions.

Just create and empty page with no content. Then add child pages to that page.

This works until you have to add two folders somewhere with the same name.

Like # people like this

I do not see a button or a menu item "add a child page" on my page.

Like Benjamin Slade likes this

Go to the page you want to create a child of.  Click "create".  The default place for the new page is under the page you were looking at.

Just remembering my initial impression when I first used the "Create" button (create page).  It wasn't clear to me where the new page would go.   

The "Create" button is up with top level items such as Spaces, People, Calendars.  My first impression is that it would create something associated with those top level items.  I didn't want to be the newbie doing stupid things like accidentally creating new Spaces.

Looking at the top of the current page subframe (CSS DOM id=main) , there are actions like Edit, Watch, Share  (in a subsection with CSS DOM id=main-header.navigation).  There is also an anonymous 3-dots pulldown menu (no mouseover description) on the current page with fancier extended actions like:  Page history, Restrictions, etc.   But there's no option to create a subpage.

The mouse-over popup help the the "Create" just says "Create blank page".   It doesn't say where.   

In fact, if you click on the 3 dots next to the Create button, and choose something like "Balsamiq Wireframes" it does create a new page with the wireframes at the point in the page hierarchy above the current page (different behavior from the create page operation)

No big deal once you understand it. 

If the "Create" button mouse-over help had said "Create blank page under the current page", it would have helped me.   If there was a "Create subpage" under the unnamed 3 dots menu (in the current page), that would have helped me.

It's interesting, I popped on here because I had the same question - I wanted to create a very simple taxonomy (just a clear separation of a couple of subject areas) so the lists of content didn't overwhelm. I was failing to find structuring mechanism beyond adding a placeholder page (I was hoping for something I could select that would show all the contained pages in the main view - perhaps even along with a short description - without manually creating that.

So, I found the make a blank page, add a sub-page. Fair enough, it works - could be improved (esp. regarding discovery) but it is what it is.

The bizarre thing (and this is my first post) is the aggressive and unhelpful nature of the 'Community Champion' commentators. This was a genuine surprise! Let's get one thing perfectly straight - users are not 'wrong' if they are unable to discover how to do something - the solution is incorrect (this might just mean not fit for what that person is trying to do, but it's certainly not a 'this software is perfect, go learn how to use it' moment).

Anyway, back to the solution...

Make a blank page, move the sub-page under that. Cool.

(and be careful about naming - there are some strange restrictions on duplicates if I recall).

Stay happy :)

great- how do you move a document in progress (*unpublished) into a new space that you are creating under a space for expressly that purpose- and more importantly, if you have a existing hierarchy of say 100 documents with images and cross references that you need to format into confluence for easy reference, that are all linked by an existing taxonnomy, how do I get them into a linked "spaces" setup exactly reflecting this existing structure? 

Also, could someone point to useful (therefore not Atlassian) documentation on how to create "spaces" that do not have anything in them for use in confluence ? And documentation on how to move things around in Confluence? All Atlassian documentation seems to reference multiple ways to do things none of which are related to actual solutions.  

I'd rather not have to go create 100 dummy spaces, then 100 dummy pages, then fill each out, then copy paste dozens of times and reformat, then move each around.. hours of work and copy paste- ? I think I'll just move it to a file share and point to it rather than try to use this? 

Well put, Rick.

You don't create a folder in Confluence because that is not how Confluence works. You create spaces and pages inside spaces. Or did I misunderstand the question?

And you create subpages under pages.

Perhaps you're referring to create groups for such users. Can you polease clarify about create a folder in Confluence?

your space is the folder that holds all documents added to confluence.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

What's New in Confluence Cloud – November 2019 Edition

Hey community! This month we’re excited to share brand new features to help you make your mark on Confluence. If you haven’t already, check out our updates from October and September too! Expre...

11,194 views 11 30
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you