Commit Graph

17 Commits

Author SHA1 Message Date
KC (ksc)
a99c1cd7e1 [FIX] crm: typo in gamification doc
closes odoo/documentation#9614

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-06-03 21:00:51 +00:00
jero-odoo
fd17dcef90 [IMP] CRM: rewrite gamification config section
closes odoo/documentation#9061

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-05-02 19:14:42 +00:00
jero-odoo
3179286430 [IMP] CRM: rewrite gamification
closes odoo/documentation#8908

Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: StraubCreative <zst@odoo.com>
2024-04-26 22:37:46 +00:00
tiku-odoo
7fad040a46 [IMP] sales: partner autocomplete rewrite
closes odoo/documentation#9013

X-original-commit: 5bed8eb25b
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-26 17:18:04 +00:00
tiku-odoo
102d9fc831 [ADD] sales: crm lead enrichment
closes odoo/documentation#8912

X-original-commit: 0bd590d4b9
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Timothy Kukulka (tiku) <tiku@odoo.com>
2024-04-22 21:55:53 +00:00
jero-odoo
2c9457e573 [IMP] crm: utilize activities for sales teams 17
closes odoo/documentation#8777

Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-04-18 19:27:52 +00:00
jero-odoo
25009a9121 [IMP] CRM: utilize activities 16.0
closes odoo/documentation#8664

X-original-commit: 50a8171f02
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-04-11 13:17:00 +00:00
jero-odoo
a17117047a [ADD] crm: utilize activities for sales teams
closes odoo/documentation#8590

X-original-commit: d27def362b
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
2024-04-09 11:19:49 +00:00
lman-odoo
d0fada27d6 [FIX] partner_autocomplete: fix a typo
closes odoo/documentation#6178

X-original-commit: e24e708a14
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2023-10-19 04:31:56 +00:00
Jonathan Castillo (jcs)
ab1a7d0a69 [IMP] *: Remove "SaaS" to keep only the "Odoo Online" appellation
task-3034812

closes odoo/documentation#2839

X-original-commit: 9b69e0d77e
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
2022-10-21 20:00:56 +02:00
Jonathan Castillo (jcs)
06d0ff6ca8 [IMP] *: consistency for the use of "Odoo Online" (and SaaS)
task-3034812

X-original-commit: 2c17b6fb4a
Part-of: odoo/documentation#2839
2022-10-21 20:00:55 +02:00
Antoine Vandevenne (anv)
8722ea902e [MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.

For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:

├── parent_doc/
│     └── doc1/
│     │     └── image.png
│     │     └── download.zip
│     └── doc1.rst
│     └── doc2.rst
├── parent_doc.rst

Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.

In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.

task-2497965

Part-of: odoo/documentation#2068
2022-05-20 14:18:54 +02:00
Xavier
b8ff49a6f1 [IMP] mail plugins: add gmail plugin + update and move outlook plugin
Task ID: 2662764

closes odoo/documentation#1168

X-original-commit: debe8cb393
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2021-10-07 20:08:48 +00:00
Jonathan Castillo
193e22492c [MERGE] Forward-port of branch 13.0 to 14.0 2021-06-04 17:21:14 +02:00
Antoine Vandevenne (anv)
74c9f94d16 [MERGE] Forward-port of branch 13.0 to 14.0 2021-05-04 16:51:07 +02:00
Antoine Vandevenne (anv)
8a6ad77935 [MERGE] Forward-port of branch 12.0 to 13.0 2021-05-04 16:31:06 +02:00
Antoine Vandevenne (anv)
e3fee2cf46 [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-05-04 15:44:00 +02:00