At StackCommerce, we currently host our internal private wiki with Github Wikis, and I've been trying to find a good way to organize it in a way that visually makes sense, i.e. how to utilize sidebar content and page content effectively.
I've tried looking for more discussions around wiki structure for inspiration outside of the world of open source (which doesn't quite fit our needs currently) and I haven't had much luck.
Right now, we have a few main sections such as 'Documentation', 'Engineering', 'How-To', 'QA' and 'Product Specifications', but not every sub-section is organized accordingly.
TL;DR--Do you use a wiki at your company and do you find that it's organized well? What makes it work for your team?
Any tips would be appreciated!
Top comments (6)
I organize our Confluence regularly and maintain proper formatting and tables of contents in our posts themselves, but overall I think the best thing is to have solid titles and a search bar. I don't see anyone really browsing our docs -- they would search for what they need.
Can you guide me on how to set up a proper account on GitHub I want to make my portfolio because I'm Wikipedia editor have to look my site wikipagecreation.agency/ and want to set it to GitHub as a portfolio?
At StackCommerce, organizing a private wiki to ensure it’s both user-friendly and efficient can be quite a challenge. At Elite Wiki Creators, we specialize in creating well-structured and visually appealing Wikipedia pages and internal wikis for companies. Our expertise in Wikipedia writing services can be easily adapted to private wikis, ensuring that your content is organized logically and is easy to navigate.
One tip is to utilize the sidebar for primary navigation, listing your main sections such as 'Documentation', 'Engineering', 'How-To', 'QA', and 'Product Specifications'. Under each main section, include links to sub-sections and important pages. This helps users quickly find the information they need.
Additionally, ensure each page follows a consistent format with clear headings and a table of contents at the top. This improves readability and makes it easier for users to locate specific information. For more ideas and assistance in structuring your internal wiki, feel free to check out Wikipedia Page Creators for professional guidance.
Interesting, I never thought of it that way. Thanks for the perspective!
I recommend you to check out Gitlab. They are using their platform as a wiki to share what's going on in every unit, and publicly. It's amazing to see it day by day.
Ah yeah, I use Gitlab personally, but I can't change where the company I work for hosts all of our application code, unfortunately. I love how Gitlab makes everything public, though. :)