Arabic, Persian, CJK, and other non-Latin titles were collapsing to an
empty d-tag because slugifyCampaignIdentifier only kept [a-z0-9] after
NFKD. NFKD doesn't transliterate Arabic to Latin, so a title like
حملة لمساعدة الأطفال slugified to "" and the user hit the cryptic
errorTitleInvalid message at submit time — after walking through the
entire wizard.
Route the title through the slugify package's charMap first (covers
Arabic, Persian, Cyrillic, Greek, Georgian, Armenian, Vietnamese, common
Latin diacritics, currency symbols, smart quotes). For inputs that still
produce no ASCII characters — emoji-only titles, CJK, Thai, Tamil —
buildCampaignSlug returns a random campaign-XXXXXX identifier so the
user can still publish; the human-readable title lives in the title tag,
not the URL.
Also strip Unicode bidi controls and zero-width characters
(RLM/LRM/FSI/PDI/ZWNJ/BOM) before they reach the title tag. RTL
keyboards routinely insert these invisibly, and preserving them in
display strings is a homograph/phishing vector.
Surface validation under the title input itself rather than at submit:
when the title transliterates cleanly, show the slug preview in a
muted-tone code block; when it doesn't, show an amber notice explaining
that a random URL identifier will be generated and that the title is
preserved verbatim. Hidden in edit mode where the d-tag is locked.
When Bitcoin transactions were rejected by the network for fee-related
reasons (min relay fee not met, mempool full, RBF replacement
underpriced), both the HD wallet Send dialog and the campaign Donate
dialog surfaced a destructive toast titled "Transaction failed" /
"Donation failed" with the raw bitcoind RPC error as the description.
The dialog stayed open with state preserved, but the donor:
- Saw an opaque, technical error string they couldn't act on.
- Got no affordance to recover. Re-tapping Send re-fired the same
rejected transaction. In HDSendBitcoinDialog the existing
two-tap arm wasn't reset on broadcast failure, so a second tap
immediately re-broadcasted with the same (rejected) parameters.
- In DonateDialog had no path to bump the fee without manually
backing out to the form step and re-picking a tier.
Three pieces, plus a small adjacent fix:
1. Classifier in src/lib/bitcoinBroadcastError.ts maps the verbatim
bitcoind / Blockbook-WebSocket / Esplora error strings onto a small
enum (feeTooLow, rbfReplacementFeeTooLow, mempoolFull,
mempoolConflict, tooLongChain, absurdlyHighFee, badInputs, network,
unknown). For the canonical 'min relay fee not met, A < B' form,
the actual and minimum sat/vB values are parsed out so the UI can
show "minimum right now is N sat/vB" and seed a custom fee. 17
unit tests covering real-world fixtures from mempool.space,
Blockstream Esplora, Blockbook framing, and bare bitcoind output.
2. Shared BroadcastErrorAlert in src/components/BroadcastErrorAlert.tsx
renders inline above the Send button. Replaces the toast for
classified errors (toast is retained only as a fallback for the
`unknown` bucket so something always surfaces). Fee-recoverable
kinds get a "Use a higher fee" action; `network` gets "Try again";
everything else has no action and waits for the donor to adjust
amount / recipient via the auto-dismiss effect. A `presetTiersOnly`
prop hides the bump button once a preset-only consumer (DonateDialog)
is on the fastest tier, surfacing "You're already on the fastest
tier" instead.
3. HDSendBitcoinDialog wiring — broadcast errors set a classified
state, the alert renders above Send, and a new bumpFeeForRetry
helper jumps to the next-faster preset OR, if already at the
top of the deduped preset list, switches to a custom rate seeded
from the strongest available hint (parsed minRelayFee + 1, or
1.5x the rejected rate, or current+1 as a last resort). Refetches
fee rates, opens the fee popover so the donor can see and tweak
the new rate, marks the picker as user-touched so the 40%-of-amount
auto-tune doesn't fight the bump, and resets the two-tap arm
unconditionally on every failure.
4. DonateDialog wiring — same alert in the confirm step. The dialog
has no custom-rate input by design (it's the simple donate flow),
so the bump action walks the preset chain economy -> hour ->
halfHour -> fastest. At the fastest tier the alert hides the
button and tells the donor to use an external wallet via the QR
panel on the campaign detail page.
5. i18n — 22 new keys under walletSend.broadcastError, translated
into all 15 non-English locales in parallel with placeholder and
technical-token preservation.
The auto-dismiss effects in both dialogs clear the alert as soon as
the donor adjusts a field that could plausibly resolve the failure
(recipient, amount, fee speed, custom rate) so the alert doesn't
linger once the donor has engaged with the fix.
Pasting a bare bc1…/sp1… address or a single-endpoint bitcoin: URI now
resolves directly to the recipient chip instead of dropping into the input
behind a one-row dropdown the donor still had to click. Pastes carrying
both an on-chain address and an sp1 code still fall through to the dropdown
so the donor picks privacy vs. compatibility.
Extracted the candidate-resolution logic into a shared resolveCandidates()
helper so the live input memo and the paste handler agree on what counts as
a valid destination; the paste handler resolves from the clipboard text
directly (query state hasn't updated yet inside the event) and
preventDefault()s the single-match case so the raw text never flickers in.
The campaign donate flow opens HDSendBitcoinDialog with a prefilled
bitcoin:bc1q…?sp=sp1… URI. BitcoinRecipientInput auto-opens its
dropdown so the donor picks between the on-chain address and the
silent-payment code — privacy vs. compatibility, the explicit choice
the picker was designed around (92608f14).
In practice the donor's eye lands on the amount presets first. Tapping
$100 counts as an outside click, dismisses the popover, and leaves
`recipient` null. The Send button is disabled (correctly — no
destination resolved), the input still shows the prefilled URI, and
nothing on screen tells the donor what's missing. They eventually
discover that re-tapping the recipient input reopens the dropdown.
Add a small amber hint with a warning icon directly beneath the
recipient input whenever the input has parseable candidates but no
selection AND the popover is closed. The whole hint is a button that
reopens the popover and refocuses the input on tap, so the recovery
takes one click instead of a guessing game.
Gate the hint on a new `hasOpenedForQuery` flag that flips true the
first time the popover opens for the current query and resets when the
query clears. That keeps the hint from flashing for one paint frame
between mount and the auto-open effect on prefilled inputs.
Regression-of: 92608f14
Swap the dropdown row order so "Send to Bitcoin address" renders above
"Send to silent payment address" — the broadly-compatible on-chain option
leads, with the privacy option following.
The candidate dropdown is a persistent choice list, but Radix's Popover
dismissed it whenever the input blurred or the user tapped elsewhere,
making the rows vanish even though a valid destination was still in the
field. Block the auto-dismiss-on-outside-interaction handlers so the
dropdown stays open as long as the input holds a candidate; it now closes
only on selection, on a cleared input, or via Escape.
Previously, clearing a selected chip in a prefilled flow (campaign "Pay
with Agora") restored the prefilled bitcoin: URI / address back into the
input. Removed that restore effect so X-ing out the chip now returns to an
empty field, letting the donor type or scan a fresh destination without
first deleting the prefill.
When the Send Bitcoin picker mounts pre-filled with a single valid
endpoint — e.g. a campaign with only a bc1 address (or only an sp1 code) —
it now auto-selects that candidate into the recipient chip instead of
leaving the bare value in the input behind a one-item dropdown the donor
still had to click.
Prefills carrying both an on-chain address and an sp1 code are left in the
input so the dropdown can surface both rows; picking privacy vs.
compatibility is a real choice the donor should make. Guarded by a
mount-once ref so it never overrides a manual selection or a clear-chip
restore.
The donate panel's copyable row only used a BIP-21 URI when a campaign
exposed both an on-chain address and a silent-payment code; single-
endpoint campaigns copied the bare bc1.../sp1... value instead. The QR
already encoded a bitcoin: URI in every case, so the copy row now mirrors
it — donors always get a wallet-parseable URI regardless of which
endpoints a campaign declares.
/campaigns was a redirect to / (the curated home), and the actual
all-campaigns directory lived at /campaigns/all. Flip the routing
so /campaigns IS the directory, the home page stays at /, and
/campaigns/all becomes a redirect to /campaigns for any external
links and bookmarks that still point there.
Rewrite every internal link/navigate target accordingly (TopNav,
the Browse-all CTA on the home page, the OnboardingGate donor
redirect, NoteCard's kind-33863 nounRoute) and refresh the
doc/comment references in NIP.md and the discovery hooks.
Two pieces of stale i18n caught up:
1. The 16 new campaignsCreate.categories.* keys (human-rights,
democracy, press-freedom, political-prisoners, humanitarian-aid,
civil-resistance, digital-rights, anti-corruption, women-girls,
refugees, legal-aid, emergency-relief, animal-rights, education,
medical, community) translated into all 15 non-English locales.
2. campaigns.all.sectionTagline rewritten across all 16 locales to
match the discovery-section fix that now lists featured campaigns
first and the rest of the network underneath, instead of
featured-only-with-fallback. Old copy ('Highlighted by moderators.
Search or sort to browse the full network.') implied search was
required to see non-featured campaigns, which is no longer true.
Swap the picker's preset list from the generic GoFundMe-style
catalog (adoption, animals, church, family, memorial, mission,
non-profit, event, first-responders, political) to a set that
reflects Agora's editorial focus on the kinds of activism HRF and
the World Liberty Congress champion: human rights, democracy,
press freedom, political prisoners, civil resistance, digital
rights, anti-corruption, women & girls, refugees & exiles, legal
aid. Plus humanitarian aid (per request), animal rights, emergency
relief, education, medical, and community to round out the
breadth.
16 entries total, ordered by editorial prominence (freedom /
democracy themes first, everyday humanitarian needs after). The
picker UI is unchanged \u2014 it iterates the array, so swapping
contents is enough.
Existing campaigns that selected one of the dropped slugs keep
their on-chain `t` tag intact \u2014 only the editor stops lighting up
a pill for them. No migration; we're pre-launch.
Strip the now-orphaned campaignsCreate.categories.* keys from the
15 non-English locales; the new English keys are in en.json only,
non-English locales will fall back to English at runtime until
proper translations land in a follow-up.
The home page community grid was missing approved campaigns whenever
the approval was older than the most recent 200 events on the
network. The grid was fed by a single `useCampaigns({ limit: 200 })`
call, so an approved campaign with a low `created_at` would silently
fall off the end of the chronological window and disappear from the
public surface even though its approval label was still active.
Two fixes here:
1. Add a second `useCampaigns` call keyed on every approved + hidden
coord, alongside the existing recent-stream query. Merge both
result sets, de-dupe by aTag, keep whichever revision is newer.
Approved coverage no longer depends on recency.
2. Restore the four-section layout the home page was supposed to
have: Featured, Community (approved only), Pending (mods-only),
Hidden (mods-only, collapsed by default). The single
chronological-all-with-toggle grid this commit replaces was the
wrong target \u2014 censorship-resistant viewing belongs on
/campaigns/all, the home page should be the moderator-curated
front door.
Extend ModeratorCollapsibleSection with an explicit `defaultOpen`
prop so the Hidden section can be forced closed independent of the
existing 'auto-open when short' heuristic.
mempool.space serves a 404 (instead of 429) to rate-limited clients,
which is common on carrier-NAT'd mobile connections where many users
share an egress IP. esploraFetch treated 404 as a legitimate "not
found", marked the endpoint healthy, and returned it WITHOUT failing
over — so getFeeRates threw 'Failed to fetch fee estimates', the query
swallowed it, and the on-chain Zap/donation dialogs showed no fee rates.
This is why fees loaded on WiFi but not LTE.
Add a per-call retryStatuses option to esploraFetch that extends the
retryable set (failover + cool-down) for that call, and apply [404] to
the paths that always exist on a healthy backend: /fee-estimates,
/address, /address/txs, /address/utxo, and the /tx broadcast. The
/tx/{txid} lookup keeps 404 meaningful (genuinely-unknown tx).
The idle (no search / no sort / no country) view of the campaigns
discovery section was a featured-only shelf with a fallback to
chronological only when nothing was featured at all. As soon as a
moderator featured one campaign, every approved-but-not-featured
campaign vanished until the viewer typed a search, picked a sort,
or filtered by country.
Switch idle mode to a true featured-first list: pin featured at the
top of the grid, then append every other non-hidden campaign in
chronological order, deduped against the featured set. Approved-
not-featured now shows up where viewers expect it.
Active mode is unchanged \u2014 it already rendered the full result set.
The section tagline still reads 'Highlighted by moderators. Search
or sort to browse the full network.' which is now slightly stale;
leaving the translation update for after we confirm the new
behavior in the wild.
The Show-hidden toggle in CampaignsDiscoverySection was gated to
moderators. Drop that gate so every viewer of /campaigns/all sees
the toggle and can unhide what mods have suppressed.
Rationale: moderation labels live on public relays regardless, so
hiding the toggle was security-by-obscurity. The Campaigns page is
the censorship-resistant browseable index; the only honest UX is
transparent moderation. The home page (/) keeps its curated
behavior \u2014 only mods see hidden campaigns there \u2014 and the Hidden
collapsible *below* the discovery section on /campaigns/all stays
mod-only because it's a review workflow with one-click hide/unhide
affordances, not a discovery surface.
The toggle's default is unchanged: off. Viewers see only non-hidden
campaigns until they opt in.
The HD-wallet Send dialog's fee popover relied on getUniqueBitcoinFeeSpeeds
falling back to all four preset tiers when rates hadn't loaded — rendering
clickable tiers with no sat/vB value (and no way to send at all when the
Blockbook estimate API was down).
- Show loading/error status (with a Retry) in the fee popover instead of
bare tiers when rates haven't loaded.
- Add a "Custom" fee tier with an inline sat/vB input so users can always
specify a rate, including when the estimate API is unavailable.
- Disable Send when the resolved rate is < 1 and surface an inline error.
- Add resolveBitcoinFeeRate + a PresetBitcoinFeeSpeed type so 'custom' is
handled distinctly from the preset tiers.
Comment out the two NAV_ITEMS entries (desktop nav and mobile drawer
share this array, so one edit covers both). Routes and feature code
stay intact \u2014 visiting /groups or /pledges still works, in-page CTAs
still link, only the persistent nav chrome stops promoting them.
Re-enable by uncommenting the two lines and re-adding the Users and
Megaphone icon imports.
The community grid stops gating on moderator approval and now lists
every kind-33863 campaign on the network, newest-first. A Switch in
the section header reveals the moderator-hidden bucket on demand (off
by default, count badge when something's there).
The moderator-only Pending and Hidden collapsibles disappear with
this change — Pending is now part of the main grid, and Hidden is one
toggle flip away. The non-mod 'Your campaigns' pending shelf goes
away for the same reason: a creator's not-yet-approved campaign
already shows up in the main grid.
Featured row, hero, and 'Browse all campaigns' link are untouched.
src/lib/countries.ts imported the full iso-3166 package solely to build
a Set of valid ISO 3166-2 subdivision codes for validation. That dataset
(~5000 objects with names, parents, and tree structure) landed in the
eagerly-preloaded countries chunk because NoteContent, ComposeBox, and
campaign.ts all import from countries.ts on the critical path.
Ship only the subdivision code strings instead, generated at build time
into src/lib/subdivisionCodes.ts via scripts/gen-subdivision-codes.mjs.
iso-3166 moves to devDependencies since only the generator script needs
it now. The strict-validation contract (rejecting US-ZZ etc.) is
preserved.
i18n.ts statically imported all 16 locale JSON files (~2.4 MB),
collapsing them into a single eager chunk that every user downloaded
on startup regardless of their language. Bundle the English fallback
only and fetch the other 15 locales on demand via dynamic import(),
so each language becomes its own lazily-loaded chunk.
This removes the 2.1 MB i18n chunk from the initial load; the eager
i18n chunk is now ~109 KB (runtime + English).
The previous commit left the home page with a single
CampaignsDiscoverySection (search/sort/country toolbar over one grid).
The original layout was richer and read better: a dedicated Featured
row, the Community Campaigns grid with a "Browse all" link, the
moderator-only Pending / Hidden collapsibles, and a per-viewer "Your
campaigns" shelf.
Rebuild that content area from moderation labels (useCampaignModeration
+ useCampaignModerators + useCampaigns), keeping the current hero and
leaving campaigns as the home page's sole focus. The shared discovery
components and the dedicated /campaigns/all, /groups, and /pledges pages
that consume them are untouched.
Regression-of: 7ccff2fb
The home page is the primary browse surface for campaigns and reads best
when it stays focused on them. Groups and Pledges each have their own
dedicated browse pages (/groups, /pledges), so surfacing all three on /
duplicated those experiences and diluted the page.
Drop the GroupsDiscoverySection and PledgesDiscoverySection from the home
page, leaving only CampaignsDiscoverySection. The shared discovery
components and the dedicated pages that consume them are untouched.
Regression-of: 7ccff2fb
The shortcut previously appeared only from step 3 onward. Once the
user fills the pledge amount on step 2 they're fully submittable —
title and description (the step 1 gate) plus a positive pledge
amount cover every required field. Forcing one extra Next click to
reach the shortcut on step 3 just to skip the rest was friction
for no benefit.
Moving the shortcut to step 2 reuses the same canAdvanceFromStep
gate the Next button does, so the button is visibly grayed out
until the pledge amount resolves to a positive sats value. Once
the amount is filled, both Next (continue to Cover) and Skip and
Launch (publish now) light up together and the user picks the
path. A minimal pledge is now two Next clicks plus a Skip and
Launch tap.
Two coordinated tweaks to the pledge create flow:
1. The free-form tag input is replaced with the same pill-style
CategoryPicker that campaigns and groups already use, drawing
from the curated 15-entry CAMPAIGN_CATEGORIES vocabulary. The
tag list emitted on publish is now ordered canonically (the
CAMPAIGN_CATEGORIES order) rather than insertion-order from
the comma-separated input — same posture campaigns and groups
adopted when they swapped pickers. Side effects:
- parseContentTagInput is no longer imported by this file
(still used by CreateEventPage and CreateCommunityEventDialog).
- pledges.create.tagsPlaceholder is dropped from en.json and
all fifteen non-en locales, since the picker has no
free-text input to placeholder.
- The step subtitle stays "Help the right people find your
pledge"; the title is renamed "Country and categories" to
match the picker (groups uses the same string).
2. The dedicated Deadline step is folded into the Pledge-amount
step. The two questions answer the same beat — "how much, and
by when?" — and a step that often gets skipped felt like
padding next to the amount field it conceptually belongs
with. The timezone subsection still reveals only once a date
is chosen, the date is still required to be present-or-future,
and the deadline tag still publishes only when a date is set.
Step count drops from 5 to 4: Title+Description, Pledge+Deadline,
Cover, Country+Categories. The Skip Next and Launch shortcut keeps
its from-step-3 placement (both required gates still clear by the
end of step 2), so a minimal pledge takes two Next clicks plus
one Skip and Launch tap.
i18n: deletes pledges.create.wizard.deadlineStepTitle and
deadlineStepSubtitle from en.json (they exist only in en so no
locale cleanup is needed). Updates pledgeStepSubtitle to mention
the optional deadline. Renames tagsStepTitle to "Country and
categories" to match the picker.
Pledges followed the original single-page stacked form for every
create. With campaigns and groups both running through the captive
wizard overlay, pledges were the odd one out — the FAB / hero CTA
landed on a long scrolling form while every other create flow
opened a focused step-by-step layout. This brings them inline.
Five steps:
1. Title + Description (both required; step 1 gates on both)
2. Pledge amount (required; gates on a positive sats preview so
the BTC/USD price has resolved before publish)
3. Cover image (optional)
4. Deadline + timezone (optional; the timezone subsection still
reveals only when a date is chosen)
5. Country + Tags (optional, terminal)
Skip Next and Launch appears from step 3 onward. Steps 1 and 2 hide
the shortcut because publishing without their fields would trip a
server-side validation error; once both required gates are
cleared, the remaining three steps are explicitly optional and a
single-tap launch is the desired escape hatch. Matches the same
posture the campaign wizard uses for its required title + wallet
gates.
Side cleanups while in the file:
- The local CountrySelect is replaced with the shared one. The
pledges.create.{countryClearAria, flagOfAria, countryHint}
locale keys were already absent from non-en locales (cleaned
out during the earlier campaign/groups extraction), so this
just removes the now-orphan en.json entries.
- pledges.create.{publishing, uploadingCover} were dead since
the page was already reading forms.publishing /
forms.uploadingCover; deleted from all sixteen locales.
- OrganizationContextChip now rides along inside step 1 as a
step1Lead, same treatment the campaign wizard gives it. The
captive overlay swallows the page header chrome, so the
"publishing under <org>" affordance has to live inside the
step body to stay visible.
No edit-mode path: pledges aren't editable today, and the file
mirrors that — there's a single create branch and that's it. If
edit support is ever added, the campaign / groups pattern (the
single-page form lives behind an isEditMode branch above the
wizard return) is the template.
i18n: adds pledges.create.wizard.{titleStepTitle, titleStepSubtitle,
pledgeStepTitle, pledgeStepSubtitle, coverStepTitle,
coverStepSubtitle, deadlineStepTitle, deadlineStepSubtitle,
tagsStepTitle, tagsStepSubtitle, launchNow} to en.json. Other
locales fall back to English until translated.
Groups require only a name to publish. The shortcut used to appear
from step 2 onward, which still forced one mandatory Next click
before the user could opt out of the remaining optional steps.
Moving it to step 1 lets a minimal group publish in a single
action: type a name, tap Skip and Launch.
The shortcut shares its disabled state with the Next button via
canAdvanceFromStep, so on step 1 it only becomes clickable once
the name field is non-empty.
Also tightens Wizard's canSubmit calculation: the mid-wizard
shortcut now respects the same canAdvance gate the Next button
does. Previously a launch button placed on a gated step would
remain clickable even when the gate was unmet, then trip a
server-side validation error. The terminal step's own submit
button keeps its old behavior because by definition every gated
step has already been cleared by then.
Two changes that go together:
1. The group create wizard now exposes a Skip Next and Launch ghost
shortcut from step 2 onward. Name is the only required field
(it is the gate on step 1 and the slug source); once a user
clears that step, everything else is opt-in and they should
not have to click Next, Next, Next through three optional
screens just to publish a minimal group. Matches the same
shortcut the campaign wizard offers from step 3 onward.
2. Edit mode now renders the original single-page stacked form
instead of the wizard, mirroring the create-vs-edit split the
campaign flow uses. Editing a populated entity benefits from
seeing all fields at once: every wizard step would already be
pre-filled, and walking through them adds friction without
adding clarity. The edit form reuses the exact same section
bundles the wizard does (nameDescriptionSection, coverSection,
moderatorsSection, countryCategoriesSection) so create and
edit stay byte-identical in their field rendering. Ordering
matches the pre-wizard page: name, description, country,
categories, cover, moderators.
i18n: adds groups.create.wizard.launchNow ("Skip Next and Launch")
to en.json. Other locales fall back to English until translated.
Groups used to render every field on a single long form. Now they
share the same captive overlay the campaign flow uses — sticky
progress bar across the top, one focused decision per step, top-left
back chrome and top-right escape, big rounded primary CTA. Four
steps:
1. Name + Description (gated; name is required to advance)
2. Cover image
3. Moderators
4. Country + Categories
The free-form 'mutual-aid, local-news, digital-rights' tag input is
replaced with the same pill-style CategoryPicker the campaign flow
uses, drawing from the same 15-entry CAMPAIGN_CATEGORIES vocabulary
so the two creation surfaces feel like the same product. Country
input uses the shared CountrySelect.
Edit mode behaviors:
- The d-tag stays immutable (kept as editCommunity.community.dTag).
- The pre-fill loop only pre-selects existing tags that exist
in the curated category set. Arbitrary tags an older
free-form entry may have published (e.g. 'mutual-aid') are
intentionally dropped from the picker — the user has no way to
re-select them, and silently re-publishing tags they can't see
would be a stealth foot-gun. Same posture campaigns adopted when
their tag input was swapped.
- The preserved-tag list in the edit branch already strips every
; nothing else changes there.
No 'Skip Next & Launch' shortcut here. Groups are only four steps
and three of them are optional, so a mid-wizard submit shortcut
would clutter the footer without saving real effort.
i18n: adds groups.create.wizard.{name,cover,moderators,tags}Step{Title,Subtitle}
to en.json. The non-en locales fall back to English for these new
strings until they're translated.
The wizard scaffolding (progress bar, captive overlay, step-aware
header chrome, Enter-to-advance keyboard handling) had been living
inline at the bottom of CreateCampaignPage.tsx as CampaignWizard and
WizardStep, and the category-pill picker was inline as well. Both
need to drop into the group-creation flow next, so they get lifted
into src/components/Wizard.tsx and src/components/CategoryPicker.tsx
with no behavioral change for the campaign page.
The campaign-specific bits — the org chip and the 'Skip Next &
Launch' shortcut — survive the move as optional props (step1Lead,
launchNowLabel) so the group flow can omit them without dragging
along irrelevant chrome. The wizard's Back / Next / close labels now
read from common.back / common.next / common.goBack, which both
flows can reuse.
CountrySelect had already been pulled out into its own component for
the calendar-event flow; it now gains the same localization the
inline campaign copy had (countryClearAria, flagOfAria, countryHint
move to the shared forms.* namespace, replacing the hardcoded
English strings the calendar-event flow shipped with) plus an
optional id prop so callers that own their own <label htmlFor> can
keep wiring it explicitly.
The three localized strings used to live duplicated under
campaignsCreate.* and groups.create.*; both copies are removed from
en.json and from every non-en locale so the locales test passes.
The grid layout forced every chip to the width of the widest label,
which left half the pills with awkward whitespace and the rest with
truncation pressure. Switching to a flex-wrap row lets each pill
size to its own text — short labels (Family, Legal) take less room,
long labels (First Responders) take more, and the row breaks
whenever the next pill wouldn't fit. Some rows naturally fit three
pills, others fit four, depending on which labels neighbor each
other on a given line.
Also drops Current Events from the curated set (it overlaps heavily
with the Event category and was usually mis-selected as a synonym)
and bumps the chip font from text-xs back to text-sm now that the
text is no longer constrained by a narrow grid cell.
Drops Competitive, Creative, Evangelism, and Business — those four
were the weakest fit for the kinds of fundraisers that actually run
on Agora (memorial drives, medical emergencies, mission trips,
mutual-aid efforts), and including them in the curated set diluted
the signal of the other 16. Also renames Animals / Pets → Animals,
which reads cleaner in the chip and avoids the awkward slash.
Locks the picker to a three-column grid (was 2/3/4 responsive) so
the full label is always visible — at the wizard's narrow max-w-md
column the previous two-column layout left half the chips with
truncated labels, and the four-column layout never had room for
multi-word categories like 'First Responders' or 'Current Events'.
Three columns gives every short label its own line and lets the two
long ones wrap to two; a min-h-[3rem] keeps the grid uniform.
The free-form 'beach-cleanup, mutual-aid, …' input asked donors to
invent and spell their own taxonomy on the spot, which produced
sparse and inconsistent tag data (no two campaigns used the same
slug for 'medical', the picker on the discover page never had a
stable set to filter against, etc). Replaces it with a fixed
20-category multi-select grid — Adoption, Animals/Pets, Business,
Church, Community, Creative, Current Events, Education, Emergency,
Evangelism, Event, Family, First Responders, Legal, Medical,
Memorial, Mission, Non-Profit, Political, Competitive — each chip
rendered with its Lucide icon.
Selected categories are persisted as ordinary lowercase 't' tags,
identical at the protocol level to anything the old input would
have produced, so existing readers (relays, the discover feed,
cross-client viewers) need no changes. Edit mode intersects the
event's existing 't' tags with the curated slug set so a campaign
created under this picker round-trips cleanly.
Also restores the previously-merged 'goal & deadline' and 'country &
tags' wizard steps as separate screens — collapsing them into one
turned out to push the category picker too far down the page on
mobile to be the first thing the user sees on the final step.
The wizard's step titles, subtitles, and footer button labels lived
only in en.json, so every non-English user saw the captive create
flow in English — even after the locale fell back gracefully for the
rest of the page. Adds the wizard subobject to all 15 other locales
with idiomatic translations matching each file's established voice.
The wizard's last two screens were each only ~one field of work:
goal+deadline (a USD input and a date) and country+tags (a country
combobox and a comma-list). Asking users to advance twice through
near-empty steps was busywork — both screens fit comfortably on the
same step without breaking the captive flow's vertical rhythm.
Collapses them into a single 'Goal, deadline, and tags' step, which
becomes the new terminal step where the Launch button lives. The
shortcut still appears from the banner step onward, so the wizard
remains a five-step flow with the same opt-in tail.
A <form> with a single text input treats Enter as submit. The wizard
sets the form's onSubmit to the publish handler, so hitting Enter on
step 1 (title) would call submitMutation.mutate() — and for a logged-in
nsec user the wallet picker already defaults to a valid HD-wallet
'mine' / 'all' configuration, so the publish actually went through and
the campaign launched after a single Enter on the title field. There
was no opportunity to fill in anything else.
Intercept Enter on the form's onKeyDown:
* If we're on the terminal step, do nothing — Enter should submit.
* If the focused element is a <textarea>, do nothing — Enter is a
legitimate newline inside the field.
* If we're mid-IME composition, do nothing — let the IME finish.
* Otherwise preventDefault and call the same "advance" logic the Next
button uses, gated by submitting + canAdvance so the gate behaves
identically.
Also wrap each child of the custom-wallet header in a block <div> so
the "← Use my Agora wallet" link stacks beneath the "Custom wallet"
title instead of sitting on the same line. Both children were
inline-flex; the parent's space-y-1 only adds margin between block
children, so on wide enough viewports the two pieces ended up
side-by-side.
Four small refinements after first review:
* Drop the card chrome (border + bg) around the identity row and
remove the pencil. The row is now a plain avatar + name + balance
display sitting on the wizard's transparent background — visual
confirmation of the destination, not a button. The "Use a custom
wallet instead" sub-link beneath becomes the only affordance for
the swap.
* Stack the "← Use my Agora wallet" link beneath the "Custom wallet"
heading instead of placing it on the same row. Two pieces of
hierarchy fighting for the same line was too much; the swap link
reads more clearly on its own line.
* Drop the icons (sparkles / bitcoin / radar) from the accept-mode
toggle pills. Each pill now carries just its label. The icons
were trying to compress meaning into one glyph each and the
captions already say the same thing.
* Expand the toggle labels to "Accept All" / "Public Only" /
"Private Only" — full enough to read as commands rather than tags.
Cleans up the lucide imports (Pencil, Sparkles, Bitcoin, Radar) and
locale key (walletEditAria) the previous version introduced and the
new version no longer needs.
The wallet step previously stacked two generic dropdowns (source +
accept) on top of two custom-address inputs that the user had to expand
explicitly. Every donation flow starts the same way: pick "my wallet"
and accept everything. The redesign treats that path as the default
view, not one of two dropdown options.
What changed:
* The Source dropdown becomes an inline identity card — avatar +
display name on the left, live USD/BTC balance on the right
(modeled on the wallet-page treatment), pencil affordance on the
far right. Tapping anywhere on the card swaps the view into the
custom-wallet inputs; a quieter "Use a custom wallet instead"
sub-link beneath it offers the same swap. From custom mode a small
"← Use my Agora wallet" mirror-link snaps back.
* The Accept dropdown becomes a three-pill segmented ToggleGroup —
All / Public / Private — with icons (sparkles / bitcoin / radar)
and a one-line caption beneath that explains the current
selection. The All and Private buttons disable when silent
payments aren't supported by the current login. Default stays
'all' (HD wallet with SP); empty toggle deselects are coerced
back to the previous value since the field is required.
* Balance comes from the parent's existing useHdWallet hook (passed
in via new `totalBalance` + `balanceLoading` props) plus an
in-component useBtcPrice call. Loading state shows a small
Skeleton in place of the price line; missing price falls back to
BTC-only.
* When no HD wallet is available (extension / bunker logins) the
picker collapses to just the two custom inputs with the existing
intro copy — no card, no toggle.
Existing locale keys are reused where the strings still fit; new
ones cover the toggle short labels, the captions, and the swap
affordances. The wider "Custom" label widens to "Custom wallet" so
the segmented header reads cleanly. Other locales fall back to
English on the new keys until the copy settles.
The previous four-step layout bundled title with wallet and banner with
story. Each pairing forced the user to mentally context-switch inside a
single screen. Splitting them out makes every step ask exactly one
question:
1. title
2. wallet
3. banner
4. story
5. goal + deadline
6. country + tags (terminal)
The 'Skip Next & Launch' shortcut now appears from step 3 onward — once
both required steps (title @ 1, wallet @ 2) are cleared. Earlier steps
hide the shortcut entirely so the user can't try to publish before the
wallet picker has been shown.
The wizard signature changes from positional step1..step4 props to a
single `steps` array plus a `canAdvanceFromStep` predicate and a
`launchAvailableFromStep` cursor, so future step inserts / removals
don't ripple through the type. Step state moves from a `1|2|3|4`
literal union to `number`, validated against `steps.length` at runtime.
Step copy is rewritten to be concise — one question, one line of
context. Other locales already fell back to English; the wizard keys
they don't yet have stay untranslated until the copy settles.
Four small refinements on the captive overlay:
* Drop the 'Step N of 4' eyebrow above each title — the sticky
progress fill at the top of the overlay already carries that signal,
and removing the duplicate keeps the focus on the step heading.
* Rename the launch shortcut on steps 1-3 from 'Launch campaign' to
'Skip Next & Launch' so its relationship to the primary Next button
is unambiguous. Step 4's terminal button keeps the 'Launch campaign'
label (it isn't a shortcut, it's the only forward action).
* Move the per-step Back affordance from a text link under the launch
button up to a round icon button mirroring the close X in the
top-left corner. The two header buttons now bracket the dialog
symmetrically and the footer stays focused on forward motion.
* Reverse the order of the banner and story fields inside step 2 so
the banner upload sits on top — it's the first thing a donor sees on
the campaign card and feels like the natural first decision when
telling the story.
Campaign launches still navigate to the campaign details page on
success via encodeCampaignNaddr in submitMutation.onSuccess; no change
needed there.
Mounts the create-mode wizard as a 'fixed inset-0 z-50' dialog so it
sits above the persistent TopNav, matching the captive OnboardingGate
signup flow. Creating a campaign is now a focused, distraction-free
task without the app's regular chrome competing for attention.
The page-level back arrow + heading are replaced by an unobtrusive
top-right X (same affordance as the onboarding overlay). The
OrganizationContextChip — previously sat under the page heading —
moves inline into step 1 so the 'publishing under <org>' context
isn't lost.
Edit mode is unaffected — it still renders inside the normal
FundraiserLayout with the page header intact.
Swaps the segmented-pill progress indicator and boxed step body for the
visual language Chad established in OnboardingGate: a sticky single-bar
progress fill across the top, a centered narrow column per step, a
centered eyebrow / heading / subtitle block, a big rounded-full primary
CTA, and a subtle text 'Back' link. Steps now fade-and-slide in on
transition so the swap reads as navigation rather than a re-render.
Step boundaries are unchanged. Step 1 still holds the required fields
(title + wallet) and gates 'Next' on a non-empty title; every step from
1 onward surfaces a ghost 'Launch campaign' shortcut so the rest of the
wizard stays opt-in. Step 4 is terminal — its only forward action is
the primary 'Launch campaign' button.
Edit mode is unaffected — it keeps the single-page form.
mkfain