Tags

Tags give the ability to mark specific points in history as being important

  • 1.0.5

    26a57fed · feat: the hero picture dissolves into the band, and the mark is drawn to survive it · 
    The hero picture dissolves into the band

Adds a fictional civic building as a dissolved layer behind the hero, toned to the band and masked
to nothing at every edge that meets flat ground. The portico mark gains a recess between its
columns so it keeps its declared contrast over the picture without a box or a scrim. Footer laid
out in five columns.

  • 1.0.4

    3fc8c7bb · feat: the euro total returns to the front page, and the bars stop slicing their figures · 
    The euro total returns, and the bars stop slicing their figures

Restores the total awarded to the front page using entityQueryAggregate, which emits one SUM() on
a decimal column and is safe on PostgreSQL, MariaDB and SQLite alike. Adds a total column to the
spend-by-area table with its bar layer, and stops the bar fill overlapping the figure at any width.

  • 1.0.3

    57e433e7 · feat: breadcrumbs, and a record-sheet layout for node pages · 
    Breadcrumbs and a record-sheet layout for node pages

Adds a breadcrumb block placement and a template override, and gives node pages a record sheet
layout that uses the page width without widening the text measure.

The override exists because core's breadcrumb template emits a visually-hidden h2 for its
accessible name, and with the block above the page title that h2 landed in front of every page's
h1. A visually-hidden span replaces it; the aria-labelledby id and wiring stay exactly as core
writes them, because core's own AssertBreadcrumbTrait selects on that id.

  • 1.0.2

    9f83908b · feat: register cards, a hero lede, and the theme's first preprocess · 
    Register cards, a hero lede, and the theme's first preprocess

Front-page work: the six registers render as a responsive card grid with each count as a large
tabular numeral, and the hero band carries a one-line lede. Adds agora_theme.theme, the theme's
first PHP, for the front-page-only lede; it returns early on every other page and that was
measured, not asserted. Also fixes four pre-existing stylelint errors.

Ships four block placements the previous releases did not have: branding, footer branding,
footer menu and powered-by.

  • 1.0.1

    8979785f · fix: two copies declared verbatim disagreed about a mode the sha cannot see · 
    1.0.1 - Views tables render through the theme's own template

The fix a user sees is one commit: dbbe934. Views tables were bypassing the theme entirely,
because Drupal renders them through views-view-table.html.twig and this theme only overrode
table.html.twig. Every register page - contracts, subsidies, agreements, datasets - rendered
without the theme's horizontal scroller and without its classes, and the scroller is the part
that makes a wide financial table reachable by keyboard.

1.0.0 did not contain templates/views-view-table.html.twig at all.

Everything else in this tag is what now notices if that file disappears again, and it was
built because the fix had shipped with nothing that would:

  - a fixture module with its own Views config entity, enough content that the table really
    renders, and five assertions that go red with the template moved aside - measured, not
    asserted, with core's own caption/scope/headers markers staying green on purpose
  - the theme's first config/ directory: default block placements for page title, main
    content, primary menu and messages. Until now no real page had a page title, an h1 or a
    menu, and menu/node/field.html.twig were exercised by nothing
  - a pager that decides its own heading level, with the rule written beside the code
  - an accessibility gate that asserts WHICH axe bucket a rule landed in, because a rule that
    never ran is filed somewhere that reads exactly like a pass

Observed on pipeline 936594: nine blocking jobs, all green; axe over 6 pages, 89 rules per
page, 0 violations, heading-order reported on 6 of 6 pages, 297 assertions across 11 tests.

  • 1.0.0

    d92ab7c2 · docs: 1.0.0 is tagged, and the README says what a tag is not · 
    Ágora Transparency Theme 1.0.0

The first stable release of the front-end theme for the Ágora Transparency site template.

What it is: a sober, institutional theme for a Spanish municipal transparency portal, whose
core content is tables of salaries, contracts, agreements and grants. Everything in it exists
to make those tables readable - by a person, and by a screen reader.

Accessibility is a gate here rather than an intention. Every push runs axe in a real browser
over four pages this theme rendered, 89 rules per page, and the job is blocking. It has been
seen to fail: an image without alternative text turns it red and the log names the rule. Two
independent markers prove the pages audited were rendered by THIS theme and not by Drupal's
default, because a green accessibility run that scanned the wrong theme is worth nothing.

Colour: 18 tokens in one file, 38 foreground/background pairs, every ratio computed and
checked by a blocking invariant at 4.5:1 for text and 3:1 for focus rings and table rules. One
colour failed on the first pass and was darkened rather than excused.

Typography: Public Sans 2.001, self-hosted, SIL Open Font License 1.1, shipped with its OFL and
byte-identical to upstream. No font CDN anywhere - that is a data-protection liability for a
public-sector site in the EU, and the check that forbids it returns zero.

Not claimed: no WCAG conformance level is asserted. axe covers a fraction of WCAG; no keyboard
walkthrough and no screen-reader pass have been done, and the criteria tools cannot see remain
untested. The project is also not yet covered by Drupal's security advisory policy - it becomes
eligible on 2026-09-03.

Requires Drupal 11. No dependencies, so nothing to justify.