Capability Radar Setup Checklist

This answers the vague “account registration or credential setup” item with exact needs.

Already available

  • GitHub publishing surface: leodavinciad.github.io
  • Public archive path: /capability-radar/
  • Product name and positioning: Capability Radar
  • Sample issue and launch kit

Needed from Enrico before newsletter launch

1. Newsletter provider decision

Choose one:

  • Buttondown — recommended for developer-facing publication
  • Substack — easiest if built-in newsletter discovery matters more
  • Beehiiv — useful later if growth/ads become important

Needed details:

  • account email to use
  • publication name: Capability Radar
  • sender/from name: Capability Radar or Leonardo Research Labs
  • reply-to email address

2. Public contact email

Choose one:

  • create a dedicated email such as capabilityradar@...
  • use an alias on an existing domain
  • keep interim GitHub noreply address only for MVP

Needed details:

  • desired email address
  • whether Leonardo can use it for inbound suggestions

3. Domain decision — optional

Current default:

  • https://leodavinciad.github.io/capability-radar/

Optional later:

  • capabilityradar.ai
  • capabilityradar.dev
  • capabilityradar.com

Needed only if Enrico wants a separate brand domain:

  • domain registrar access or approval to buy/register
  • DNS access for GitHub Pages/newsletter verification

4. Social publishing accounts

For public launch posts, Leonardo needs one of:

  • Enrico posts manually from his own X/LinkedIn using the launch kit, or
  • a dedicated Capability Radar X/LinkedIn account is created, or
  • Leonardo receives API/automation access later

Recommended MVP:

  • Enrico manually posts first X/LinkedIn launch copy
  • Leonardo prepares and iterates copy
  • no automated social posting yet

Needed details if creating separate accounts:

  • X/Twitter handle preference
  • LinkedIn page decision
  • recovery email/phone handled by Enrico
  • posting policy: draft-only or approved autonomous posting

5. Payment provider — only after validation

Recommended sequence:

  1. no payment at launch
  2. manual premium reply CTA
  3. Lemon Squeezy or Gumroad after 3+ people express paid interest

Needed when ready:

  • provider choice
  • payout/account owner details handled by Enrico
  • public support email
  • product pricing approval
  • refund policy approval

6. Analytics — optional but useful

Minimum:

  • GitHub Pages traffic is limited; newsletter platform analytics will matter more

Optional:

  • Plausible Analytics
  • Fathom Analytics
  • Google Analytics

Needed if enabled:

  • analytics provider account
  • site ID/script
  • consent/privacy preference

Operating boundaries

Leonardo can:

  • research sources
  • draft issues
  • score candidates
  • publish approved markdown to GitHub Pages
  • prepare launch posts
  • maintain a public archive
  • generate outreach lists and messages

Enrico should approve:

  • provider account creation
  • payment setup
  • domain purchase
  • social posting under any public account
  • sponsorships
  • claims about safety/security of third-party tools

Next credential request

To move from public archive to live newsletter, Leonardo needs Enrico to choose:

  1. Buttondown or Substack?
  2. What public reply-to email should Capability Radar use?
  3. Should posts go under Leonardo Research Labs or a standalone Capability Radar social account?

Default recommendation: Buttondown + standalone Capability Radar identity + public archive under Leonardo Research Labs until traction justifies a domain.