[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
{%- extends "basic/layout.html" %}
|
|
|
|
|
{%- set html5_doctype = True %}
|
|
|
|
|
|
|
|
|
|
{%- block css %}
|
|
|
|
|
{{ super() }}
|
|
|
|
|
{%- if 'custom-css' in meta %} {# Allow custom css style import for specific pages #}
|
|
|
|
|
{%- set css_files = meta['custom-css'].split(',') %}
|
|
|
|
|
{%- for css_file in css_files %}
|
|
|
|
|
{%- set link = '_static/css/' + css_file %}
|
|
|
|
|
<link rel="stylesheet" href="{{ pathto(link, 1) }}" type="text/css"/>
|
|
|
|
|
{%- endfor %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
{%- endblock %}
|
|
|
|
|
|
|
|
|
|
{%- block scripts %}
|
|
|
|
|
{%- if 'custom-js' in meta %} {# Allow custom js import for specific pages #}
|
|
|
|
|
{# Before the custom files using React & Immutable (accounting mementos) #}
|
|
|
|
|
<script src="https://cdnjs.cloudflare.com/ajax/libs/immutable/3.8.2/immutable.min.js"
|
|
|
|
|
integrity="sha512-myCdDiGJRYrvRb/VuJ67ljifYTJdc1jdEvL4c4ftX9o3N6EAnmD83c/7l2/91RCINZ7c8w21tiXDT7RDFjdc3g=="
|
|
|
|
|
crossorigin="anonymous"></script>
|
|
|
|
|
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/0.13.0/react-with-addons.min.js"
|
|
|
|
|
integrity="sha512-wsnDgOxfyn4lhblRMHPMuJh+9CnLcwcisda1zLRGNWKh6OiQynebYTyRZYgH+eWLEdNTKak0OD2GAd/S51UhTw=="
|
|
|
|
|
crossorigin="anonymous"></script>
|
|
|
|
|
<script src="{{ pathto('_static/js/atom.js', 1) }}"></script>
|
|
|
|
|
{%- set js_files = meta['custom-js'].split(',') %}
|
|
|
|
|
{%- for js_file in js_files %}
|
|
|
|
|
{%- set link = '_static/js/' + js_file %}
|
|
|
|
|
<script src="{{ pathto(link, 1) }}"></script>
|
|
|
|
|
{%- endfor %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
{{ super() }} {# Load the scripts specified in the extensions/themes #}
|
2022-05-06 22:03:06 +07:00
|
|
|
{%- if plausible_script -%}
|
|
|
|
|
<script defer="defer" src="{{ plausible_script }}" data-domain="{{ plausible_domain }}"></script>
|
|
|
|
|
{%- endif -%}
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.0.0-beta2/dist/js/bootstrap.bundle.min.js"
|
|
|
|
|
integrity="sha384-b5kHyXgcpbZJO/tY9Ul7kGkf1S0CWuKcCD38l8YkeH8z8QjE0GmW1gYU5S9FOnJ0"
|
|
|
|
|
crossorigin="anonymous"></script>
|
|
|
|
|
{%- endblock %}
|
|
|
|
|
|
|
|
|
|
{%- block linktags %}
|
|
|
|
|
{%- for alternate_language, language_code, url in alternate_languages %}
|
|
|
|
|
<link rel="alternate" hreflang="{{ language_code }}" href="{{ url }}" />
|
|
|
|
|
{%- endfor %}
|
|
|
|
|
<link rel="canonical" href="{{ canonical }}" />
|
|
|
|
|
{{ super() }}
|
|
|
|
|
{%- endblock %}
|
|
|
|
|
|
|
|
|
|
{#
|
|
|
|
|
Google analytics key logic.
|
|
|
|
|
We do not want to call super here since our custom footer logic is defined in the content block.
|
|
|
|
|
#}
|
|
|
|
|
{%- block footer %}
|
|
|
|
|
{%- if google_analytics_key -%}
|
|
|
|
|
{%- include "layout_templates/google_analytics.html" %}
|
|
|
|
|
{%- endif -%}
|
|
|
|
|
{%- endblock %}
|
|
|
|
|
|
|
|
|
|
{%- block header %}
|
|
|
|
|
<noscript>
|
|
|
|
|
<nav class="o_side_nav border-end">
|
|
|
|
|
{%- include "layout_templates/menu.html" %}
|
|
|
|
|
</nav>
|
|
|
|
|
</noscript>
|
|
|
|
|
{# Shown when the JS has properly set all the classes on the TOC elements #}
|
2022-06-14 18:18:34 +07:00
|
|
|
<nav id="o_menu" class="o_side_nav">
|
|
|
|
|
<div class="o_mobile-overlay" data-bs-toggle="collapse" data-bs-target="#o_menu"></div>
|
|
|
|
|
<div class="o_side_nav-inner border-end">
|
|
|
|
|
{%- if 'hide-page-toc' not in meta %}
|
|
|
|
|
{# Shown when the JS has properly set all the classes on the TOC elements #}
|
|
|
|
|
<aside id="o_page_toc_in_nav" class="o_page_toc o_in_nav_toc border-bottom pt-3 pb-3" hidden>
|
|
|
|
|
{%- include "layout_templates/page_toc.html" %}
|
|
|
|
|
</aside>
|
|
|
|
|
{%- endif %}
|
|
|
|
|
<div id="o_main_toctree" class="o_main_toc mt-3" hidden>
|
|
|
|
|
{%- include "layout_templates/menu.html" %}
|
|
|
|
|
</div>
|
2022-06-08 16:05:14 +07:00
|
|
|
</div>
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
</nav>
|
2022-06-13 21:33:19 +07:00
|
|
|
<header class="o_headers">
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
{%- include "layout_templates/header.html" %}
|
|
|
|
|
</header>
|
|
|
|
|
{%- endblock %}
|
|
|
|
|
|
|
|
|
|
{%- block content %}
|
|
|
|
|
<div id="wrap">
|
|
|
|
|
{%- set main_classes = [] %}
|
|
|
|
|
{%- if pagename == master_doc %} {# The current page is the homepage #}
|
|
|
|
|
{%- set main_classes = main_classes + ['o_index'] %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
|
2021-06-30 16:21:32 +07:00
|
|
|
{%- if ('show-content' in meta) and ('show-toc' not in meta) %} {# The page is an accessible toctree #}
|
2021-05-26 21:48:05 +07:00
|
|
|
{%- set main_classes = main_classes + ['o_hide_toc'] %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
{%- if 'code-column' in meta %} {# The page contains a 'memento' (dynamic side block) #}
|
|
|
|
|
{%- set main_classes = main_classes + ['o_has_code_column'] %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
|
|
|
|
|
{%- if 'classes' in meta %} {# The page source defines custom classes #}
|
|
|
|
|
{%- set main_classes = main_classes + meta['classes'].split() %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
|
|
|
|
|
{%- if 'hide-page-toc' in meta %}
|
|
|
|
|
{%- set main_classes = main_classes + ['o_fullwidth_page'] %}
|
|
|
|
|
{%- endif %}
|
|
|
|
|
|
|
|
|
|
<main class="container-fluid {{ ' '.join(main_classes) }}">
|
|
|
|
|
{%- if pagename == master_doc %}
|
|
|
|
|
{# Custom landing page on the root of the documentation #}
|
|
|
|
|
{%- include "layout_templates/homepage.html" %}
|
2022-11-28 20:49:53 +07:00
|
|
|
{%- elif pagename == 'legal' %}
|
|
|
|
|
{%- include "layout_templates/legal.html" %}
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
{%- else %}
|
|
|
|
|
<article id="o_content" class="doc-body">
|
|
|
|
|
<div role="main"> {# Beacon used by the Sphinx search to know where to look for a string #}
|
|
|
|
|
{%- block body %} {%- endblock %}
|
|
|
|
|
</div>
|
2022-04-07 15:37:10 +07:00
|
|
|
{%- if github_link and pagename != 'search' and not pagename.startswith('legal') %}
|
2025-02-28 16:04:04 +07:00
|
|
|
<a href="{{ github_link(mode='_edit') }}"
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
class="o_git_link d-none d-lg-inline-block">
|
2025-02-28 16:04:04 +07:00
|
|
|
<i class="i-edit"></i> Edit on Repository
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
</a>
|
|
|
|
|
{%- endif %}
|
|
|
|
|
</article>
|
|
|
|
|
{%- endif %}
|
|
|
|
|
</main>
|
|
|
|
|
{%- if 'hide-page-toc' not in meta %}
|
2021-05-26 21:48:05 +07:00
|
|
|
{# Shown when the JS has properly set all the classes on the TOC elements #}
|
|
|
|
|
<aside id="o_page_toc" class="o_page_toc" hidden>
|
[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
2021-04-30 17:40:29 +07:00
|
|
|
{%- include "layout_templates/page_toc.html" %}
|
|
|
|
|
</aside>
|
|
|
|
|
{%- endif %}
|
|
|
|
|
</div>
|
|
|
|
|
<footer>
|
|
|
|
|
{%- include "layout_templates/footer.html" %}
|
|
|
|
|
</footer>
|
|
|
|
|
{%- endblock %}
|
