Create your account

What this slide is

The “create an account” call-to-action. The precursor before the polls and breakouts. Frames why the audience should bother creating an account: Stacks, Polls, and future Dojo surfaces that don’t exist yet.

Why it’s here

Slides 05b (LP Conundrum) and 05c (From Yes to Win) need participation — filling out polls, claiming a breakout track. Participation requires an account. This slide is the quiet, friendly ask that unlocks the next 15 minutes of interactivity.

But the account unlocks more than this session’s interactivity:

• Between sessions — the June 24 cohort needs an account to be reachable; Stacks contributions accumulate over time.
• Working Groups & Projects — the surface where the dojo’s emergent cooperation actually happens. Currently seeded with strawmen, looking for facilitators to take them over (or replace them with better ideas).
• Future surfaces — once accounts exist, the next thing we cook up costs us nothing to add. Polls/proposals/matchmaking/etc.

The session-day participation is the urgent reason; the ongoing dojo coordination is the lasting reason.

The Working Groups + Projects framing (worth surfacing on the slide itself)

This is the meta-point most worth saying out loud:

All currently-listed Working Groups + Projects are strawmen — Michael’s thinking out loud, written down. The ones in green / Active are ones he’ll personally convene if no one else has the time. The rest are ideas he’s bumped into and thinks add value, looking for a facilitator.

But the dojo’s real bet is emergent cooperation. The strawmen exist to seed the surface — the point is for you to propose your own (or enlist in someone else’s) and run with it.

That paragraph belongs as a callout under the “Working Groups & Projects” value-prop card, or as a small caption when the audience’s eye lands on the /working-groups and /projects URLs.

What to surface

• The simple ask, big and friendly: “Please create your account and log in.”
• The three OAuth providers as visual buttons (Google Workspace · LinkedIn · GitHub) — logos if possible, otherwise wordmarks.
• The three value props as small cards: Stacks · Polls · Working Groups & Projects — each with a one-line body and a link to the relevant surface.
• The strawman / emergent-cooperation callout under the Working Groups card — this is the load-bearing meta-point. “All currently listed are strawmen. Green = I’ll convene. The rest are ideas looking for a facilitator. The dojo’s bet is emergent cooperation — propose your own.”
• The privacy line prominently, not buried: “Data will never be used for any reason other than better curating experiences for the Dojo.” People read this and it matters.
• A pointer to Michael’s profile at /people/mpstaton as the only fully filled-out reference — “here’s what a Stack looks like when someone takes the time.”
• The “not a company, just an initiative for the Dojo” framing — sets expectations correctly. This is community, not SaaS.
• The GitHub recommendation note — soft, not pressuring. “If you don’t have one, we recommend one anyway, for many reasons aside from OAuth.”

Visual hierarchy suggestion

• Top: big welcoming headline (“Please create your account.”) in --color-primary or --color-accent — feels invitational, not transactional.
• Subhead: “Two minutes. Unlocks Stacks, Polls, Working Groups & Projects — plus what we haven’t cooked up yet.” — direct, time-honest.
• Middle row, left: three value-prop cards stacked vertically (Stacks · Polls · Working Groups & Projects), each with heading + one-line body + link target.
• Working Groups card emphasis: small caption underneath — “strawmen now; emergent cooperation is the bet” — links to /working-groups and /projects.
• Middle row, right: three OAuth provider buttons as a vertical stack, each with the provider’s brand color, with the small note next to each one.
• Bottom row: privacy line in subdued (--color-text-muted) text, with a link to Michael’s profile as a small chip — “see Michael’s Stack →”.
• Footer touch: the “not a company” line as a small chip, low-emphasis, lower-left.

Whole composition should feel warm and frictionless — not corporate, not enterprise-y. The audience is being asked to trust the host, briefly. The slide’s voice should match.

The “vibe-coded” disclaimer (small, friendly, lower-right)

Render the disclaimer_vibe_coded line in a small chip or footnote near the bottom of the slide, in --color-text-muted. It’s an honest acknowledgment that this whole platform is being built in real time with AI co-development — the audience appreciates the candor, and it reduces the cost of a glitch happening during the actual login attempt. If someone hits a weird error, they remember the disclaimer and don’t lose trust in the dojo.

Recommended phrasing on the slide itself (matches the user’s voice):

We’re vibe-coding this whole thing with Claude Code + Pi.dev. If something glitches mid-login, that’s par for the course — we’ll fix it once we understand it (Claude usually has to explain it to us first).

Why this slide stays AHEAD of 05b/c

If the audience hits the LP conundrum poll (05b) and is told “log in to vote,” they’ll either skip or bounce. Putting the account ask BEFORE the participation surface gives them the why first (Stacks/Polls/Future) and removes the in-the-moment friction. Sequence matters.