@kitconcept/volto-light-theme 3.1.2 → 3.2.0

package/.yarnrc.yml

@@ -1,3 +0,0 @@
-nodeLinker: node-modules
-
-yarnPath: .yarn/releases/yarn-3.2.3.cjs

package/Makefile

@@ -1,174 +0,0 @@
-# Yeoman Volto App development
-
-### Defensive settings for make:
-#     https://tech.davis-hansson.com/p/make/
-SHELL:=bash
-.ONESHELL:
-.SHELLFLAGS:=-eu -o pipefail -c
-.SILENT:
-.DELETE_ON_ERROR:
-MAKEFLAGS+=--warn-undefined-variables
-MAKEFLAGS+=--no-builtin-rules
-
-CURRENT_DIR:=$(shell dirname $(realpath $(lastword $(MAKEFILE_LIST))))
-
-# Recipe snippets for reuse
-
-# We like colors
-# From: https://coderwall.com/p/izxssa/colored-makefile-for-golang-projects
-RED=`tput setaf 1`
-GREEN=`tput setaf 2`
-RESET=`tput sgr0`
-YELLOW=`tput setaf 3`
-
-PLONE_VERSION=6
-VOLTO_VERSION=17.15.5
-
-ADDON_NAME='@kitconcept/volto-light-theme'
-ADDON_PATH='volto-light-theme'
-COMPOSE_FILE=dockerfiles/docker-compose.yml
-ACCEPTANCE_COMPOSE=acceptance/docker-compose.yml
-ACCEPTANCE_COMPOSE_A11Y=acceptance/docker-compose-a11y.yml
-CMD=CURRENT_DIR=${CURRENT_DIR} ADDON_NAME=${ADDON_NAME} ADDON_PATH=${ADDON_PATH} VOLTO_VERSION=${VOLTO_VERSION} PLONE_VERSION=${PLONE_VERSION} docker compose
-DOCKER_COMPOSE=${CMD} -p ${ADDON_PATH} -f ${COMPOSE_FILE}
-DEV_COMPOSE=COMPOSE_PROFILES=dev ${DOCKER_COMPOSE}
-LIVE_COMPOSE=COMPOSE_PROFILES=dev ${DOCKER_COMPOSE}
-ACCEPTANCE=${CMD} -p ${ADDON_PATH}-acceptance -f ${ACCEPTANCE_COMPOSE}
-ACCEPTANCE_A11Y=${CMD} -p ${ADDON_PATH}-acceptance -f ${ACCEPTANCE_COMPOSE_A11Y}
-
-.PHONY: build-backend
-build-backend: ## Build
-	@echo "$(GREEN)==> Build Backend Container $(RESET)"
-	${DEV_COMPOSE} build backend
-
-.PHONY: start-backend
-start-backend: ## Starts Docker backend
-	@echo "$(GREEN)==> Start Docker-based Plone Backend $(RESET)"
-	${DEV_COMPOSE} up backend -d
-
-.PHONY: stop-backend
-stop-backend: ## Stop Docker backend
-	@echo "$(GREEN)==> Stop Docker-based Plone Backend $(RESET)"
-	${DEV_COMPOSE} stop backend
-
-.PHONY: build-live
-build-live: ## Build Addon live
-	@echo "$(GREEN)==> Build Addon development container $(RESET)"
-	${LIVE_COMPOSE} build addon-live
-
-.PHONY: build-addon
-build-addon: ## Build Addon dev
-	@echo "$(GREEN)==> Build Addon development container $(RESET)"
-	${DEV_COMPOSE} build addon-dev
-
-.PHONY: start-dev
-start-dev: ## Starts Dev container
-	@echo "$(GREEN)==> Start Addon Development container $(RESET)"
-	${DEV_COMPOSE} up addon-dev backend
-
-.PHONY: start-live
-start-live: ## Starts Dev container
-	@echo "$(GREEN)==> Start Addon Development container $(RESET)"
-	${DEV_COMPOSE} up addon-live backend
-
-.PHONY: dev
-dev: ## Develop the addon
-	@echo "$(GREEN)==> Start Development Environment $(RESET)"
-	make build-backend
-	make start-backend
-	make build-addon
-	make start-dev
-
-.PHONY: help
-help:		## Show this help.
-	@echo -e "$$(grep -hE '^\S+:.*##' $(MAKEFILE_LIST) | sed -e 's/:.*##\s*/:/' -e 's/^\(.\+\):\(.*\)/\\x1b[36m\1\\x1b[m:\2/' | column -c2 -t -s :)"
-
-## Setup the local environment
-.PHONY: install
-install: ## Install the local environment, Cypress, build acceptance containers
-	yarn
-	make install-acceptance
-
-# Dev Helpers
-.PHONY: i18n
-i18n: ## Sync i18n
-	@echo "$(YELLOW)==> Do not forget to setup the local environment (make install) $(RESET)"
-	yarn i18n
-
-.PHONY: format
-format: ## Format codebase
-	${DEV_COMPOSE} run --rm addon-dev lint:fix
-	${DEV_COMPOSE} run --rm addon-dev prettier:fix
-	${DEV_COMPOSE} run --rm addon-dev stylelint:fix
-
-.PHONY: lint
-lint: ## Lint Codebase
-	${DEV_COMPOSE} run --rm addon-dev lint
-	${DEV_COMPOSE} run --rm addon-dev prettier
-	${DEV_COMPOSE} run --rm addon-dev stylelint --allow-empty-input
-
-.PHONY: test
-test: ## Run unit tests
-	${DEV_COMPOSE} run --rm addon-dev test --watchAll
-
-.PHONY: test-ci
-test-ci: ## Run unit tests in CI
-	${DEV_COMPOSE} run -e CI=1 addon-dev test
-
-## Acceptance
-.PHONY: install-acceptance
-install-acceptance: ## Install Cypress, build acceptance containers
-	(cd acceptance && yarn)
-	${ACCEPTANCE} --profile dev --profile prod build
-
-.PHONY: start-test-acceptance-server
-start-test-acceptance-server: ## Start acceptance server (for use it in while developing)
-	${ACCEPTANCE} --profile dev up
-
-.PHONY: start-test-acceptance-server-prod
-start-test-acceptance-server-prod: ## Start acceptance server in prod (used by CI)
-	${ACCEPTANCE} --profile prod up -d
-
-.PHONY: test-acceptance
-test-acceptance: ## Start Cypress (for use it while developing)
-	(cd acceptance && ./node_modules/.bin/cypress open --config specPattern='cypress/tests/main/**/*.{js,jsx,ts,tsx}')
-
-.PHONY: test-acceptance-headless
-test-acceptance-headless: ## Run cypress tests in CI
-	(cd acceptance && ./node_modules/.bin/cypress run)
-
-.PHONY: stop-test-acceptance-server
-stop-test-acceptance-server: ## Stop acceptance server (for use it while finished developing)
-	${ACCEPTANCE} --profile dev down
-
-.PHONY: status-test-acceptance-server
-status-test-acceptance-server: ## Status of Acceptance Server (for use it while developing)
-	${ACCEPTANCE} ps
-
-.PHONY: start-test-acceptance-server-a11y
-start-test-acceptance-server-a11y: ## Start a11y acceptance server (for use it in while developing)
-	${ACCEPTANCE_A11Y} --profile dev up
-
-.PHONY: stop-test-acceptance-server-a11y
-stop-test-acceptance-server-a11y: ## Stop a11y acceptance server (for use it while finished developing)
-	${ACCEPTANCE_A11Y} --profile dev down
-
-.PHONY: test-acceptance-a11y
-test-acceptance-a11y: ## Start Cypress (for use it while developing)
-	(cd acceptance && CYPRESS_a11y=1 ./node_modules/.bin/cypress open --config specPattern='cypress/tests/a11y/**/*.{js,jsx,ts,tsx}')
-
-.PHONY: debug-frontend
-debug-frontend:  ## Run bash in the Frontend container (for debug infrastructure purposes)
-	${DEV_COMPOSE} run --entrypoint bash addon-dev
-
-.PHONY: pull-backend-image
-pull-backend-image:  ## Pulls and updates the backend image (for use it while developing)
-	docker pull ghcr.io/kitconcept/voltolighttheme:latest
-
-.PHONY: release
-release:  ## Release a version of the add-on
-	yarn release
-
-.PHONY: release-rc
-release-rc:  ## Release a RC version of the add-on
-	npx release-it --preRelease=rc

package/README.md

@@ -1,453 +0,0 @@
-# Volto Light Theme by kitconcept
-
-[![NPM](https://img.shields.io/npm/v/@kitconcept/volto-light-theme.svg)](https://www.npmjs.com/package/@kitconcept/volto-light-theme)
-[![Build Status](https://github.com/kitconcept/volto-light-theme/actions/workflows/code.yml/badge.svg)](https://github.com/kitconcept/volto-light-theme/actions)
-[![Build Status](https://github.com/kitconcept/volto-light-theme/actions/workflows/unit.yml/badge.svg)](https://github.com/kitconcept/volto-light-theme/actions)
-[![Build Status](https://github.com/kitconcept/volto-light-theme/actions/workflows/acceptance.yml/badge.svg)](https://github.com/kitconcept/volto-light-theme/actions)
-
-![kitconcept GmbH](https://github.com/kitconcept/volto-blocks/raw/master/kitconcept.png)
-
-## Vision
-
-The main vision of the Volto Light Theme is to serve as a foundation for kitconcept's future projects, following the release of Plone 6.
-
-It contains the feedback from the company's last years projects and the success stories in the UI/UX side.
-
-It aims to be future proof, so it has to be aligned with the upcoming Volto vision in terms of theming strategy decided by the Plone community.
-
-![Volto-Light-Theme](https://github.com/kitconcept/volto-light-theme/raw/main/volto-light-theme.png)
-
-## Requirements and specs
-
-### It should not use any SemanticUI component or styling
-
-Volto will abandon SemanticUI as default design component system in the mid term, and we should be prepared for it.
-
-We will achieve that by not using any SemanticUI component, nor any related styling (`.ui.XXX`) in our upcoming themes.
-
-The Volto strategy is:
-
-- Provide a very basic and structural Vanilla components to build upon theming and CMSUI as well (`@plone/components`)
-- These components will be based in a headless component system [React Aria Components](https://react-spectrum.adobe.com/react-aria/components.html)
-- Volto projects can be themed using `@plone/components` as baseline or use a complete different design or component system of the developer/integrator choice. The presence of Volto's component registry system could help for adapting, if required.
-
-#### Volto components `customizations` use case
-
-If possible, we will switch to SemanticUI-less components when `@plone/components` is ready.
-Specially if the elements that we are customizing are clearly "theme" (eg. header/footer, etc).
-In the case of other Volto customizations that are not clear part of the theme (eg. Search block), it's fine to stick using what the original is using (SemanticUI).
-When Volto will make the switch in the future, we should then adapt all the customizations to match the one in the Volto core.
-The approach used is to use a proxy to a component of the `components` folder. This way it's easier to keep track of changes, and another add-on can customize again the light theme component, not the original Volto customization.
-
-### It should use kitconcept's layout used in FZJ/DLR projects
-
-Since FZJ/DLR projects we've been trying a new concept in layout for Volto. This new layout uses three widths for the content elements:
-
-- Narrow (text)
-- Default (blocks)
-- Layout (main screen elements like Header, Footer)
-
-The Layout sized elements snap to 1440px. The breakpoints are also different than default Volto.
-
-This new layout uses mixin's and CSS that can be found in `layout.less` in the theme folder.
-
-Since the new container queries spec is out, we will be introducing it to the current CSS in order to implement the complexities that the "inner container" (the one between the toolbar and the sidebar) width presents. Until now, we did complex calculations given into account if the size of the inner container depending if the toolbar, the sidebar, or both were presents. With container queries we can do that in a more sensible and easy way.
-
-### Organization of the files
-
-We will start organising the files in the root of `theme` folder, to differentiate from a normal "SemanticUI" theme. Take a look at the current state. We will follow this convention:
-
-- One file per component/block
-- Use the Volto theme facility using the SCSS scape hatch provided so other add-ons can hook to it.
-- The styling is centralized in `main.scss`, the rest of the files are loaded from there.
-
-## Why a headless component system?
-
-https://medium.com/@nirbenyair/headless-components-in-react-and-why-i-stopped-using-ui-libraries-a8208197c268
-
-## Vertical spacing block model
-
-This theme has the concept of block "grouping" given two consecutive blocks with the same styling block wrapper property `backgroundColor`. You have to add this property to your blocks in your blocks code. This add-on customizes `RenderBlocks.jsx` component in order to do so.
-
-The wrappers have the classnames `blocks-group-wrapper` and the name of the background color, eg. `grey`, defaulting to `transparent` if no `backgroundColor` property is set in the styling block wrapper in the block.
-
-**Disclaimer**: This might change in the near future, since we are developing a new integral Block Model for VLT and Volto.
-
-### Vertical spacing rules
-
-These main rules spec applies to the theme:
-
-- On each change of color, a vertical padding (both `padding-bottom` and `padding-top`) of `80px` defined with the main variable `$color-block-change-vertical-spacing`.
-- The default bottom margin is defined with the main variable `$block-vertical-space` and set by default to `25px`.
-- [grid] Vertical spacing for grids should be `80px` for both top and bottom, even if the previous and next blocks are of the same color.
-- [grid+grid] When two grids happen side by side and are of the same color. It should be equal to the grid gap, so it's set to `@gutterWidth` and currently `1rem`. It has to be adjusted with a bit of negative margin to cancel the current inner padding in grid cells.
-- [grid+grid] Grids columns belonging to the same grid and same color in small mobile viewports. They should be closer to match the other adjacent ones, so they seem to belong to the same grid set.
-- [footer] The footer has a top vertical spacing of `80px`.
-- [teasers] The last teaser, except if the following is a button, does NOT have a line at the bottom.
-- [listing] The last listing, except if the following is a button, does NOT have a line at the bottom.
-- [listing] After two consecutive listings, the vertical spacing should be `200px`.
-- [text+button] If there's a text and a button, then the vertical spacing betweeen them is `60px`.
-- [image+separator-block] If after image comes a separator block, the vertical spacing between them is `40px`.
-
-### Media queries vs container queries
-
-We use media queries when the styling it's generic enough to apply only to the View.
-
-We use container queries when do care explicitly about how the styling is being applied in edit mode as well and we want the content area to behave 1:1 with the view mode.
-
-Reason: The container queries allow us to abstract the width from the sidebar and toolbar in edit mode, showing the content area as it will be in that size, in view mode.
-
-**Remember**: The margins in responsive are being taken care with container queries in `layout.scss`. So everything related to that, goes like it works in there, with container queries. See implementations for details in case you need it.
-
-## Specification
-
-`@kitconcept/volto-light-theme` works with the following Plone Blocks:
-
-- Grid-Block (https://www.npmjs.com/package/@kitconcept/volto-blocks-grid)
-- Teaser-Block (https://www.npmjs.com/package/@kitconcept/volto-blocks-grid)
-- Slider-Block (https://www.npmjs.com/package/@kitconcept/volto-slider-block)
-- Button-Block (https://www.npmjs.com/package/@kitconcept/volto-button-block)
-- Separator-Block (https://www.npmjs.com/package/@kitconcept/volto-separator-block)
-- Heading-Block (https://www.npmjs.com/package/@kitconcept/volto-heading-block)
-- Introduction-Block (https://www.npmjs.com/package/@kitconcept/volto-introduction-block)
-- Accordion-Block (https://www.npmjs.com/package/@eeacms/volto-accordion-block)
-
-and the following add-ons:
-
-- DSGVO-Banner (https://www.npmjs.com/package/@kitconcept/volto-dsgvo-banner)
-
-## Installation
-
-It is recommended that your project or policy add-on `package.json` include the aforementioned add-ons.
-
-```json
-  "dependencies": {
-    "@eeacms/volto-accordion-block": "^10.4.0",
-    "@kitconcept/volto-button-block": "^2.3.1",
-    "@kitconcept/volto-dsgvo-banner": "^1.3.0",
-    "@kitconcept/volto-heading-block": "^2.4.0",
-    "@kitconcept/volto-highlight-block": "^3.0.0",
-    "@kitconcept/volto-introduction-block": "^1.0.0",
-    "@kitconcept/volto-separator-block": "^4.0.0",
-    "@kitconcept/volto-slider-block": "^6.0.0",
-    "@kitconcept/volto-light-theme": "^2.0.0",
-  }
-```
-
-This theme won't install them for you, as they are declared as `peerDependencies`.
-This is because the theme won't have to force you to use any specific add-on version, and avoids package hoisting issues.
-
-In your project or policy add-on `package.json` you should declare all of them as Volto add-ons
-
-```json
-  "addons": [
-    "@eeacms/volto-accordion-block",
-    "@kitconcept/volto-button-block",
-    "@kitconcept/volto-heading-block",
-    "@kitconcept/volto-introduction-block",
-    "@kitconcept/volto-highlight-block",
-    "@kitconcept/volto-separator-block",
-    "@kitconcept/volto-light-theme",
-    "your_policy_addon_here"
-  ],
-```
-
-Make sure your policy add-on is the last one, as you would want that its configuration has priority over all the others. Make sure also that `@kitconcept/volto-light-theme` is the one before your policy add-on.
-
-Then, declare the theme in your project `package.json`:
-
-```json
-  "theme": "@kitconcept/volto-light-theme",
-```
-
-Alternatively, you can also declare it in your project's `volto.config.js`:
-
-```js
-const addons = [];
-const theme = '@kitconcept/volto-light-theme';
-
-module.exports = {
-  addons,
-  theme,
-};
-```
-
-You can specify your project add-ons in `volto.config.js`, but sometimes is better to have them all in one place (in your policy add-on) for portability.
-
-## Feature Flags
-
-### Enable Fat Menu
-
-Since 2.0.0, the light theme has a fat menu (below the main site sections) triggered clickin on one of them.
-It's behind a feature flag, as opt-out:
-
-```js
-config.settings.enableFatMenu = true;
-```
-
-### Show Site Label
-
-If you want to show a label on top of site you can pass label name to `siteLabel` property.
-
-```js
-config.settings.siteLabel = 'Plone Intranet';
-```
-
-If you wanted a translated label then you have to define a translation object in `defineMessages` function provided by react-intl.
-
-Here is the code snippets you have to add in your addon index.js file.
-If you don't have addon, you can also add in your config.js file in root of your frontend folder.
-
-```js
-import { defineMessages } from 'react-intl';
-
-defineMessages({
-  siteLabel: {
-    id: 'siteLabel',
-    defaultMessage: ' ',
-  },
-});
-
-```
-Then add the translation you want in your `locale` file.
-
-### Show intranetHeader
-
-We have totally different header for intranet sites. If you want that, you can enable it by passing `intranetHeader` property.
-
-```js
-config.settings.intranetHeader = true;
-```
-## Releases
-
-The releases follow a semantic versioning model.
-
-### Definition of breaking change
-
-In general, the same rules as Volto releases applies.
-However, in VLT we add an extra exception: The vertical spacing is carefully curated and considered an important feature of the theme and because of that, changes and improvements in the vertical spacing are **NOT** considered breaking changes.
-They will be noted properly in the changelog.
-
-## Upgrade Guide
-
-See a detailed upgrade guide in: https://github.com/kitconcept/volto-light-theme/blob/main/UPGRADE-GUIDE.md
-
-## Development Setup
-
-This theme works under Volto 17 alpha 16 onwards.
-Compatibility with Volto 16 might be achieved, but it has to be at customization level in the
-specific project add-on.
-This is mainly due to the `RenderBlocks` customization that is based in the one in 17 because of the Grid block in core and the autogrouping feature.
-See more information about the other dependencies in `peerDependencies` in `package.json`.
-It is possible to develop this add-on using docker containers and the provided convenience Makefile commands.
-Run `make help` to list the available commands.
-
-````text
-    build-backend                       Build
-    start-backend                       Starts Docker backend
-    stop-backend                        Stop Docker backend
-    build-live                          Build Addon live
-    build-addon                         Build Addon dev
-    start-dev                           Starts Dev environent container
-    start-live                          Starts Live environment container
-    dev                                 Develop the addon
-    help                                Show this help.
-    i18n                                Sync i18n
-    format                              Format codebase
-    lint                                Lint Codebase
-    test                                Run unit tests
-    test-ci                             Run unit tests in CI
-    install-acceptance                  Install Cypress, build acceptance containers
-    start-test-acceptance-server        Start acceptance server (for use it in while developing)
-    start-test-acceptance-server-prod   Start acceptance server in prod (used by CI)
-    test-acceptance                     Start Cypress (for use it while developing)
-    test-acceptance-headless            Run cypress tests in CI
-    stop-test-acceptance-server         Stop acceptance server (for use it while finished developing)
-    status-test-acceptance-server       Status of Acceptance Server (for use it while developing)
-    debug-frontend                      Run bash in the Frontend container (for debug infrastructure purposes)
-    pull-backend-image                  Pulls and updates the backend image (for use it while developing)
-````
-
-### Prerequisites
-
-- Docker
-- Node 18 (e.g. via nvm)
-
-### Development Environment Setup
-
-Run once
-
-```shell
-make dev
-```
-
-which will build and launch the backend and frontend containers.
-There's no need to build them again after doing it the first time unless something has changed from the container setup.
-
-To make the local IDE play well with this setup, it is required to run `yarn` once to install the required packages (ESlint, Prettier, Stylelint).
-
-Run
-
-```shell
-yarn
-```
-
-### Build the containers manually
-
-Run
-
-```shell
-make build-backend
-make build-addon
-```
-
-## Run the containers
-
-Run
-
-```shell
-make start-dev
-```
-
-This will start both the frontend and backend for the dev environment containers.
-
-
-### Stop Backend (Docker)
-
-After developing, the backend stops automatically. However, it can be stopped by running:
-
-Run
-
-```shell
-make stop-backend
-```
-
-### Linting
-
-Run
-
-```shell
-make lint
-```
-
-### Formatting
-
-Run
-
-```shell
-make format
-```
-
-### i18n
-
-Run
-
-```shell
-make i18n
-```
-
-### Unit tests
-
-Run
-
-```shell
-make test
-```
-
-### Acceptance tests
-
-Run once
-
-```shell
-make install-acceptance
-```
-
-For starting the servers
-
-Run
-
-```shell
-make start-test-acceptance-server
-```
-
-The frontend is run in dev mode, so development while writing tests is possible.
-
-Run
-
-```shell
-make test-acceptance
-```
-
-To run Cypress tests afterward.
-
-When finished, don't forget to shutdown the backend server.
-
-```shell
-make stop-test-acceptance-server
-```
-
-### Accessibility Acceptance tests
-
-Run once
-
-```shell
-make install-acceptance
-```
-
-For starting the servers
-
-Run
-
-```shell
-make start-test-acceptance-server-a11y
-```
-
-The frontend is run in dev mode, so development while writing tests is possible.
-
-Run
-
-```shell
-make test-acceptance-a11y
-```
-
-To run Cypress tests afterwards.
-
-When finished, don't forget to shutdown the backend server.
-
-```shell
-make stop-test-acceptance-server-a11y
-```
-
-### Live mode
-
-There is an alternate Docker Compose configuration for running volto in live mode.
-This is not usually needed during development, but can be useful for debugging.
-
-To build the frontend for the live environment, run
-
-```shell
-make build-live
-```
-
-To start both the frontend and backend for the live environment, run
-
-```shell
-make start-live
-```
-
-
-### Release
-
-Run
-
-```shell
-make release
-```
-
-For releasing a RC version
-
-Run
-
-```shell
-make release-rc
-```

package/UPGRADE-GUIDE.md

@@ -1,38 +0,0 @@
-# Upgrade Guide
-
-## volto-light-theme 3.0.0
-
-### Blocks background colors go full width
-
-The background colors previously used to snap to 1440px.
-From 3.0.0-alpha.0 this changed to be unconstrained by default, and expand to the end of the horizontal viewport.
-
-### Upgraded support for volto-slider-block 6.0.0
-
-VLT upgraded the dependency on `@kitconcept/volto-slider-block` to use `6.0.0`.
-
-This is a drop-in replacement, so no action is required for the existing slider blocks you may have already in your sites.
-However, the CSS classes of the structural slider block elements changed in this version.
-The inner (visible objects) CSS classes remain unchanged.
-If you have customized them in your project, you may have to update them, although the structural class names are rarely customized aside from vertical spacing properties.
-They are mapped 1:1 with the previous ones, following this table correspondence:
-
-| Old className   | New className    |
-| --------------- | ---------------- |
-| slick-slider    | slider-wrapper   |
-| slick-list      | slider-viewport  |
-| slick-track     | slider-container |
-| slick-slide     | slider-slide     |
-| slick-arrow     | slider-button    |
-| slick-prev      | slider-button-prev |
-| slick-next      | slider-slide-next  |
-| slick-next      | slider-slide-next  |
-| slick-dots      | slider-dots      |
-| slick-dot       | slider-dot       |
-
-For more information, please check the https://github.com/kitconcept/volto-slider-block/blob/main/README.md [#288](https://github.com/kitconcept/volto-light-theme/pull/288)
-
-### Language switcher shows the two letters abbreviation of the languages
-
-Volto default is to show the full name of the language in the language switcher.
-VLT now shows only the two letters abbreviation of the language.