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
1c. Click and drag these into the structure you want:
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:
...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.
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.
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"?
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.
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.
"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.
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?
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
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!
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