Skip to content

feat(launch): optional creator banner, stored and edited like the logo - #66

Merged
kevincodex1 merged 1 commit into
feat/ui-overhaul-homefrom
ui/overhaul-3-banners
Oct 6, 2026
Merged

kevincodex1 merged 1 commit into
feat/ui-overhaul-homefrom
ui/overhaul-3-banners

Conversation

@Vasanthdev2004

@Vasanthdev2004 Vasanthdev2004 commented Oct 6, 2026 •

Copy link
Copy Markdown
Collaborator

Part 3 of 9 of the UI overhaul, stacked on #61. Each PR's diff is only its own step; review and merge in order.

Creators can add one optional wide banner beside the logo. This PR is the data path and the edit sheet; the market cards (part 4), the token page (part 7) and the launch form (part 8) show and offer it.

What changes

  • Schema: ALTER TABLE bb_launch_meta ADD COLUMN IF NOT EXISTS banner_url text; (nullable, idempotent).
  • Upload route: kind=banner picks the banner processor (1500 x 500 WebP) and a 4 MB cap; logos keep their path. A random key in the same store, never a user-chosen name.
  • Saved at launch (meta.ts), replaced by signed edits (editServer.ts), and read with the market list (queries.ts, canonicalised like the logo).
  • Signing (editAuth.ts): the banner line joins the signed message only when a banner is set, so messages signed before banners existed still verify.
  • The edit sheet offers a banner upload; ImageUpload gains kind="banner" and a stacked layout.

Notes

  • Schema change: needs Kevin's approval before it ships (one new nullable column on bb_launch_meta).

Checks on this branch: lint, tsc --noEmit, npm test (849 pass, 0 fail, 10 skipped), next build.

Stack (merge top to bottom)

  1. UI overhaul, phase 1: search everywhere, row-to-page morph, rolling live numbers #60 phase 1: search, row-to-page morph, live numbers
  2. ui: home as a live floor (river, totals sentence, watchlist, just launched) #61 home as a live floor
  3. ui: shared foundations for the overhaul (Geist type, chain marks, vendor kit) #64 shared foundations for the overhaul (Geist type, chain marks, vendor kit)
  4. ui: rebuild the header nav #65 rebuild the header nav
  5. feat(launch): optional creator banner, stored and edited like the logo #66 optional creator banner, stored and edited like the logo (this PR)
  6. ui: market board with cards and denser rows #67 market board with cards and denser rows
  7. ui: home floor (hero, live river and bubbles, trending) #68 home floor (hero, live river and bubbles, trending)
  8. feat(charts): GeckoTerminal chart with the native chart as fallback #69 GeckoTerminal chart with the native chart as fallback
  9. ui: token page hero, trade panel and details #70 token page hero, trade panel and details
  10. ui: launch flow as a step rail with a live preview #71 launch flow as a step rail with a live preview
  11. ui: posts, how it works, agents and dashboard in the new style #72 posts, how it works, agents and dashboard in the new style

@coderabbitai

coderabbitai Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 81c5c113-55e9-4448-9a59-1c670534bc6c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

One nullable column (bb_launch_meta.banner_url), the upload route picks its processor and byte cap from the role, and the edit sheet offers it. Signed like every other edit.
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