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
* for coda, ofx & qif: the pages using those files do not exist anymore
(cf #569)
* for the vendor pricelist csv, the files was moved into its folder of
use (in another commit)
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
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
The current certificates for demo in the documentation will to expire
the October 21. For this reason were updated by new files.
The new CSD files need to stamp with the VAT ``EKU9003173C9``.
Both values are updated.
Closesodoo/documentation-user#771
* [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
`\sphinxmaketitle` only exists as of v1.8.3, and `\renewcommand` would
crash when the command is not defined. Similarly `\newcommand` would
crash if the command already exists.
`\providecommand` acts as a shim: no-op if the command exists,
otherwise creates it so that it can be redefined.
Backport of 54e7ed30ac
`\sphinxmaketitle` only exists as of v1.8.3, and `\renewcommand` would
crash when the command is not defined. Similarly `\newcommand` would
crash if the command already exists.
`\providecommand` acts as a shim: no-op if the command exists,
otherwise creates it so that it can be redefined.
- 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
- 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
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.
- Removed the doc version and absolute path from all user doc redirections.
- Made developer doc redirections use 13.0 instead of online, master or earlier version string.
- Fixed outdated links.
- Enforced the use of :doc:, :ref: and :download: directives for redirections.
- Replaced google drive/docs links by doc redirections.
Sections get an id automatically generated from the title, "journal
entries" and "chart of accounts" are pretty generic concepts, so the
widgets looking for these ids can get enabled on sections they're not
intended to live in.
On the other hand, Sphinx is not likely to generically create classes
for these concepts without being explicitly prompted (via
e.g. rst-class).
