Release notes + homepage redesign

[mnocon]

Target: master, 4.6

How to review:

Frontend:

• All the SVG, CSS, SCSS, JS, .eslintignore changes are done by @GrabowskiM and should not be reviewed

My changes:

• Added list of LTS updates in https://ez-systems-developer-documentation--2652.com.readthedocs.build/en/2652/ibexa_products/editions/
  • I believe it's a good place to mention them as it's one of the first pages which people see, LTS Updates are additional features and they can belong to different editions
• Added empty sections to the update page to make things consistent (https://ez-systems-developer-documentation--2652.com.readthedocs.build/en/2652/update_and_migration/from_4.6/update_from_4.6/)
• The homepage has been redesigned to include information about latest LTS update (and LTS updates in general)
• Added missing information for the old releases (4.6.1 - 4.6.18)
• Added Python macros so that adding new releases is more enjoyable and does not require adding any HTML tags

Adding a new release

You can add a new release as in the following example:

[[% set version = 'v4.6.11' %]] # Required if the change log snippet is used
[[= release_note_entry_begin("Ibexa DXP " + version, '2024-09-16', ['Headless', 'Experience', 'Commerce']) =]] # Required: specifes the title of the release, release date and categories. Available categories are: 'Headless', 'Experience', 'Commerce', 'LTS Update', 'New feature'

#### Section header

You can use Markdown here, as usual

[[% include 'snippets/release_46.md' %]] # Optional, generates the full change logs and update guide link. Version variable must be set to use this
[[= release_note_entry_end() =]]

Previews

• Release notes for 4.6: https://ez-systems-developer-documentation--2652.com.readthedocs.build/en/2652/release_notes/ibexa_dxp_v4.6/
• Homepage: https://ez-systems-developer-documentation--2652.com.readthedocs.build/en/2652/
• Editions (List of LTS updates): https://ez-systems-developer-documentation--2652.com.readthedocs.build/en/2652/ibexa_products/editions/

[github-actions]

Preview of modified Markdown:

• docs/ai_actions/ai_actions_guide.md
• docs/ibexa_products/editions.md
• docs/index.md
• docs/release_notes/ibexa_dxp_v4.6.md
• docs/snippets/release_46.md
• docs/update_and_migration/from_4.6/update_from_4.6.md

[dabrt]

The two tiles seem misaligned, with the LTS Updates one being slightly lower. Aalso, there is more whitespace in the LTS Update one. The "LTS Updates List" link calls for a button.

[mnocon]

Fixed alignment and height for the boxes. I'm not sure if the button is better, so I'd stick with the design here

[dabrt]

We already have a link to the release notes in line 78. How about a link to the upgrade/update instructions, like we had to date?

[mnocon]

People should go to the update instructions through the release notes first, I think it's a good order.

I've removed the link from line 79 completely - with 3 options (release notes, latest lts update, lts updates list) it's enough choice for the visitor and that link was barely visible anyway.

[dabrt]

Suggested change

	<a href="ibexa_products/editions#lts-updates">LTS Updates List</a>
	<a href="ibexa_products/editions#lts-updates">Discover other LTS Updates</a>

`
I would put it on a button, it looks lost without one

[mnocon]

Applied the text suggestion, I'd stick with the design when it comes to the button

[dabrt]

I was wondering:

1. whether we need edition pills next to each release number. Was there ever a version released for less than three editions? I'd say this is redundant information.
2. why these pills are different from the pills visible when within the article below, we should be consistent visually
3. do we need "New feature" pill if right below the pills we have the "Features" header. I'd say not, because if a version has new features, it is very well visible because their list is right below the version number.

IMVHO there's too much clutter, too many colors.

[mnocon]

1. We need them for the filters to work, and if we release an LTS update available not available for Headless then it would be useful. I'd keep it and we can revisit it in the future if needed.
2. I've discussed this with @GrabowskiM - we will align the pills visually once this is merged to keep the scope of this PR small
3. I'd keep it as it works well with filtering - you can have a quick a glance of what was added in the recent releases