WEBSITESfor Normal People2026

Part V: Keep These Handy (use them when you need them)C

Appendix C

Appendix C: Every human step, and where the keys live

2 min read

Only the steps your site needs.

Start with the accounts and the local build. Come back for the rows that apply to your site. These are tasks, not a promise that every sign-up takes one click.

Your part, in order

Your clicks, ticked off

0/ 16

Cloudflare upgrades are conditional too. Have the agent explain the plan and expected bill before you approve one.

Where access lives

Access or secretCreated byNeeded whenKept where
cf local loginBrowser sign-in you approveSharing and managing previewsThe CLI's credential storage; do not export it
GitHub local loginBrowser sign-in you approveSaving the codeGitHub CLI's credential storage
Bitwarden access tokenYouExtra service secretsYour computer's keychain
CLOUDFLARE_DEPLOY_TOKENYou, scoped with the agentOptional GitHub ActionsVault and Actions secret, mapped to CLOUDFLARE_API_TOKEN in the job
CLOUDFLARE_ACCOUNT_IDAgent looks it upAccount selection / optional CIProject config or Actions secret; this is an ID, not a password
TURNSTILE_SECRET_KEYAgentFormsWorker secret; optional vault backup
PAYLOAD_SECRET / PAYLOAD_ADMIN_PASSWORDAgentCMSVault, and Worker secret for PAYLOAD_SECRET
STRIPE_SECRET_KEY / STRIPE_WEBHOOK_SECRETYou / agentStoreVault and Worker secrets; separate test and live environments
GOOGLE_SERVICE_ACCOUNT_JSONAgentAnalyticsVault

When access expires

Use the relevant browser sign-in again for local access. For a CI token, follow its recorded renewal instructions in Appendix B. Do not create a broad bootstrap token just to fix an expired local login.

On a phone, swipe left and right to turn pages.