[IMP] Multi: minor content changes for 19.0 #15330
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
|
Felicious
approved these changes
Nov 20, 2025
| enter a :guilabel:`UNSPSC Category`, which is a globally recognized `code managed by | ||
| GS1 <https://www.unspsc.org/>`_, that **must** be purchased in order to use. | ||
| enter a :guilabel:`UNSPSC Category`, which is a globally recognized `code managed by GS1 | ||
| <https://www.unspsc.org/>`_, that **must** be purchased in order to use. |
Contributor
There was a problem hiding this comment.
thank you for catching all the early line breaks that I and Erin missed! 😊
Comment on lines
172
to
175
| If you sell products with specific patterns, you can also add an image to display the pattern of the | ||
| product. To do so, click the :icon:`fa-camera` :guilabel:`(camera)` icon, then click the | ||
| :icon:`fa-pencil` :guilabel:`(pencil)` icon and select an image from your local drive. This pattern | ||
| will appear as a color option on the ecommerce product page. |
Contributor
There was a problem hiding this comment.
Let's remove the use of yous and make the value prop more direct, like: "businesses can attach images to product variant attribute values so customers can see on the eCommerce website, which value they want."
|
|
||
| Performance can be measured in several ways in performance plans. These are configured in the | ||
| :guilabel:`Achievements` tab of each plan. | ||
| :guilabel:`Achievements` tab of each plan. It's possible to track achievements by all products sold, |
Contributor
There was a problem hiding this comment.
Suggested change
| :guilabel:`Achievements` tab of each plan. It's possible to track achievements by all products sold, | |
| :guilabel:`Achievements` tab of each plan. It is possible to track achievements by all products sold, |
content/applications/sales/sales.rst
Outdated
|
|
||
| **Odoo Sales** is the application to run your sales process (from quotation to sales order) and | ||
| deliver and invoice what has been sold. | ||
| **Odoo Sales** is the application to run the sales process (from quotation to sales order) and |
Contributor
There was a problem hiding this comment.
Suggested change
| **Odoo Sales** is the application to run the sales process (from quotation to sales order) and | |
| The **Sales** application is used to run the sales process (from quotation to sales order) and |
content/applications/sales/sales.rst
Outdated
| **Odoo Sales** is the application to run your sales process (from quotation to sales order) and | ||
| deliver and invoice what has been sold. | ||
| **Odoo Sales** is the application to run the sales process (from quotation to sales order) and | ||
| deliver and invoice what has been sold. Any product with the **Sales** checkbox ticked on its |
Contributor
There was a problem hiding this comment.
We italicize UI items that we currently cannot see
Suggested change
| deliver and invoice what has been sold. Any product with the **Sales** checkbox ticked on its | |
| deliver and invoice what has been sold. Any product with the *Sales* checkbox ticked on its |
content/applications/sales/sales.rst
Outdated
| product form can be sold with the **Sales** app. | ||
|
|
||
| .. seealso:: | ||
| - `Odoo Tutorials: Sales Tutorials <https://www.odoo.com/slides/sales-17>`_ |
Contributor
There was a problem hiding this comment.
Suggested change
| - `Odoo Tutorials: Sales Tutorials <https://www.odoo.com/slides/sales-17>`_ | |
| - `Odoo Tutorials: Sales <https://www.odoo.com/slides/sales-17>`_ |
| (:guilabel:`bug`) icon. | ||
| To display an :ref:`availability <payment_providers/availability>` report for payment providers | ||
| and payment methods and help diagnose potential availability issues on the payment form, enable | ||
| the :ref:`developer mode <developer-mode>` and click the :icon:`fa-bug` (:guilabel:`bug`) icon. |
Contributor
There was a problem hiding this comment.
Suggested change
| the :ref:`developer mode <developer-mode>` and click the :icon:`fa-bug` (:guilabel:`bug`) icon. | |
| the :ref:`developer mode <developer-mode>` and click the :icon:`fa-bug` :guilabel:`(bug)` icon. |
we put the parentheses inside the guilabel!
Co-authored-by: Felicia Kuan <feku@odoo.com>
theRealThagomizer
force-pushed
the
19.0-multi-batch-content-alignment-thjud
branch
from
49abb04 to
a2afda9
Compare
Contributor
Author
|
@robodoo r+ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hiya, Felicia! Here's a slew of minor content changes to align our documentation with the 19.0 release. This PR has 14 minor changes across 11 pages. Beyond this, I think there will be three more PRs addressing features that aren't adequately documented, and possibly two whole new pages around setting warnings on products and eventually how the heck the customer portal works.
This version also implement feedback from auva from a now-closed branch.
This 19.0 PR can be FWP up to master.