Keycloak login theme source files #173

New issue

Closed

opened 2026-06-08 02:37:01 +00:00 by ldraney · 0 comments

ldraney commented

2026-06-08 02:37:01 +00:00

Owner

Type

Feature

Lineage

Follow-up from keycloak-setup.md ticket #5: "Keycloak login theme -- Not started."

Repo

ldraney/landscaping-assistant

User Story

As a developer maintaining the landscaping app
I want the Keycloak theme source files in the app repo
So that the theme CSS co-evolves with the app's design system

Context

The Keycloak login theme CSS mirrors application.css design tokens. Keeping the source in the app repo means when design tokens change, the theme stays in sync. The actual deployment is via pal-e-platform ConfigMap, but the source of truth for the CSS lives here.

File Targets

Files the agent should modify or create:

keycloak-theme/landscaping/login/theme.properties -- theme config
keycloak-theme/landscaping/login/resources/css/login.css -- CSS matching app design tokens

Files the agent should NOT touch:

app/assets/stylesheets/application.css -- read-only reference, not modified

Feature Flag

none

Acceptance Criteria

Theme files at keycloak-theme/landscaping/login/
CSS uses same design tokens as application.css
Plant icon SVG matches sessions/new.html.erb icon
Hides default Keycloak branding

Test Expectations

Visual verification via Playwright
CSS loads correctly on Keycloak server
Run command: n/a (static CSS files, no tests)

Constraints

No Tailwind
CSS-only, no FreeMarker templates
Follow ror-css-guide conventions (tokens, no hardcoded hex)

Checklist

PR opened
No unrelated changes

landscaping-assistant -- project this affects

### Type Feature ### Lineage Follow-up from keycloak-setup.md ticket #5: "Keycloak login theme -- Not started." ### Repo `ldraney/landscaping-assistant` ### User Story As a developer maintaining the landscaping app I want the Keycloak theme source files in the app repo So that the theme CSS co-evolves with the app's design system ### Context The Keycloak login theme CSS mirrors application.css design tokens. Keeping the source in the app repo means when design tokens change, the theme stays in sync. The actual deployment is via pal-e-platform ConfigMap, but the source of truth for the CSS lives here. ### File Targets Files the agent should modify or create: - `keycloak-theme/landscaping/login/theme.properties` -- theme config - `keycloak-theme/landscaping/login/resources/css/login.css` -- CSS matching app design tokens Files the agent should NOT touch: - `app/assets/stylesheets/application.css` -- read-only reference, not modified ### Feature Flag none ### Acceptance Criteria - [x] Theme files at `keycloak-theme/landscaping/login/` - [x] CSS uses same design tokens as application.css - [x] Plant icon SVG matches sessions/new.html.erb icon - [x] Hides default Keycloak branding ### Test Expectations - [x] Visual verification via Playwright - [x] CSS loads correctly on Keycloak server - Run command: n/a (static CSS files, no tests) ### Constraints - No Tailwind - CSS-only, no FreeMarker templates - Follow ror-css-guide conventions (tokens, no hardcoded hex) ### Checklist - [x] PR opened - [x] No unrelated changes ### Related - `landscaping-assistant` -- project this affects