Customize Authentik login/enrollment pages to match GitcheGumi branding #37

New issue

Closed

opened 2026-06-03 20:12:40 -05:00 by Gitchegumi · 0 comments

Gitchegumi commented

2026-06-03 20:12:40 -05:00

(Migrated from github.com)

Problem

The Authentik login/enrollment experience currently uses the default Authentik look and does not match the GitcheGumi/GitchAlerts branding.

Since GitchAlerts uses Authentik for OIDC authentication and invite onboarding, the auth experience should feel visually connected to the rest of the GitcheGumi ecosystem.

Brand references

Use the existing GitcheGumi/GitchAlerts style direction from:

Brand palette:

Ultramarine Blue   #4166f5   Primary branding elements, logos
Golden Orange      #fca311   Secondary elements, call-to-action buttons
Dark Charcoal      #2c2c2c   Backgrounds, text, main interface elements
Tiffany Blue       #afe0ce   Accents, buttons, highlights
Soft White         #f0f0f0   Text, backgrounds, contrast areas
Platinum           #CCDBDC   Secondary accents, icons, subtle highlights

Desired behavior

Authentik login and enrollment pages should visually align with GitchAlerts/GitcheGumi branding.
The enrollment flow used for GitchAlerts invites should not look like a generic Authentik default page.
Branding should support both login and enrollment screens.
Branding should not break Authentik functionality, policies, prompts, invitation flow, or OIDC redirects.

Scope

Investigate and implement the best Authentik-supported customization approach for:

Login page styling.
Enrollment flow styling.
Logo/brand treatment.
Background imagery or solid branded background.
Button/link colors.
Text contrast and readability.
Any custom CSS or flow appearance configuration Authentik supports.

Acceptance criteria

Authentik login page uses GitcheGumi/GitchAlerts branding.
GitchAlerts enrollment flow uses the same branding.
Styling aligns with the core brand palette.
Mobile layout remains usable.
OIDC login and enrollment still work after customization.
Document where the customization lives and how to maintain it during Authentik upgrades.

Notes

This may live outside the GitchAlerts codebase depending on how Authentik theming is handled. This issue still belongs here because Authentik is part of the GitchAlerts onboarding experience for this self-hosted deployment.

## Problem The Authentik login/enrollment experience currently uses the default Authentik look and does not match the GitcheGumi/GitchAlerts branding. Since GitchAlerts uses Authentik for OIDC authentication and invite onboarding, the auth experience should feel visually connected to the rest of the GitcheGumi ecosystem. ## Brand references Use the existing GitcheGumi/GitchAlerts style direction from: - https://gitchpage.com - https://blog.gitchegumi.com Brand palette: ```text Ultramarine Blue #4166f5 Primary branding elements, logos Golden Orange #fca311 Secondary elements, call-to-action buttons Dark Charcoal #2c2c2c Backgrounds, text, main interface elements Tiffany Blue #afe0ce Accents, buttons, highlights Soft White #f0f0f0 Text, backgrounds, contrast areas Platinum #CCDBDC Secondary accents, icons, subtle highlights ``` ## Desired behavior - Authentik login and enrollment pages should visually align with GitchAlerts/GitcheGumi branding. - The enrollment flow used for GitchAlerts invites should not look like a generic Authentik default page. - Branding should support both login and enrollment screens. - Branding should not break Authentik functionality, policies, prompts, invitation flow, or OIDC redirects. ## Scope Investigate and implement the best Authentik-supported customization approach for: - Login page styling. - Enrollment flow styling. - Logo/brand treatment. - Background imagery or solid branded background. - Button/link colors. - Text contrast and readability. - Any custom CSS or flow appearance configuration Authentik supports. ## Acceptance criteria - Authentik login page uses GitcheGumi/GitchAlerts branding. - GitchAlerts enrollment flow uses the same branding. - Styling aligns with the core brand palette. - Mobile layout remains usable. - OIDC login and enrollment still work after customization. - Document where the customization lives and how to maintain it during Authentik upgrades. ## Notes This may live outside the GitchAlerts codebase depending on how Authentik theming is handled. This issue still belongs here because Authentik is part of the GitchAlerts onboarding experience for this self-hosted deployment.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gitchegumi/GitchAlerts#37

No description provided.

Rows
Columns