I am sure this question comes often and doesn't have any right or wrong answer but I have to ask it as I am wondering if we are starting the wiki on the right foot.
We are a hardware developping company. We have many projects (products). The big question is: how to organize this?
Right now, we started as one space per project. This will grow (tens of projects; hopefully hundreds). Is this a viable approach since we can't have nested spaces (tried the subspace plugin but it does create a space after all and the space list grows the very same way).
The dilema I have is that I could cathegorize projects and have a shorter list of spaces. I am also unsure of how confluence will handle so many spaces (probably doesn't matter much but still, I don't know).
Any input is welcome,
Interestingly, I'm looking at one section of a space and that has at least 82 pages, and it's not a particularly large area. Some have over 400, so a wiki space can have a great many pages. You're not going to change that unless you have lots of spaces instead.
If you don't want everyone to see everything in a sapce, you can always use permissions to hide the areas you don't want them to see or find in searches.
You should be able to print only the pages you want to print if you look in the Space Admin area. I haven't done this, but if you look at the page tree in there, you can select the ones you want to print and then print them as one document. (There's more to it than that, best check the Atlassian docs.)
You can also create an empty page and then use the page include macro to add all the pages you want to print, then save that and export to PDF.
My first thought is how do the people who are going to use the wiki view the projects/products? You might be able to organise by project/product type, but is this how your users (and possibly your customers) see group them? What natural groupings do your projects/products have?
I'm not sure that having 100s of spaces is much of a problem, I believe Atlassian have at least that many, so theoretically Confluence should be able to handle it.
One of the nice things about having seperate sapces is that you can limit search results to that space only. On the other hand, there's not much point in having 25 spaces that only have 20 pages in each. So another criterion might be how much content will each space have?
I see you point. Eack project will have requirements, development docs, schematics etc. Many type of documents; hence why we opted for a space per projet. The pain is in the browsing; the tree is just too big.
The Wiki is, for now, only for our R&D. But we wish to eventually be able to print our product specifications directly from the wiki. This is a bone when export to PDF adds header/footer only to a complete space export.
I really appreciate your point of vue; thank you very much.
Hi Community! 2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...
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