Our team has been using Confluence in a less than intelligent way thus far (very little reusable content, almost no templates) and I'm trying to change that. The problem is... I don't know anything.
One of our needs is for an application inventory. Ideally this would be a page for every application we support. On that main page you'd find support info, a list of relevant servers, licensing info and important links. Child pages would include 1) a page with installation instructions 2) troubleshooting (with child pages), etc.
I am looking for any suggestions on setting this up in a way that doesn't take a lot of know how by my team. I was hoping to find a way to create a template/blueprint that comes with the complete page hierarchy but I'm not sure how that could even exist given you can't have two pages with the same name. I was planning on getting around that by giving each application a unique ID
Below is a pretty simple mock-up. I can't overstate how open I am to any recommendations. Confluence is fairly eliptical and if I'm going to do this right, I'd like to find out what "right" might mean.
I will read any relevant articles anyone replies with and heed the warnings of the veterans.
Have you ever noticed that fixing specific problems might be a door opener for a bigger challenge, affecting a wider audience? This was exactly the case when we, as a service company working with mul...
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