Remove the patchqueue extension from the doc requirements since it isn't
maintained anymore (raising warnings for recent sphinx versions) and the
patches to specify code blocks aren't easy to maintain.
Remove hidden code patches, and replaces shown patches by code block /
literalincludes to keep the useful content.
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
Prepare the incoming documentation refactoring, ensuring the files used by a doc page
are correcly moved together with the page, avoiding broken links during the reorganisation.
Partial backport of f7bedfce2e
to ease forward-ports
- cherry-pick of e10581ef6e (see PR #572 )
- more fields deleted so that there was none left in 12.0
--> this makes the build of 12.0 much faster
*: accounting, inventory, purchase
As these buttons points to demo.odoo.com, it is outdated very quickly
and leads to weird results were a button on the 10.0 documentation
points to demo.odoo.com that runs 13.0 or no longer exists.
documentation update as we have removed the `-c` option from
the upgrade script to provide the subscription code. Now
it is directly read from the database.
CUPS the server will never be installed on an Odoo.sh machine.
That being said you can use a remote printer with a cups client.
The problem lays in the sorry state of libcups dependencies so we will
try to get a reliable section in the documentation for 20.04 as soon as
we can get a testcase.
Meanwhile, it has been reported that the command line `lp` cups cli
client tool could be used as a workaround in the OCA concerned module:
https://gist.github.com/rm-jamotion/0453e91ff3e13350a1e46a11ebb02e8d
It's not really obvious that payments and invoices need to be fully
reconciled before their currency exchange entries get created, so this
is a warning about that.
Make explicit which permissions you need to grant in a personal access
token. I verified `repo` suffices to complete the tutorial, and I'm
assuming Odoo.sh doesn't need any of the admin and site permissions.
