[MOV] documentation structure reorganization

This commit aims to improve the documentation's navigability by
redefining some categories' purposes and titles.

There is a redirection rule for each documentation page moved.
This ensures that users won't have a 404 error message.

task-3217827

closes odoo/documentation#8063

Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
This commit is contained in:
Jonathan Castillo (jcs)
2024-03-04 12:02:08 +01:00
parent af91b7c2b6
commit bf7fa31503
562 changed files with 644 additions and 643 deletions
@@ -12,9 +12,9 @@ In this chapter, you will learn:
Install
=======
There are multiple ways to :doc:`install Odoo <../../../administration/install>`, depending on the
There are multiple ways to :doc:`install Odoo </administration/on_premise>`, depending on the
intended use case. This documentation assumes you use the :doc:`source install
<../../../administration/install/source>` (running Odoo from the source code), which is best suited
</administration/on_premise/source>` (running Odoo from the source code), which is best suited
for Odoo designers and developers.
Databases
@@ -44,7 +44,7 @@ Fields
In a model, we will centralize fields (field names we need to target in our code).
.. seealso::
:doc:`/applications/productivity/studio/fields`
:doc:`/applications/studio/fields`
Classic fields
**************