scavold 0.2.0-rc.9 → 0.2.1

package/CHANGELOG.md

@@ -4,11 +4,91 @@ All notable changes to Scavold are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), versions follow
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-While the version stays below `1.0.0` and carries a pre-release suffix, breaking
-changes may occur in any release.
+While the version stays below `1.0.0`, a minor release may break what the previous
+one offered; a patch release does not.
 
 ## [Unreleased]
 
+## [0.2.1] — 2026-10-04
+
+### Fixed
+
+- Menus and breadcrumbs no longer link a folder without an `index.md` — there is no page
+  to go to, and the link was dead. Such a folder is named as text above its pages where a
+  menu shows them, left out where a menu does not, and named as text in a breadcrumb.
+
+## [0.2.0] — 2026-10-04
+
+### Added
+
+- Named menus. A site declares them under `menus` in `.cratly.config.yaml`, a page
+  chooses in its `menus` front matter which of them it appears in, and the theme renders
+  one with `<ScavoldMenu menu="footer">` — so a page no longer has to sit in a folder of
+  its own, hidden from its URL by an alias, just to be collected into a footer. `depth`,
+  `active-only` and `expand` descend below each listed page as before, and a page
+  chosen along with its parent is listed below it there — or beside it in a flat menu,
+  which stays flat. `from-path` and `from-root` narrow the part of the site searched,
+  e.g. to one language. A name the site does not declare is warned about at build time.
+
+### Changed
+
+- A page choosing named menus only leaves the page tree's menus unless it chooses
+  `auto` as well. Pages without `menus` front matter are listed exactly as before.
+
+## [0.2.0-rc.12] — 2026-10-03
+
+### Added
+
+- `:::cover` takes `tone=light` or `tone=dark` for content on top that is meant to be
+  light or dark, depending on the picture. It only marks the cover with
+  `scavold-cover--light` or `scavold-cover--dark`; the colours are the theme's. The
+  editor offers it as a choice.
+
+## [0.2.0-rc.11] — 2026-10-01
+
+### Added
+
+- A container opening a page carries an empty `data-leading` attribute, and the page
+  data name it as `leadingContainer` — known before the content renders, so a layout
+  can arrange its own parts around a cover at the top of a page, e.g. move its
+  breadcrumb below it. Both are information only; nothing changes for a theme that
+  does not ask.
+
+## [0.2.0-rc.10] — 2026-10-01
+
+### Added
+
+- `:::cover` shows an image or a video across the full width and height of the
+  window, cropped to fit, with the block's content laid on top. An image comes with
+  all its variants and a `sizes` value that accounts for the cropping; a video plays
+  muted in a loop while at least half of it is on screen, stays still for visitors
+  asking for reduced motion, and always has a button to pause it. The editor offers it
+  as a section type.
+- A container argument declared as `media-file` that names an image hands its
+  component the variants and dimensions as well, as `data-<arg>-srcset`,
+  `data-<arg>-webp-srcset`, `data-<arg>-width` and `data-<arg>-height`.
+- `<ScavoldImage>` takes `loading` and `fetchpriority`, for an image at the top of a
+  page.
+- `useAutoplay()` brings the same autoplay behaviour to a site's own video component.
+
+### Changed
+
+- A `:::video` with `autoplay` plays only while at least half of it is on screen, and
+  pauses when scrolled away — unless the visitor turned the sound up. It stays paused
+  for visitors whose system asks for reduced motion, and once the visitor paused it.
+  The `autoplay` attribute is no longer part of the markup: it started the video at
+  once, wherever it was on the page and before reduced motion could be checked.
+
+### Removed
+
+- The `overlay` and `controls` arguments of `:::video`. Use `:::cover` for a video
+  with content on top: the background mode had no way to pause a looping video, which
+  WCAG 2.2.2 requires, and ignored reduced motion. A `:::video` now always is a player
+  with its controls; a block still carrying `overlay` renders as one, with its content
+  as fallback text. `useVideo()` no longer returns `overlay` and `controls`, and the
+  `.scavold-video--overlay`, `.scavold-video__media` and `.scavold-video__overlay`
+  classes are gone.
+
 ## [0.2.0-rc.9] — 2026-10-01
 
 ### Fixed
@@ -289,7 +369,12 @@ First published release. Version `0.1.0` existed in-tree only.
 - Only images are processed out of `media_folder`; other file types (video, documents)
   are never copied into the build output and have to live in the static folder.
 
-[Unreleased]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.9...main
+[Unreleased]: https://gitlab.com/cratly/scavold/-/compare/v0.2.1...main
+[0.2.1]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0...v0.2.1
+[0.2.0]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.12...v0.2.0
+[0.2.0-rc.12]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.11...v0.2.0-rc.12
+[0.2.0-rc.11]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.10...v0.2.0-rc.11
+[0.2.0-rc.10]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.9...v0.2.0-rc.10
 [0.2.0-rc.9]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.8...v0.2.0-rc.9
 [0.2.0-rc.8]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.7...v0.2.0-rc.8
 [0.2.0-rc.7]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.6...v0.2.0-rc.7