The review preview card showed the group description in the middle of the card and always used the same teal fill. This matches the review layout: description at the bottom, and a background taken from the uploaded logo—or a random light color when there is no image.
Changes
Expanded Rule cards can pin the description under the category rows, with the divider above it.
Review preview reads the uploaded community photo when there is one, and uses that image’s most common color (lifted to a light tint if the logo is dark so black type stays readable).
With no photo, the card picks a random light color once, stores it on the draft, and reuses it on reload.
The saved fill is applied before paint so reload does not flash the teal placeholder.
Screenshots
How to Test
Run the app and open /create/final-review with a named community and a group description.
Confirm the description sits under Conflict management, with a line above it.
With no community photo: note the card color, reload, and confirm it stays the same and does not flash teal first.
Upload a community photo, return to review, and confirm the card fill follows the logo’s main color.
Notes
The fallback color is a draft field. While you are working it lives in the browser draft; it is included in the saved draft payload as well.
Logo fills are derived from the image on the review step, not stored as a separate color.
## Overview
The review preview card showed the group description in the middle of the card and always used the same teal fill. This matches the review layout: description at the bottom, and a background taken from the uploaded logo—or a random light color when there is no image.
## Changes
- Expanded Rule cards can pin the description under the category rows, with the divider above it.
- Review preview reads the uploaded community photo when there is one, and uses that image’s most common color (lifted to a light tint if the logo is dark so black type stays readable).
- With no photo, the card picks a random light color once, stores it on the draft, and reuses it on reload.
- The saved fill is applied before paint so reload does not flash the teal placeholder.
## Screenshots
<!-- Paste a review-step screenshot if you have one -->
## How to Test
1. Run the app and open `/create/final-review` with a named community and a group description.
2. Confirm the description sits under Conflict management, with a line above it.
3. With no community photo: note the card color, reload, and confirm it stays the same and does not flash teal first.
4. Upload a community photo, return to review, and confirm the card fill follows the logo’s main color.
## Notes
- The fallback color is a draft field. While you are working it lives in the browser draft; it is included in the saved draft payload as well.
- Logo fills are derived from the image on the review step, not stored as a separate color.
an.di
self-assigned this 2026-09-29 21:17:15 +00:00
The review screen’s effect ran before draft hydration, so reload always generated a fresh color and overwrote the stored one.
Co-authored-by: Cursor <cursoragent@cursor.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
The review preview card showed the group description in the middle of the card and always used the same teal fill. This matches the review layout: description at the bottom, and a background taken from the uploaded logo—or a random light color when there is no image.
Changes
Screenshots
How to Test
/create/final-reviewwith a named community and a group description.Notes