e3fee2cf46
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
58 lines
2.3 KiB
ReStructuredText
58 lines
2.3 KiB
ReStructuredText
|
|
|
|
.. _support-expectations:
|
|
|
|
===========================================
|
|
What can I expect from the support service?
|
|
===========================================
|
|
|
|
|
|
5 days a week
|
|
=============
|
|
|
|
Your Odoo Online subscription includes **unlimited 24hr support at no extra
|
|
cost, Monday to Friday**. Our teams are located around the world to ensure you
|
|
have support, no matter your location. Your support representative could be
|
|
communicating to you from San Francisco, Belgium, or India!
|
|
|
|
Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__.
|
|
|
|
|
|
What kind of support is included?
|
|
=================================
|
|
|
|
- Providing you with relevant material (guidelines, product documentation,
|
|
etc...)
|
|
- Answers to issues that you may encounter in your standard Odoo database (eg.
|
|
“I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)
|
|
- Questions related to your account, subscription, or billing
|
|
- Bug resolution (blocking issues or unexpected behaviour not due to
|
|
misconfiguration or customization)
|
|
- Issues that might occur in a test database after upgrading to a newer version
|
|
|
|
*Odoo Support does not make changes to your production database, but gives you
|
|
the material and knowledge to do it yourself!*
|
|
|
|
|
|
What kind of support is not included?
|
|
=====================================
|
|
|
|
- Questions that require us to understand your business processes in order to
|
|
help you implement your database
|
|
- Training on how to use our software (we will direct you to our many resources)
|
|
- Import of documents into your database
|
|
- Guidance on which configurations to apply inside of an application or the database
|
|
- How to set up configuration models (Examples include: Inventory Routes,
|
|
Payment Terms, Warehouses, etc)
|
|
- Any intervention on your own servers/deployments of Odoo
|
|
- Any intervention on your own third party account (Ingenico, Authorize, UPS, etc)
|
|
- Questions or issues related to specific developments or customizations done
|
|
either by Odoo or a third party (this is specific only to your database or
|
|
involving code)
|
|
|
|
You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__.
|
|
With a pack, one of our consultants will analyze the way your business runs and
|
|
tell you how you can get the most out of your Odoo Database. We will handle all
|
|
configurations and coach you on how to use Odoo.
|
|
|