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:
- duplicate_a_planning.rst
- send_planned_shifts.rst
These pages document very straightforward screens and flows users can easily figure out without dedicated documentation. Besides, those screens are frequently reworked, requiring to maintain the related pages closely. This commit then removes low-value pages to reduce the technical debt and allow focusing on actually useful documentation pages.
Docs removed:
- mailing_lists.rst
- manage_unsubscriptions.rst
- send_emails.rst
These pages document very straightforward screens and flows users can easily figure out without dedicated documentation. Besides, those screens are frequently reworked, requiring to maintain the related pages closely. This commit then removes low-value pages to reduce the technical debt and allow focusing on actually useful documentation pages.
Docs removed:
- campaigns.rst
- livechat.rst
- manage_social.rst
- push_notifications.rst
These pages document very straightforward screens and flows users can easily figure out without dedicated documentation. Besides, those screens are frequently reworked, requiring to maintain the related pages closely. This commit then removes low-value pages to reduce the technical debt and allow focusing on actually useful documentation pages.
Docs deleted:
- track_talks.rst
- track_attendees.rst
- tickets.rst
- create_event.rst
- integrations.rst
* [ADD] subscriptions: add base documentation for Subscriptions
* [ADD] subscriptions/sales_flow/create_a_quotation: new content
* [ADD] subscriptions/sales_flow/renewals: new content
* [ADD] subscriptions/sales_flow/upselling: new content
* [ADD] subscriptions/sales_flow/closing: new content
* [ADD] subscriptions/reporting/subscription_reports: new content
- Update Enterprise & Partnership agreement (EN, FR)
- Update legal page index: hide outdated agreements, replace
with a link to an archive of the old PDFs.
- Add icons for missing files, to make index table layout more consistent
- Add `text-justify` on HTML versions of contracts, for consistency with
the PDF versions.
- Fix compatibility of PDF generation with recent sphinx versions
(\sphinxmaketitle instead of \maketitle)
- Re-add NL PDF building, still needs to be updated like all others
Backport of 5b80ed551c from 13.0
Because:
- Mementos are already referenced multiple times in related toctrees.
- Only two mementos are remaining, which is not enough to justify a whole doc category.
- References to mementos are easily broken without being detected at compilation time.
The new section has been named My Odoo Portal and it is a small guide about what you can find and manage from My Account page. It is accessible from Practical
