Docs
====

.. todo::
    **Onboarding docs**: Since all docs are now unified in this repo, we need to rework this page.


We're a highly structured company - even (or especially?) because we're so small.

Thus we've some documentation deployed which should cover most of the **daily stuff** required.
We try to document **only the necessary things**, but document them pretty well.

Most docs are based on `Sphinx <https://www.sphinx-doc.org/en/master/>`_ and `reStructuredText <https://docutils.sourceforge.io/rst.html>`_ files.

confirm docs
------------

We've the :ref:`Handbook of confirm IT solutions <handbook>`. These handbook is internal and document the following topics:

- Administrative topics
- Operational topics
- Infrastructure topics

Feel free to browse the :doc:`docs <docs:index>`, and read whatever sparks your interest, for example the :ref:`fringe benefits`.

.. note::

    These docs are only available from internal networks. However, the `Docs Git repository <https://gitlab.confirm.ch/confirm/docs>`_ can always be accessed.

.. _DIY onboaring Strategy:

Strategy
--------

We've the :doc:`strategy:index` docs. These docs are internal and document the following things:

- Strategy framework
- Organisational chart
- Roles and their responsibilities

Feel free to browse the :doc:`strategy:index` docs, and read whatever sparks your interest, for example the :ref:`strategy:organisation`.

.. note::

    These docs are only available from internal networks. However, the `Strategy Git repository <https://gitlab.confirm.ch/confirm/admin/strategy>`_ can always be accessed.

Corporate identity
------------------

We've the :ref:`corporate-identity` docs. These docs are public and document the following topics:

- Our brand and public appearance
- Our guiding principles
- Our communication style

Feel free to browse the :ref:`corporate-identity` docs, and read whatever sparks your interest, for example the :ref:`foundation`.

.. note::

    These docs are public.

    Everything that is published must be compliant with our corporate identity & design.

Guidelines
----------

We've our :ref:`technical-guidelines`. These docs are public and document the following topics:

- Client guidelines
- Documentation guidelines
- Meeting guidelines
- Scrum guidelines
- Development guidelines

Feel free to browse the :ref:`technical-guidelines`, and read whatever sparks your interest, for example the :ref:`Zen`.

.. note::

    These docs are public and can be accessed by anyone, as we love open source.