This commit aims to improve the documentation's navigability by
redefining some categories' purposes and titles.
There is a redirection rule for each documentation page moved.
This ensures that users won't have a 404 error message.
task-3217827
closesodoo/documentation#8056
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
task-2790245
- Update existing Google Analytics doc for GA4
- Merge GA and Plausible into one Analytics page
- Review Plausible.io instructions to adopt same style as GA instructions
closesodoo/documentation#5704
X-original-commit: 5b6be43481
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
This commit improves the structure of the accounting documentation by
- reducing the levels necessary to reach the information
- grouping some docs
- moving content to their parent category page (content in all levels)
- renaming some sections to reflect the structure of the app better
task-3330093
closesodoo/documentation#4470
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
This commit splits the 7 chapters of the JS tutorial in two
smaller and more focused tutorials:
- a basic one (Discover the JS framework)
- and an advanced one (Master the odoo web framework)
closesodoo/documentation#4243
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
The redirection rule for plausible.rst was missing from the forward-port
in PR #4107. Because of that, a link in the app leads to a 404 page
instead of the appropriate doc page. This commit fixes it.
closesodoo/documentation#4211
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
This commit improves the structure of the Subscription doc and updates
its content (recurring products, subscription plans, sales flow)
task-3222232
closesodoo/documentation#4062
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Co-authored-by: Xavier Platteau <xpl@odoo.com>
Co-authored-by: Tom Aarab <toaa@odoo.com>"
The JavaScript cheatsheet is outdated, we therefore remove it and
replace it by multiple howtos:
- Create a view from scratch
- Extending an existing view
- Create a field from scratch
- Extend an existing field
- Create a client action
There is other subjects to introduce as the web framework is big. Other
future contributions will cover them.
closesodoo/documentation#3969
Signed-off-by: Dardenne Florent (dafl) <dafl@odoo.com>
Adding a page on customer interaction and adding redirects. Forward to
master.
closesodoo/documentation#3775
Taskid: 3224716
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Adding a page on customer accounts for the eCommerce doc. Forward to
master.
closesodoo/documentation#3769
Taskid: 3223001
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
Adding a page on handling orders for the eCommerce doc, and removing
older pages. Forward to master.
closesodoo/documentation#3721
Taskid: 3214065
Signed-off-by: Aarab Tom (toaa) <toaa@odoo.com>
Adding a cross/upselling page for the ecommerce section. Forward to
master.
closesodoo/documentation#3367
Taskid: 3142720
Signed-off-by: Aarab Tom (toaa) <toaa@odoo.com>
Adding a product page for the eCommerce section, currently does not
exist. V16, forward to master.
closesodoo/documentation#3112
Taskid: 2903859
Signed-off-by: Aarab Tom (toaa) <toaa@odoo.com>
Add a new content focused on SCSS and user-interface.
- SCSS coding guidelines: regroup information already available (eg [1])
or based on "oral tradition".
The aim is not to establish new rules, ~99% of the current codebase
is already compliant.
- SCSS inheritance: explain how SCSS assets management works in odoo.
For example, people still find confusing that overrides are defined
*before* the variable to customize.
- SCSS optimization tips: suggestions to lean SCSS code. Based on SCSS
optimization task's know-how [2].
- CSS variables: explain how this feature is commonly used in odoo to
adapt layout & design without raw CSS overrides.
- UI Icons: Add link to fontAwesome4 library . Replace the picture of
odoo icons with the actual font (90kb image VS 15Kb font)
[1] https://github.com/odoo/odoo/wiki/SCSS-coding-guidelines
[2] https://www.odoo.com/web#id=2704984&menu_id=4720&cids=1&model=project.task&view_type=form
task-3090800
closesodoo/documentation#3093
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Changing the name of model payment.acquirer to payment.provider
and everything that it touches. It is technically incorrect to
use the term "acquirer" for systems that only provide a service
of payment.
After this commit the model payment.acquirer and everything
related to it will be renamed to payment.provider.
Task - 2842088
closesodoo/documentation#1981
Related: odoo/upgrade#3542
Related: odoo/odoo#90899
Related: odoo/enterprise#27131
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
The `redirects.txt` file used to specify redirect rules for renamed or
moved documentation pages is starting to grow too big to be easily
maintainable. The main reason is that the number of redirect rules that
were thought to be required has been largely underestimated when
implementing the 'redirects' extension. At first, we believed that no
guidelines or structure were necessary because only a small amount of
redirect rules would be specified. This proved wrong and the file is now
becoming a mess, making it increasingly difficult to figure out where,
why, when, and if a redirect rule is specified in the file.
As the file is versioned, another issue emerges: conflicts occur every
time a commit is forward-ported to a later version if that commit adds a
redirect rule at the end of the file or at a line that was changed in
the later version. As redirect rules are frequently added, and since
blocks of redirect rules for new versions are added at the end of the
file, this tends to happen a lot.
This commit attempts to hit two birds with one stone by splitting the
`redirects.txt` file into multiple files, one per version. While doing
so, the existing redirect rules are ordered alphabetically and moved
into contextual blocks. Instructions and guidelines on how to create
redirect rules are also listed in the `redirects/MANUAL.md` file. By
sorting the redirect rules and adding them in different files, the
number of conflicts should decrease by a lot.
task-2891912
closesodoo/documentation#2292
X-original-commit: 0417b95514
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
