We're using Confluence to share our knowledge about several Projects.
This also includes noting the growing know-how related to working on growing Code and Repositories.
By the time and commitment of several programmers there's quite an output over time. What are your strategies and best-practices to keep Glossaries readable and update-able?
And how do you structure your Index- and Wiki-Pages and ares so people are able to find what they are looking for as afford-less as possible?
Especially related to common bugs it would be nice to keep it StackOverflow-Like and avoid parallel or overlapping Index-Pages.
Can you tell me a bit about your ideas and solutions?
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
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