Skip to content

fix(staff-ui): render dashboard image as background on 1.2 - #203

Closed
asmitonweb wants to merge 1 commit into
OpenG2P:1.2from
asmitonweb:fix/1.2-dashboard-background-image
Closed

asmitonweb wants to merge 1 commit into
OpenG2P:1.2from
asmitonweb:fix/1.2-dashboard-background-image

Conversation

@asmitonweb

Copy link
Copy Markdown

An uploaded dashboard_image renders as a full-width illustration below the dashboard search bar. A photograph grows with page width, pushes content below the viewport and leaves the patterned background behind the cards.

Use a configured image as a decorative, centered cover background behind the cards/search controls, with a light theme-coloured overlay. It does not add document height or receive pointer events. Preserve the existing pattern and people illustration when no custom image is configured, and retain the 1.2 branch's responsive widths and foreground overflow behavior.

This PR is based directly on the 1.2 release branch at 5f828d2, which contains the source revision of the currently consumed 1.2.2-rc.544 platform image (323a9829). It contains one dashboard-component change and no develop-only commits. It replaces closed PR #200, whose original head was based on develop.

Validation:

  • Confirmed 1.2.2-rc.544's OCI source revision (323a9829) is an ancestor of the target release branch. The PR contains one commit and changes only ui/staff-ui/src/app/[locale]/page.tsx relative to 1.2.
  • git diff --check passed. Resolved the port against the release branch while retaining its responsive content widths and unclipped foreground controls.
  • The original implementation passed a production build, targeted lint and Firefox component checks at 1440×900 and 390×844, with and without a custom image. Those results were for the previous develop baseline, not this release-line port.
  • Release-line npm ci could not complete: this workstation's npm policy disables remote-tarball dependencies, and 1.2 already depends on @openg2p/notification from a GitHub tarball. No policy or dependency pins were changed. The failed installation left no runnable local build/lint/component dependencies, so those checks have not been rerun on this port. Upstream UI CI must validate the release-line build before merge.

The existing theme setting is reused; no schema, API, dependency or version-pin changes are included. This changes the presentation of configured dashboard images from illustrations to backgrounds; cropping follows viewport aspect ratio. No Farmer Registry repository changes or deployments are included.

@Q-Niranjan

Copy link
Copy Markdown
Contributor

@asmitonweb FYI, The Staff UI home page has two distinct visual elements.

  1. Background pattern- Covers the entire page to provide a consistent visual background.
  2. Dashboard illustration- Intentionally positioned at the bottom of the page, below the search bar, to complement the homepage design.

In this pr, the background pattern has been removed, and the dashboard illustration is being used as the page background. This does not align with the intended design of platform.

@faizmagic

Copy link
Copy Markdown

@shibu-narayanan, as part of the registry implementation, our requirement is to have a full sized background image rather than a background pattern. is it ok if we make the corresponding change to have the following options in the theme

  1. User background pattern
  2. Use background images as per user choice.

Currently this functionality does not exist and hence we updated the dashboard illustration.

CC: @asmitonweb, @Q-Niranjan

@asmitonweb asmitonweb closed this Oct 23, 2026
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.

3 participants