Upvote Overlord

Roadmap edition stage 2: the board can now present itself as a roadmap, and every string the frontend JavaScript renders goes through the Joomla language layer. No database changes; existing boards keep their settings and data.

Added

• Roadmap view. New "Board view" setting on the Display tab: "List (sorted

by votes)" (the existing behaviour, still the default) or "Roadmap (status columns)". The roadmap groups the votable items into columns per status - Open / Planned / In Progress / Shipped / Declined - using the status a moderator set on each item. Items keep their vote order inside a column, voting and the moderation toolbar work exactly as in the list view, and column accent colours reuse the status-badge palette (status is always also named in text, never colour-only). Vote-only display mode always uses the list view.

• "Roadmap empty columns" setting (Display tab): hide status columns that

have no items (default) or keep them visible as an explicit empty lane.

• 36 new frontend language keys in all six languages (en-GB, nl-NL, de-DE,

fr-FR, es-ES, it-IT), plus a translated noscript message.

Changed

• Frontend JavaScript is now fully localized (closes the YC.6 JS i18n gap).

Every string the JS renders - moderation and status toasts, loading/empty/ error states, countdown labels, builder-preview notices, the delete confirmation, and the accessibility labels on vote/moderation controls - is resolved through the language layer server-side and handed to the JS in the element config. The previous hardcoded English strings remain in the JS only as fallbacks for missing keys.

• In the roadmap view, item cards no longer show the status badge - the column

itself communicates the status.

Fixed

• Removed a duplicate ERR_NO_BOARD language key that shipped in all six

languages since v3.0.0 (the later definition already won at parse time, so no behaviour change).

• Removed a duplicate pad2() helper definition in the frontend JS.

Settings-panel clarity pass. No functional or data changes - only labels, help text and field placement in the builder. Existing boards keep their settings.

Changed

• "Board ID mode" is now "Board scope", and its options describe the result

instead of the mechanism: "One shared board (set the Board ID below)" and "A separate board per page (automatic)". The stored values are unchanged, so boards configured before this release keep working exactly as they were.

• Board scope now appears above Board ID in the Content tab. It is the

decision that determines whether Board ID is used at all, so it comes first.

• Board ID help text rewritten. It previously recommended mapping the field

to a dynamic source, which can silently bind to the first item of a source rather than the current one (every page then shares one board). It now points to Board scope -> "A separate board per page" as the reliable way to give each item its own board, and demotes dynamic mapping to an advanced note.

• Vote icon moved from the Voting tab to the Display tab, next to Card style

and Theme. It is a cosmetic choice, not a voting mechanic.

Added

• Board ID mode: "Auto (current page / item)". A new option on the element.

When set to Auto, the plugin ignores the Board ID field and derives a unique, stable board id from the current Joomla item server-side - it prefers the request item id (works on non-SEF sites and survives alias changes) and falls back to the current URL path (SEF catalogs). Use this when one shared template renders many items and YOOtheme's dynamic-source picker keeps resolving Board ID to the wrong (first) item. No source mapping required; every item's page gets its own board automatically.

Notes

• Default is still Manual, so existing boards are unaffected. Auto is opt-in.

Added

• Dynamic Board ID. The Board ID field is now dynamic-content mappable. Drop

one Upvote Overlord into a reusable YOOtheme template (e.g. a product/article detail template) and map Board ID to the current item (its ID or alias): every item's page then renders its own separate board automatically, with no per-page setup. The board "remembers" which item it belongs to because the id is resolved per item at render and carried on every vote/submit call.

Changed

• Board ID sanitisation now slugifies: any run of disallowed characters becomes

a single dash (so a mapped title like "My Cool Plugin" becomes "my-cool-plugin"). Existing dashes and underscores are preserved, so current board IDs are unaffected. The rule is identical on render and in every AJAX endpoint, keeping a board's identity stable across actions.

Themes edition. Three fully-designed visual themes are added to the existing Theme dropdown, alongside the original colour presets.

Added

• Three design themes, selectable per board from the element's Theme

field:

• Leaderboard Arena - light cream surface, coral accent, hard offset

"sticker" shadows, big numbered rank, a leader pill on #1, vote pill on the right. (Bricolage Grotesque + Plus Jakarta Sans.)

• Neon Stage - dark, volt-lime accent, vote button that fills and glows

when voted. (Space Grotesk.)

• Retro Pixel Arcade - dark purple, 8-bit type, thick pixel borders, hard

shadows, cyan to pink vote button. (Press Start 2P + VT323.)

• Per-item furniture for these themes: a rank number (Arena), an avatar that

uses the item image when set and otherwise shows colour-coded initials derived from the title, a leader pill on the top item, and a "votes" label. Vote presses replay a count-pop + icon-bounce animation.

• Self-hosted web fonts under media/plg_system_yc_upvote_overlord/fonts/

(OFL, latin subset, woff2). No Google Fonts CDN call, so visitor IPs stay on your server (GDPR-friendly). A font file is only fetched by the browser when a theme actually uses it.

Notes

• Fully backward-compatible: the default theme is unchanged; existing boards keep

their current look. The colour presets (Light, Dark, Auto, Minimal, Soft, Bold) are untouched.

• Next stages: v3.2.0 Roadmap view (status columns); v3.3.0 Comments.