This is a long term project, following the recurring question we currently face at the support func & tech
Done in the commit:
1/ Modify the references to discuss/advanced/ to match a newly created folder
specific for email communication (more generic and not specifically linked to the discuss app)
called `email_communication`.
2/ Creation of the new folder under 'Practical Information' in the documentation/user (bottom of the page)
that will handle of the mechanism around emails, including (none exhaustive list)
1/ Modify the references to discuss/advanced/ to match a newly created folder
specific for email communication (more generic and not specifically linked to the discuss app).
2/ Creation of the new folder under 'Practical Information' in the documentation/user (bottom of the page)
that will handle of the mechanism around emails, including (none exhaustive list):
email_communication/get_started.rst > A small introduction of the content of this section Email communication
email_communication/get_helped.rst > A file that is providing reason why the emails might not be properly sent
+ contact the support and what to tell them. In order to have the quickest and best answer.
email_communication/advanced/mail_servers.rst > An explanation on how to use an outgoing mail server in Odoo.
+ how to configure SPF DKIM DMARC for Odoo.
(Not modified yet, only mv from `discuss` folder)
email_communication/advanced/email_template.rst > Contain informations about email templates
(Not modified yet, only mv from `discuss` folder)
More to come, in collaboration with GOR, EDV, JQU, ALA
task-1925363
This page documents a straightforward flow users can easily figure out without dedicated documentation. Besides, screens are frequently reworked, requiring to maintain the related page closely. This commit then removes a low-value page to reduce the technical debt and allow focusing on actually useful documentation pages.
Doc removed:
- forecast.rst
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that a user can easily figure out without the help of dedicated documentation. Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely. This commit removes such low values pages to reduce the technical debt and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that auser can easily figure out without the help of dedicated documentation.Besides, those screens are frequently reworked, thus requiring to maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
* remove reference to claim_issue removed in revision
21c4b5c3fd
* mark tex sources as orphan (they're not expected to be linked from
any TOC or other document)
* remove empty expenses.rst file (actual file is expense/expense)
* remove commmented links to deleted documents in applications TOC
* fix footnotes in partnership_es and partnership_fr
Not only is it clearly outdated, as it uses the Issue Tracking module which no longer exists, but it also undermines our Helpdesk module as it shows a way to get round it.
