• Operating pleb.school: creators and admins
  • Drafts and publishing
  • Admin content management
  • Payments and purchases
  • Analytics and operations
  • Next steps for self-hosters

§Operating pleb.school: creators and admins

§Drafts and publishing

• Admins create drafts at /create
• Drafts live in the database until published
• Publishing signs a Nostr event (NIP-07 for Nostr-first, server-side for OAuth-first)
• Courses publish lesson resources first, then the course list event
• Published items are linked by noteId for fast lookup

§Admin content management

Profile > Content (admin tab) lets you:

• Inspect published courses and resources
• See whether Nostr notes are in sync
• Edit metadata and republish
• Delete items only when they are not tied to purchases or lessons

§Payments and purchases

• Zaps are Lightning payments with Nostr receipts
• Purchases are claimed when receipts meet the price
• Partial payments are supported; users can unlock with past zaps
• Purchase records live in the database for access checks and audit

§Analytics and operations

• View counts are tracked via KV with a database fallback
• Admin analytics summarize platform activity
• Admins are detected via database roles or config/admin.json pubkeys

§Next steps for self-hosters

• Configure auth providers, relays, and branding
• Seed your instance with your own content
• Decide your moderation and pricing strategy

This is the operational heart of pleb.school: simple for learners, powerful for operators.