# End User Documentation Structure

**URL:** <https://forum.mautic.org/t/end-user-documentation-structure/24355>\
**Category:** General Discussion\
**Created:** [June 3, 2022, 1:45pm UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355 "2022-06-03T13:45:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![favourchi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/favourchi/32/7701_2.png) [@favourchi](https://forum.mautic.org/u/favourchi)\
**Post date:** [June 3, 2022, 1:45pm UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355/1 "2022-06-03T13:45:45Z")

</div>

Hi everyone,

I am Favour Chibueze and I was selected to participate in Google Season of Doc’22 at Mautic as a technical writer.

Our goal in this project will be to improve end-user documentation as well as move existing documentation to a new platform while also organizing and structuring information to make it easier for a user to get started.

I would love to hear your ideas for the end-user documentation structure and how I can make the experience better for users.

---

<div class="post-metadata">

**Author:** ![zaharovrd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/zaharovrd/32/7799_2.png) [@zaharovrd](https://forum.mautic.org/u/zaharovrd)\
**Post date:** [June 5, 2022, 8:12pm UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355/2 "2022-06-05T20:12:34Z")

</div>

How you planing organizing documentation on different language?

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [June 6, 2022, 8:38am UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355/3 "2022-06-06T08:38:36Z")

</div>

@zaharovrd once we have the docs migrated and updated in English we will make use of the Transifex integration from Read the Docs to allow translators to work on creating a translated version.

The docs are here on how that works: [Manage Translations for Sphinx projects — Read the Docs user documentation 8.1.1 documentation](https://docs.readthedocs.io/en/stable/guides/manage-translations-sphinx.html)

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [June 10, 2022, 11:34am UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355/4 "2022-06-10T11:34:12Z")

</div>

Hi,  
We found it extremely helpful if the first steps (a little bit of everything) are summarized to help people to get started fast.  
Each topic can be further unfolded, and ellaborated. I would create a list of minimum docs to have someone started with Mautic including:

1. tracking
2. import
3. create an email
4. sending
5. segments
6. campaigns

And go from there. We did it differently in the beginning, but re-organising the docs helped our clients.  
Of course this is just one way to do it.

---

<div class="post-metadata">

**Author:** ![favourchi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/favourchi/32/7701_2.png) [@favourchi](https://forum.mautic.org/u/favourchi)\
**Post date:** [June 10, 2022, 11:48am UTC](https://forum.mautic.org/t/end-user-documentation-structure/24355/5 "2022-06-10T11:48:19Z")

</div>

Thank you for sharing. We would look at implementing this.