Following the recent shift to a 4-column layout in the theme picker [1],
this commit focuses on updating a little bit the size and quality of
theme screenshot images. Providing a clearer and more visually appealing
presentation of the themes.
task-3648576
closesodoo/design-themes#758
Related: odoo/odoo#149989
Signed-off-by: Soukéina Bojabza (sobo) <sobo@odoo.com>
This commit reviews the occurrences of the numbers snippets across
the website themes, especially broken selector.
The goal of this commit is to fix potential broken xpath as wel as
fine-tune the design if needed.
task-3924624
Part-of: odoo/design-themes#822
Related: odoo/odoo#163583
Signed-off-by: Benoit Socias (bso) <bso@odoo.com>
*: theme_artists, theme_avantgarde, theme_beauty, theme_bewise,
theme_bistro, theme_bookstore, theme_buzzy, theme_clean, theme_kiddo,
theme_loftspace, theme_notes, theme_odoo_experts, theme_orchid,
theme_paptic
This commit adapts the s_product_catalog customizations since this
snippet has been redesigned in PR [1].
task-3665307
Part of task-3619705
[1]:https://github.com/odoo/odoo/pull/173507closesodoo/design-themes#833
Related: odoo/odoo#173507
Signed-off-by: Benjamin Vray (bvr) <bvr@odoo.com>
*: (anelusia, beauty, bewise, graphene, notes, yes)
This commit adapts the design of `s_company_team` for multiple themes,
based on the new Odoo 18 snippet redesign.
task-3657640
closesodoo/design-themes#844
Related: odoo/odoo#172719
Signed-off-by: Benjamin Vray (bvr) <bvr@odoo.com>
*: theme_artists, theme_beauty, theme_bewise, theme_buzzy, theme_clean,
theme_cobalt, theme_kea, theme_loftspace, theme_notes,
theme_odoo_experts, theme_paptic, theme_treehouse, theme_zap
This commit adapts the s_color_blocks_2 customizations since this
snippet has been redesigned in PR [1].
task-3665302
Part of task-3619705
[1]: https://github.com/odoo/odoo/pull/173461closesodoo/design-themes#834
Related: odoo/odoo#173461
Signed-off-by: Soukéina Bojabza (sobo) <sobo@odoo.com>
This commit aims to review all the occurrences of the `s_text_cover`
snippet across the themes in order to fix broken selectors.
task-3665300
Part-of: odoo/design-themes#827
Related: odoo/odoo#172725
Signed-off-by: Benoit Socias (bso) <bso@odoo.com>
This commit aims to review all the occurrences of the `s_cover`
snippet across the themes in order to fix broken selectors.
task-3665300
Part-of: odoo/design-themes#827
Related: odoo/odoo#172725
Signed-off-by: Benoit Socias (bso) <bso@odoo.com>
Following the change in the way of dragging and dropping a snippet onto
the page (by selecting it from a dialog displaying the actual previews
of snippets). The themes tours have been adapted to this change in this
commit.
task-3919405
closesodoo/design-themes#817
Related: odoo/odoo#166967
Related: odoo/enterprise#66150
Signed-off-by: Robin Lejeune (role) <role@odoo.com>
In order to simplify the tours API, it was decided to remove the
extra_trigger key from the steps.
To check that an element is in the DOM, simply create a step with
a trigger.
task~3974087
closesodoo/design-themes#816
Related: odoo/odoo#171309
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit removes the overrides of scss variables that are set to the
default value and duplicated overrides.
task-2463604
closesodoo/design-themes#768
Signed-off-by: Outagant Mehdi (mou) <mou@odoo.com>
To make sure the required primary templates have been generated from
the theme's manifest when inherited views are imported/updated, this
commit triggers their generation from a first imported XML file.
This has been added to all themes for consistency, even the ones that
do not require it currently.
Related to https://github.com/odoo/odoo/pull/148443
task-3670496
X-original-commit: 22abe61eaf
Part-of: odoo/design-themes#761
Steps to reproduce
==================
Run the `test_02_homepage_tour_every_theme` tour.
Cause of the issue
==================
There is an homepage tour for every theme. Since the owl conversion of
web_tour, none of the custom theme tour were run and for every website,
the default homepage tour was used instead.
Some updates to those themes caused the tours to fail, but since they
weren't run, no one noticed.
The issue has been fixed in community:
https://github.com/odoo/odoo/pull/142350
Solution
========
Since 1aa6700c98,
some h1 tags were replaced by h2.
Since 68c68740bf,
The banner has been replaced by a text cover.
opw-3595512
X-original-commit: 2e263a4f6b
Part-of: odoo/design-themes#746
Given that the duplicate and conflicting classes resolved by the
previous commit did still exist at the time new page templates were
introduced in [1], they could not be avoided for new page templates
snippets.
This commit removes those from the new page templates snippets now that
they have been removed from the base snippets.
[1]: https://github.com/odoo/design-themes/commit/80cbee66f6bb4d897dd7e577f1109c75f6f6ad74
task-3562147
X-original-commit: 9984745d3d
Part-of: odoo/design-themes#744
In [1] all shapes were moved from the base snippet to the specific
configurator snippet. This was a bit overkill.
This commit reverts this partially so that only shapes that connect
with each other are specific to the configurator, but "intra-block"
shapes are restored onto the base snippet.
The "New page from template" snippets are adapted accordingly in order
to produce the same output as before this commit.
Restored shapes are: (label (image))
- Origins: 12 (18)
- Blob: 11 (11)
- Airy: 03 (03_001), 04 (04_001), 07 (07), 10 (10), 11 (11), 14 (14)
- Zigs: 01 (01_001), 02 (02_001)
- Wavy: 04 (10), 15 (11)
- Blocks: 02 (01_001)
- Rainy: 03 (06), 05 (10), 09 (08_001), 10 (09_001)
- Floats: all
[1]: https://github.com/odoo/design-themes/commit/d206c119720d557c11320ebb3d7339890b8f9efa
task-3555325
closesodoo/design-themes#726
Related: odoo/odoo#138748
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
This commit customizes all New Page template designs for every single
theme.
The changes are organized as follow:
When the used blocks are not the default ones:
- the new sequence of block is listed in the `new_page_templates`
manifest entry.
- the blocks are updated in the `new_page_template_sections_..._...`
XML templates accordingly.
After the potential block sequence updates, the `new_page_template.xml`
then first contains the general customization of blocks (those that
apply across all new page templates) then the customization for each
category of page.
Customizations for a specific page are directly below category-wide
customizations of the given block when both exist.
task-3381714
closesodoo/design-themes#692
Related: odoo/odoo#126719
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Co-authored-by: Benoit Socias <bso@odoo.com>
Co-authored-by: Arthur Detroux (ard) <ard@odoo.com>
This commit extracts the pre-defined section shapes from blocks into
templates that are dedicated to being used by the configurator.
For blocks that are not used in configurator pages, the configurator
templates have not been created.
task-3381714
Part-of: odoo/design-themes#692
The new text_cover snippet introduced in commit [1] reproduces the same
result as the Anelusia banner. It makes more sense to use now this new
snippet and get rid of the banner customizations.
This commit removes banner customizations in favor of text_cover
snippet.
As the text_cover snippet is not yet managed in the svg preview, this
snippet uses the banner image.
[1]: https://github.com/odoo/odoo/commit/5ac340b1b27c9527463e2eed65fe2e7768b36702
task-3097005
Part-of: odoo/design-themes#687
*: anelusia, artists, aviato, graphene, kiddo, loftspace, monglia,
notes, odoo_experts, paptic, test_custo, yes
The community PR [125824] introduces an automatic check on buttons to
add the `mb-2` class when several buttons follow each other, so that
they have space to breathe when split on multiple lines.
For consistency, this commit therefore removes most `mb-2` occurrences
on buttons within themes as long as they are alone on their line, but
keeps or adds the class when several buttons are next to each other.
[125824]: https://github.com/odoo/odoo/pull/125824
task-3369604
closesodoo/design-themes#680
Related: odoo/odoo#125824
Signed-off-by: Benjamin Vray (bvr) <bvr@odoo.com>
As steps are encapsuled in an arrow function from
69a5d8e3ce47238 for steps tour definition to avoid
direct Markup(_t()) interpretation, the same is done
for registerWebsitePreviewTour() of
"odoo/addons/website/static/src/js/tours/tour_utils.js"
in this commit.
This is done in anticipation of the use of
_t() (import from @web/core/l10n/translation) with
registerWebsitePreviewTour().
task-3292454
closesodoo/design-themes#678
Related: odoo/odoo#130248
Signed-off-by: Luca Vitali (luvi) <luvi@odoo.com>
Before this commit, if a theme wanted to define a main font for their
theme and let the "headings", "navbar" and "buttons" ones use the same
they had to add this in their map:
```
'font': XXX,
'headings-font': null,
'navbar-font': null,
'button-font': null,
```
Indeed, without setting the "null" values, those font would use YYY
which is the first font defined in the theme config, which might be
different from XXX. And if forcing XXX 4 times, like most themes do at
the moment, if the user wanted to change them all, he had to change the
4 ones instead of the main one.
Now, only the 'font' value use the first font defined in the theme
config if not explicitly set. So forcing the null values is not
necessary, it will be the default behavior.
The advantage is thus also functional, as most theme forced all their 4
fonts so changing the main one did not change the others.
task-2993054
closesodoo/design-themes#593
X-original-commit: fc64bce81e
Related: odoo/odoo#101068
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
> Media query mixins parameters have changed for a more logical approach
> media-breakpoint-down() uses the breakpoint itself instead of the next
> breakpoint (e.g., media-breakpoint-down(lg) instead of
> media-breakpoint-down(md) targets viewports smaller than lg).
> Similarly, the second parameter in media-breakpoint-between() also
> uses the breakpoint itself instead of the next breakpoint (e.g.,
> media-between(sm, lg) instead of media-breakpoint-between(sm, md)
> targets viewports between sm and lg).
https://getbootstrap.com/docs/5.1/migration/#sass
Task ID: 2766483
Part-of: odoo/design-themes#580
This commit fixes the "Contact" header and the "default" header that
were not displaying correctly (in related themes) in the web editor
panel as expected.
task-2713578
closesodoo/design-themes#557
X-original-commit: f403f252bc
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
See [1], `enable_view()` is now in charge of disabling the already possibly
existing template header (and/or footer).
Disabling `website.template_header_default` was not enough, any of the other
template could have been selected by the user before updating the theme.
Note that when installing a theme the first time on a website, the error won't
occur as `_reset_default_config()` will be called through `_theme_remove()`.
[1]: https://github.com/odoo/odoo/pull/81181
Fixes https://github.com/odoo/upgrade/pull/3048
task-2593407
opw-2680866
opw-2685951
opw-2685124
opw-2679040
closesodoo/design-themes#548
X-original-commit: 9a289ea574
Related: odoo/odoo#81953
Signed-off-by: Romain Derie (rde) <rde@odoo.com>
In Safari (14+) the CSS workaround to make block "readable" over any bg
is broken. By replacing the current CSS workaround by an appropriate
SVG filter in each themes svg, the problem will be fixed.
This commit will add the svg filter.
task-2667028
closesodoo/design-themes#538
X-original-commit: 545cf002ea
Related: odoo/odoo#81190
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
This commit injects for each theme a "preferred" palette into the
website's UI palette list ("Theme" tab).
It also removes '$o-palette-priority-prefix' overrides, letting website
handling the palettes order.
task-2656337
closesodoo/design-themes#514
X-original-commit: 0539787e23
Related: odoo/odoo#77857
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Many themes were overriding the yiq threshold, thus having an impact
on which of the dark or light text is used over a particuler background
by default. This is a tricky value to change and only made some sense
when the Odoo themes were defining their own color palettes. Now that
all palettes can be used in all themes, it makes no sense to change the
yiq threshold as it induces inconsistent behavior for a same palette
used in different themes. Besides, leaving the value by default is most
of the time what you want and when it is not entirely correct, the user
has full control over the color combination text colors anyway.
task-2655730
closesodoo/design-themes#507
X-original-commit: f244035809
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Xavier Morel