Skip to content

Move outreach scripts from atleast-leads into this repo #185

Description

@leogdion

Summary

Keep lead data private in brightdigit/atleast-leads, but move the remaining scripts into this public site repo so all outreach tooling lives next to the finders.

This is possible without exposing contact details: finders (scripts/find-*.js, verify-leads.js) already live here and write to gitignored leads/. Only drafting tooling is still nested inside the private checkout.

Current split

Location What
This repo scripts/ find-leads.js, find-studios.js, find-podcasts.js, verify-leads.js, config
Private leads/scripts/ make-drafts.py (used by make drafts), archival _build_outreach_plan_2026_08_24.py
Private leads/ (stay) reports/, plan/, drafts/, templates/

Proposed work

  1. Move make-drafts.pyscripts/make-drafts.py in this repo.
  2. Point LEADS_DIR at the sibling leads/ checkout (today the script assumes it lives under leads/scripts/).
  3. Update make drafts in the Makefile to call the new path.
  4. Update AGENTS/CLAUDE and the private leads/README so atleast-leads is documented as data-only.
  5. Remove scripts/ from the private repo (or leave a short pointer) on the next leads snapshot.
  6. Decide whether the archival plan builder moves here too or stays in the private repo as history-only.

Leave templates/ in the private repo (outreach copy, not site content).

Out of scope

  • Publishing any reports, plan entries, drafts log, or contact details into this repo.
  • Changing the leads-clone / leads-pull / leads-backup workflow for the data checkout.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions