# How do you structure your documentation repositories in Confluence (or similar)

**URL:** <https://club.ministryoftesting.com/t/how-do-you-structure-your-documentation-repositories-in-confluence-or-similar/61733>\
**Category:** Archive\
**Tags:** documentation\
**Created:** [12 August 2022 01:36 UTC](https://club.ministryoftesting.com/t/how-do-you-structure-your-documentation-repositories-in-confluence-or-similar/61733 "2022-08-12T01:36:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![piconyannyan](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/piconyannyan/32/9018_2.png) [@piconyannyan](https://club.ministryoftesting.com/u/piconyannyan)\
**Post date:** [12 August 2022 01:36 UTC](https://club.ministryoftesting.com/t/how-do-you-structure-your-documentation-repositories-in-confluence-or-similar/61733/1 "2022-08-12T01:36:41Z")

</div>

I am tasked to propose a base structure for the Confluence page for our own team. I tried searching for this topic here but seems to be something that hasn’t been discussed.

How do you structure your documentation in the QA space? Below is what I have come up with so far.

- Onboarding   
– 00 - Onboarding Schedule  
– 01 - Getting Started  
– 02 - Systems Overview  
– 03 - QA Process  
– 04 - QA Defect Management  
– 05 - Using the test case management tool  
– 06 - Application Links & References  
– 07 - Scrum for QA
- Test Case Repository
- How to Test Guides
- Test Automation   
– Development Environment Setup  
– Writing Automation Test Cases  
– API Automation Best Practices
- Production Release Plan
- Training Resources

---

<div class="post-metadata">

**Author:** ![markjnicoll](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/markjnicoll/32/10683_2.png) [@markjnicoll](https://club.ministryoftesting.com/u/markjnicoll)\
**Post date:** [16 August 2022 16:07 UTC](https://club.ministryoftesting.com/t/how-do-you-structure-your-documentation-repositories-in-confluence-or-similar/61733/2 "2022-08-16T16:07:25Z")

</div>

It looks like a good start.

I don’t think there is any one solution to this as each company is different.

What I will add is, I find the use of emojis at the beginning of page titles that are the “index” pages to the child content helpful; It is easier to navigate.

![image](https://us1.discourse-cdn.com/flex020/uploads/ministryoftesting/original/2X/4/420e8945d64bb191918ad50c7315e4bce7a161f3.png)

---

<div class="post-metadata">

**Author:** ![piconyannyan](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/piconyannyan/32/9018_2.png) [@piconyannyan](https://club.ministryoftesting.com/u/piconyannyan)\
**Post date:** [17 August 2022 03:19 UTC](https://club.ministryoftesting.com/t/how-do-you-structure-your-documentation-repositories-in-confluence-or-similar/61733/3 "2022-08-17T03:19:34Z")

</div>

Makes sense. Actually, I had some difficulty coming up with a one size fits all structure, but being a base structure, there could be common ground at least.

Also, those emojis looks nice for index pages 😃