Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

CFPB-branded Keycloak Theme #8

Closed
hkeeler opened this issue Oct 12, 2016 · 3 comments
Closed

CFPB-branded Keycloak Theme #8

hkeeler opened this issue Oct 12, 2016 · 3 comments
Assignees

Comments

@hkeeler
Copy link
Member

hkeeler commented Oct 12, 2016

Keycloak allows for full rebranding of all pages and email through their FreeMarker-based theme system.

  • Account - Account management
  • Admin - Admin console
  • Email - Emails
  • Login - Login forms
  • Welcome - Welcome page

I think the priority should be:

  1. Account and Login: All users will see the pages, obviously.
  2. Email: - The default email theme is pretty bare-bones, with almost no styling. This may be good enough for the initial version.
    1.Welcome or Admin: I don't think the end user will ever see these pages, and I'm fine keeping the default Keycloak theme for the Admin pages.

Let's evaluate what it will take to create CFPB/FFIEC-branded pages that match (as closely as makes sense) the hmda-platform-ui pages.

@hkeeler
Copy link
Member Author

hkeeler commented Oct 12, 2016

The details around Keycloak themes are at:

@hkeeler
Copy link
Member Author

hkeeler commented Oct 17, 2016

Keycloak itself uses PatternFly as its UI framework. It was created by Red Hat, appears to be a Bootstrap wrapper, and likely used to keep styles consistent across their products.

It is unclear at this point if we want to play within this framework, or go completely from scratch using https://standards.usa.gov/.

@awolfe76 awolfe76 self-assigned this Nov 16, 2016
@hkeeler
Copy link
Member Author

hkeeler commented Dec 16, 2016

I'm going to close this one out as we've decided to hold off on implementing the account theme for MVP. See #42 (comment).

@hkeeler hkeeler closed this as completed Dec 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants