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
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
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?