You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm juuust getting started and I have a kind of organization challenge. Not organization like a business but organization like how to order stuff with confluence.
It seems there are a few different ways to look at the "stuff" I would contain in confluence (the content)..
There's the kind of thing it addresses (as in a website to be built vs a mobile app vs a desktop application, and so on). There's what you're gonna do with it (as in designing it, managing it, coding it, and so on). Then there's the kind of information that it is (as in troubleshooting vs how to vs policy declaration or document, and so on).
That's 3 distinct paradigms. What is a sane approach to organizing that mess? And how would I even begin to find an answer?
Maybe I should start by writing an article on how to write articles. (That was a joke).
I totally figured it out. I guess I just needed to work through it and writing it out here has made the difference. I'm not sure what's appropriate for the community - to delete this whole thing and move on or leave it here. I would share my discoveries if I knew how / where.
Wow... this actually sounds like a Dear diary post @Jake .
Actually, Its never to late to write a "how to write article"..
We have tons of new folks join in and they can definitely benefit from it. :)