[FW][ADD] tutorials/website_theme: Add tutorials to build a website theme

[fw-bot]

Add a tutorial to learn how to create a website theme Odoo16
Based on the documentation 16.0: How-to guides -> Website themes
This tutorial is illustrated by a example module: the website theme of Airproof. It will be on the GitHub repository: /tutorials.

See also:

• [ADD] website airproof: add solution for website theme tutorial tutorials#678

Forward-Port-Of: #12573

[robodoo]

[fw-bot]

@cede-odoo @AntoineVDV cherrypicking of pull request #12573 failed.

• 9f8b8e7 <- on this commit
• 2a976d4

stdout:

CONFLICT (modify/delete): content/developer/tutorials/website.rst deleted in 9f8b8e79d942a77e3948ddc2e791f43f9e841202 and modified in 5492d6e41614ea7e88e3685f9ee7fbc942e383d0.  Version 5492d6e41614ea7e88e3685f9ee7fbc942e383d0 of content/developer/tutorials/website.rst left in tree.

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[AntoineVDV]

Is there something I should review in particular?

Except for the commits that should be squashed together and rewritten to look like a proper forward-port, I don't think I need to comment on anything else as I already reviewed the original version in 16.0.

For forward-port PRs, it's up to the author to decide whether the reviewer should make a second pass, for example when significant adaptations are made. If not, they can r+ themselves.

[bram-odoo]

Is there something I should review in particular?

Except for the commits that should be squashed together and rewritten to look like a proper forward-port, I don't think I need to comment on anything else as I already reviewed the original version in 16.0.

For forward-port PRs, it's up to the author to decide whether the reviewer should make a second pass, for example when significant adaptations are made. If not, they can r+ themselves.

I don't think so, I was not sure @cede-odoo was able to r+ by herself without a new review. My bad, @AntoineVDV

[cede-odoo]

@robodoo r+

[AntoineVDV]

@robodoo r-

Could you squash the commits? 🙏

[bram-odoo]

@AntoineVDV There you go

[AntoineVDV]

This PR's commit still mentions other commits, "cherry pick failed", etc.

Its commits should rather be like in the 16.0 PR

[cede-odoo]

@robodoo r+

[robodoo]

@cede-odoo @AntoineVDV because this PR has multiple commits, I need to know how to merge it:

• merge to merge directly, using the PR as merge commit message
• rebase-merge to rebase and merge, using the PR as merge commit message
• rebase-ff to rebase and fast-forward

[cede-odoo]

@robodoo r+ rebase-ff

[robodoo]

This PR is already reviewed, reviewing it again is useless.

[robodoo]

Merge method set to rebase and fast-forward.