Skip to content

Conversation

nickboldt
Copy link
Member

@nickboldt nickboldt commented Jun 19, 2025

What does this PR do?

chore: fix branding defaults; bump to 1.6 as default image version; improve docs for consistency with RH style guide (RHIDP-7883)

Signed-off-by: Nick Boldt [email protected]

Screenshot/screencast of this PR

Using quay.io/rhdh/rhdh-hub-rhel9:1.6:
image

Using quay.io/rhdh-community/rhdh:next

image

What issues does this PR fix or reference?

RHIDP-7883
RHIDP-7906

How to test this PR?

podman-compose stop rhdh; podman-compose up --pull --build --force-recreate; google-chrome http://localhost:7007/settings

PR Checklist

As the author of this Pull Request I made sure that:

  • Code produced is complete
  • Code builds without errors
  • Tests are covering the bugfix
  • Relevant user documentation updated
  • Relevant contributing documentation updated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Summary by Sourcery

Fix branding defaults, bump default image version to 1.6, and update documentation for style consistency and clearer image configuration instructions

Bug Fixes:

  • Fix branding defaults to include required logos and theme color variables

Enhancements:

  • Bump default RHDH container image version in compose.yaml to 1.6
  • Add default branding configuration (fullLogo, iconLogo, and theme colors) to app-config and example files
  • Expand documentation with instructions for switching between community, CI, and official images

Documentation:

  • Revise README for Red Hat style guide consistency, including updated headings, casing, a caution block, and reorganized prerequisites

@nickboldt nickboldt changed the title chore: fix branding defaults; bump to 1.6 as... chore: fix branding defaults; bump to 1.6 as default image version; improve docs for consistency with RH style guide (RHIDP-7883) Jun 19, 2025
@nickboldt nickboldt requested review from kadel, rm3l and benwilcock June 19, 2025 17:21
@nickboldt
Copy link
Member Author

nickboldt commented Jun 20, 2025

The white-on-grey logotype problem may be related to / fixed by redhat-developer/rhdh-plugins#981

Using the 1.6.1 community build at quay.io/rhdh-community/rhdh:1.6.1-b7bf4c77, the branding for the light theme looks fine:

image

@nickboldt nickboldt requested review from logonoff and ciiay June 20, 2025 00:44
@nickboldt nickboldt changed the title chore: fix branding defaults; bump to 1.6 as default image version; improve docs for consistency with RH style guide (RHIDP-7883) chore: fix branding defaults; bump to 1.6 as default image version; improve docs for consistency with RH style guide (RHIDP-7883, RHIDP-7906) Jun 20, 2025
@rm3l
Copy link
Member

rm3l commented Jun 24, 2025

@sourcery-ai review

Copy link
Contributor

sourcery-ai bot commented Jun 24, 2025

Reviewer's Guide

This PR bumps the default RHDH image to version 1.6, enriches the application configuration with comprehensive branding defaults (logos, title, theme colors), and refactors the local testing documentation for consistency with the Red Hat style guide, including expanded image customization guidance and streamlined architecture support notes.

Class diagram for updated branding configuration in app-config

classDiagram
    class AppConfig {
        +string title
        +string baseUrl
        +Branding branding
    }
    class Branding {
        +string fullLogo
        +string iconLogo
        +string fullLogoWidth
        +Theme theme
    }
    class Theme {
        +ThemeMode light
        +ThemeMode dark
    }
    class ThemeMode {
        +string primaryColor
        +string headerColor1
        +string headerColor2
        +string navigationIndicatorColor
    }
    AppConfig --> Branding
    Branding --> Theme
    Theme --> ThemeMode
Loading

File-Level Changes

Change Details Files
Default image version bumped to 1.6
  • Updated RHDH service image fallback to community build 1.6
  • Aligned install-dynamic-plugins container image to 1.6
compose.yaml
Branding configuration enriched
  • Added fullLogo, iconLogo, fullLogoWidth, and theme color variables
  • Renamed app title from shorthand to “Red Hat Developer Hub”
configs/app-config/app-config.local.example.yaml
configs/app-config/app-config.yaml
Documentation refactored for RH style guide
  • Standardized headings and phrasing
  • Replaced Mac M1 note with unified amd64/arm64 support
  • Introduced caution admonition and expanded image customization scenarios
README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @nickboldt - I've reviewed your changes - here's some feedback:

  • Make sure to add the new branding placeholders (FULL_LOGO_WIDTH, PRIMARY_LIGHT_COLOR, etc.) to your default.env or .env.example so the example configs don’t break at runtime.
  • The huge base64 blobs make the YAML hard to review—consider moving those inline logos into separate asset files or a shared include to reduce noise in the config examples.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Make sure to add the new branding placeholders (FULL_LOGO_WIDTH, PRIMARY_LIGHT_COLOR, etc.) to your default.env or .env.example so the example configs don’t break at runtime.
- The huge base64 blobs make the YAML hard to review—consider moving those inline logos into separate asset files or a shared include to reduce noise in the config examples.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

…mprove docs for consistency with RH style guide (RHIDP-7883)

Signed-off-by: Nick Boldt <[email protected]>

add theme colours

Signed-off-by: Nick Boldt <[email protected]>

refactor text to clarify commercially supported official images vs. CI builds vs. community builds

Signed-off-by: Nick Boldt <[email protected]>
@nickboldt nickboldt requested a review from benwilcock June 27, 2025 12:17
Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

🥳

@benwilcock
Copy link
Contributor

If we're sure we can make the switch to using RHDH community builds without incurring any user disruption or incompatibility, I am happy to endorse these changes. Thanks @nickboldt (and the whole team here) for taking the time to improve the RHDH Local experience for everyone and for the additional transparency for users around RHDH image choices. I think that's super useful and very educational.

…sing same sources for community & commercial

Signed-off-by: RHDH Build (rhdh-bot) <[email protected]>
@nickboldt
Copy link
Member Author

nickboldt commented Jun 27, 2025

Followup work to ensure we keep getting fresh :1.y tags in the quay.io/rhdh-community/rhdh repo for all .z updates, and that compose.yaml/readme.md are updated quarterly:

	update tagRelease.sh to
		replace the 1.6 tag for the rhdh repo when pushing the 1.6.z tag
		generate PR to update 
			compose.yaml: 1.6 floating tag
		 	readme: latest 1.6 or next 1.7

See https://issues.redhat.com/browse/RHIDP-7906 / https://issues.redhat.com/browse/RHIDP-7829

@rm3l
Copy link
Member

rm3l commented Jun 27, 2025

@sourcery-ai review

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @nickboldt - I've reviewed your changes - here's some feedback:

  • The huge inline base64 blobs for logos in your app-config examples make the YAML very hard to read and maintain—consider externalizing those images to files (or URLs) and referencing them to keep your configs DRY and cleaner.
  • You’re bumping the default image version in two places (compose.yaml and install-dynamic-plugins)—it might be worth consolidating that into a single RHDH_IMAGE default or variable so future version updates only need one change.
  • The README’s “Changing the container image” section now covers several different use cases (community, nightly CI, official), which can be a bit overwhelming—consider grouping those under a tabbed or collapsible format to simplify navigation.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The huge inline base64 blobs for logos in your `app-config` examples make the YAML very hard to read and maintain—consider externalizing those images to files (or URLs) and referencing them to keep your configs DRY and cleaner.
- You’re bumping the default image version in two places (`compose.yaml` and `install-dynamic-plugins`)—it might be worth consolidating that into a single `RHDH_IMAGE` default or variable so future version updates only need one change.
- The README’s “Changing the container image” section now covers several different use cases (community, nightly CI, official), which can be a bit overwhelming—consider grouping those under a tabbed or collapsible format to simplify navigation.

## Individual Comments

### Comment 1
<location> `README.md:209` </location>
<code_context>
+
+#### Using image digests
+
+If you prefer to use digests to floating tags, [browse for the tag you want to use](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba/history), and click though to find the digest of the image you want to use. For example, from the [Get this image](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?image=68360c12177ad86df31947d8&architecture=amd64&container-tabs=gti) tab for 1.6.1 provides this image:
+
+```sh
</code_context>

<issue_to_address>
Typo: 'click though' should be 'click through'.

Update the text to use the correct phrase.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
If you prefer to use digests to floating tags, [browse for the tag you want to use](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba/history), and click though to find the digest of the image you want to use. For example, from the [Get this image](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?image=68360c12177ad86df31947d8&architecture=amd64&container-tabs=gti) tab for 1.6.1 provides this image:
=======
If you prefer to use digests to floating tags, [browse for the tag you want to use](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba/history), and click through to find the digest of the image you want to use. For example, from the [Get this image](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?image=68360c12177ad86df31947d8&architecture=amd64&container-tabs=gti) tab for 1.6.1 provides this image:
>>>>>>> REPLACE

</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@benwilcock
Copy link
Contributor

/lgtm from a non-technical product management perspective. I didn't test it myself though - just reading through the changes.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@nickboldt nickboldt merged commit cad7f94 into main Jun 27, 2025
13 checks passed
@nickboldt
Copy link
Member Author

Merged after 2 people agreed it was an improvement over the current status, despite them not being code owners ;)

@nickboldt nickboldt deleted the RHIDP-7883-local branch July 14, 2025 15:33
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.

6 participants