Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Epic: get new organizers from a draft to a shared link

Aperta
  • Qualcosa non va?
#498 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
full-stack

Direzione di ricerca

This is an umbrella plan whose implementation is split across issues #499–#506; start by reading those sub-issues and the linked design canvas, especially row C. The plan defines a multi-step organizer flow, measurement goals, and dependencies, but does not name files, tests, or code entry points. Done means the planned flow and measurements are implemented across the sub-issues.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

This tracks the plan. Each sub-issue carries its own pipeline:proposed label and needs your OK on its own.

The problem

Most new organizers who stop do so before they publish, and in their first session:

  • AI drafts: people open the draft and leave without editing it.
  • Hand-built drafts: people stall after the first slot or two.
  • Publish: it's easy to miss, especially on a phone.
  • Coming back: nothing brings an organizer back to an unfinished draft.
  • Sharing: some published signups never get their link shared.

Participants who reach a page mostly sign up fine.

This comes from a funnel review of production data and a check of drafts that were never published. The figures stay out of this public repo.

The plan

New drafts land on a short page, "Check your signup, then share it", instead of the Build tab. The page:

  • shows the signup the way people will see it;
  • points out problems the code can prove, with a one-tap fix for each;
  • puts Publish front and centre.

A share step after publishing and a one-time reminder email about unpublished drafts cover the two ends.

Design

The design is on a canvas: https://claude.ai/artifact/RqcjzCcdSTw5JhbXjm2x5y. It's private until it's shared from its Share menu. Row C is this plan:

  • C · Check and publish: an AI draft with two problems: the review page. It's clickable.
  • C · After the two fixes, editing one slot
  • C · The same card on four common shapes (made-up data)
  • C · Share step (phone)
  • C · Same-day draft email

The "Today" row has screenshots of the current flow. Rows A, B and D are other directions and aren't part of this plan.

Order

  1. #499 Make Publish hard to miss, and say when it fails (with #457).
  2. #500 Record link copies, failed AI drafts and refused publishes. Ship this before #502, so its effect can be measured.
  3. #501 Magic Compose: one slot with N spots, not N copies of a row.
  4. #502 Land new drafts on a "Check your signup, then share it" page.
  5. #503 Find fixable problems in a draft and offer one-tap fixes.
  6. #504 Edit slots from the review page.
  7. #505 After publishing, help the organizer share the link.
  8. #506 Email organizers once about a draft they haven't published. It has three decisions for you.

#499, #500 and #501 don't depend on each other and can be built in parallel. #503 and #504 need #502.

How we'll know

Compare before and after on:

  • the share of new drafts published within a day;
  • review-page notices shown against notices accepted, by kind (#500);
  • link copies after publishing.

Not in this plan

  • A better start for hand-built signups. Direction D on the canvas: days × shifts × people. Empty drafts need this more than any review.
  • Change a draft by asking. Direction A, available when an LLM is configured. It's for organizers who re-create the same signup again and again.
  • A dashboard hint when several drafts look like the same event.
  • Rejected along the way: generating a custom editor from each signup's shape. It needed nine layout combinations and still couldn't correct a single value.

Planned in https://claude.ai/code/session_01AkZbMUc4ej4ed7o5uh6nqr

Lingua principale
TypeScript
Stelle
19
Fork
4
Merge medio
21h 3m
PR unite (30g)
176

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di richshaw/OpenSignup

Tutte le issue di richshaw/OpenSignup

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.