Skip to content

docs(configuration): add white labeling guide#441

Merged
lexfrei merged 6 commits intomainfrom
docs/white-labeling
Mar 4, 2026
Merged

docs(configuration): add white labeling guide#441
lexfrei merged 6 commits intomainfrom
docs/white-labeling

Conversation

@lexfrei
Copy link
Contributor

@lexfrei lexfrei commented Mar 4, 2026

Summary

  • Add dedicated documentation page for configuring white labeling (branding) in Cozystack v1
  • Covers Dashboard fields (titleText, footerText, tenantText, logoText, logoSvg, iconSvg) and Keycloak fields (brandName, brandHtmlName)
  • Includes SVG preparation guide with theme-aware template variables, portable base64 encoding, and migration notes from v0 ConfigMap approach
  • Update platform-package.md reference to link to the new guide

Summary by CodeRabbit

  • Documentation
    • Updated Platform Package reference documentation to direct users to the White Labeling guide with details on default field behavior
    • Added comprehensive White Labeling guide covering Dashboard and Keycloak branding customization, including SVG logo preparation, base64 encoding workflows, YAML configuration examples, verification steps, and migration guidance

lexfrei added 5 commits March 4, 2026 15:41
Add dedicated documentation page for configuring branding
in Cozystack Dashboard and Keycloak authentication pages.
Covers all available fields, SVG preparation, theme-aware
variables, and migration notes from v0 ConfigMap approach.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Remove misleading "colors" claim from description, add note
explaining non-standard SVG template syntax, use portable
base64 command, and fix migration link anchor.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Use full CRD name packages.cozystack.io in kubectl commands
for consistency with the rest of the documentation. Remove
duplicated "Example SVG" heading.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
…se Hugo refs

Package is a cluster-scoped resource, remove incorrect
namespace field from the YAML example. Switch cross-references
to Hugo ref shortcode for build-time validation.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
…bectl commands

Use kubectl apply --server-side for idempotent application.
Remove --namespace flag from kubectl commands since Package
is a cluster-scoped resource.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
@netlify
Copy link

netlify bot commented Mar 4, 2026

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit d874df1
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/69a82dafb3da3f00087c5b6d
😎 Deploy Preview https://deploy-preview-441--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 4, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a74ff75f-0b36-43c1-b84a-e9516912a3cf

📥 Commits

Reviewing files that changed from the base of the PR and between e1d6350 and d874df1.

📒 Files selected for processing (2)
  • content/en/docs/v1/operations/configuration/platform-package.md
  • content/en/docs/v1/operations/configuration/white-labeling.md

📝 Walkthrough

Walkthrough

Documentation updates for white-labeling and branding configuration: the Platform Package reference was updated to cross-reference a new comprehensive white-labeling guide that covers Dashboard and Keycloak branding customization, SVG logo embedding, base64 encoding, configuration examples, and migration guidance.

Changes

Cohort / File(s) Summary
Branding Documentation Updates
content/en/docs/v1/operations/configuration/platform-package.md
Updated Branding field description to reference the new White Labeling guide and clarify that individual fields have default values when not specified.
New White-Labeling Guide
content/en/docs/v1/operations/configuration/white-labeling.md
New comprehensive documentation covering branding customization for Dashboard (titleText, footerText, tenantText, logoText, logoSvg, iconSvg) and Keycloak (brandName, brandHtmlName), including SVG preparation with theme-aware placeholders, base64 encoding workflows, YAML configuration examples, CLI patch commands, verification procedures, and migration notes from v0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A guide to whitewashing the brand so fine,
Where logos dance and colors align,
New documentation, pristine and neat,
Makes platform theming ever so sweet!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title 'docs(configuration): add white labeling guide' directly and clearly summarizes the main change: adding new documentation for white labeling configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/white-labeling

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new, comprehensive documentation guide for configuring white labeling within Cozystack v1. The guide aims to empower users to customize the branding elements across the Dashboard UI and Keycloak authentication pages, providing clear instructions on available configuration fields, SVG preparation, and migration considerations from previous versions.

Highlights

  • New Documentation Page: Added a dedicated documentation page for configuring white labeling (branding) in Cozystack v1.
  • Configuration Details: Detailed the configuration fields for both the Dashboard (titleText, footerText, tenantText, logoText, logoSvg, iconSvg) and Keycloak (brandName, brandHtmlName).
  • SVG Preparation Guide: Provided a comprehensive guide for preparing SVG logos, including theme-aware template variables, portable base64 encoding, and an example workflow.
  • Migration Notes: Included migration notes for users transitioning from the v0 ConfigMap approach to v1, explaining the automatic conversion process.
  • Updated Reference: Updated the platform-package.md document to reference the newly created white labeling guide.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • content/en/docs/v1/operations/configuration/platform-package.md
    • Updated the description for the branding field to include a direct link to the new white labeling guide.
  • content/en/docs/v1/operations/configuration/white-labeling.md
    • Added a new documentation page titled "White Labeling" which details how to customize branding elements in the Cozystack Dashboard and Keycloak.
    • Included sections on overview, configuration, specific Dashboard and Keycloak fields, preparing SVG logos (theme-aware variables, base64 encoding), an example workflow, verification steps, and migration notes from v0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request introduces a comprehensive and well-structured white labeling guide, which is a valuable addition to the documentation. The new page clearly outlines the configuration steps for both the Dashboard and Keycloak, including practical examples for SVG preparation and patching the Platform Package. The update to platform-package.md correctly links to this new guide.

Note: Security Review has been skipped due to the limited scope of the PR.

| --- | --- | --- |
| `titleText` | `Cozystack Dashboard` | Browser tab title and Dashboard header text. |
| `footerText` | `Cozystack` | Text displayed in the Dashboard footer. |
| `tenantText` | Platform version string | Version or tenant identifier displayed in the Dashboard. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The default value for tenantText is described as "Platform version string". To enhance clarity, it would be beneficial to provide a more concrete example of what this string typically looks like (e.g., "v1.0.0" or "1.0") or explain how it's derived. This would help users understand what to expect if they don't explicitly set this field.

Add --server-side to kubectl patch for consistency, clarify
SVG template syntax note, add variant comment to YAML example,
and note individual field defaults in platform-package.md.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
@lexfrei lexfrei marked this pull request as ready for review March 4, 2026 13:04
@lexfrei lexfrei requested review from kvaps and lllamnyp as code owners March 4, 2026 13:04
@lexfrei lexfrei self-assigned this Mar 4, 2026
@lexfrei lexfrei merged commit acd30be into main Mar 4, 2026
6 checks passed
@lexfrei lexfrei deleted the docs/white-labeling branch March 4, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants