Fill once. Your Worker runs the queue.

Step-by-step (read once)

1. What you’re looking at. This site (aidensocial.pages.dev) is your branded front door. The real engine is a separate Worker URL (given to you by your operator). Buttons here open that console once config.js points at it.
2. Colors. Black background and yellow accents match swarmmm.com / SWARM marketing so your clients feel the same product family. Your accent picker below still overrides what gets saved into the Worker for emails/UI bits that read that color.
3. Fill the form. Business name, tagline, contact email, which networks you use (X, LinkedIn, Reddit, Dev.to), and cadence — that controls how many draft posts we seed across ~two weeks (Light / Standard / Aggressive).
4. Topics & hashtags. Topics rotate through drafts. Hashtag packs append when it makes sense. Caption template is optional; leave blank for a sensible default.
5. AI captions. If checked, the Worker can rewrite drafts using Cloudflare Workers AI (Llama 3.3 70B) — no OpenAI key required if your Worker was deployed with the AI binding.
6. API tokens (optional). Expand “paste API tokens” if you already have access tokens; otherwise skip and add them later in the operator console. Without tokens, drafts still queue, but nothing can publish until at least one network is connected.
7. Submit. Press Send → enable autopilot. That one POST saves settings, stores optional tokens, turns the account on, and seeds scheduled drafts. From then on, publishing runs on the Worker’s clock (hourly batch + your schedule).
8. After submit. Use Operator console to edit posts, tokens, or turn things off. Usage and errors show in the Cloudflare dashboard for whoever owns the Worker.
9. Billing. The “Billing” button should point to your Stripe products — SWARM’s main checkout on swarmmm.com is unrelated to this deployment.

Why “SWARM” styling? Your operator runs this on the same stack family as SWARM (Cloudflare Workers, D1, terminal-yellow UX). Matching swarmmm.com keeps the story consistent for your customers without mixing their data into the shared SWARM SaaS database.