Weekly Cloudflare docs & feature digest
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Every Friday, review Cloudflare's developer documentation for the areas my project relies on, and email me a prioritized digest of best practices, newly-documented features, and anything I should act on. Read and report only — never deploy or change my Cloudflare setup. Tell me my stack below, then each run: - What I run on Cloudflare: <e.g. Workers, Pages, R2, Durable Objects, DNS + SSL for one domain> 1. Check the areas I use. Using the Cloudflare Docs tool, look up the current best-practice guidance and configuration for each area of my stack (e.g. Workers limits, Pages build config, SSL/TLS mode, rate limiting, DDoS settings). Note anything the docs now recommend that's worth a second look. 2. Surface newly-documented features. Flag features, APIs, or options in my areas that I may have missed — especially ones the docs describe as new, recommended, or replacing an older approach. Be honest about what the docs actually say; don't infer a release date the docs don't state. 3. Add recency from the web. To catch what changed *this week*, also run a web search for recent Cloudflare changelog / blog / "what's new" posts in my areas, and pull the concrete item + link. (Docs show the current state; the changelog shows what moved.) 4. Prioritize and email. Rank by impact: breaking changes / deprecations first, then new capabilities worth adopting, then clarifications. One line each with a doc or changelog link. If it was a quiet week for my areas, say so plainly rather than padding. Never invent a link or a version — only report what you actually found in the docs or a real changelog post.
How it works
- Attach Cloudflare Docs (free, keyless) on the Connections page — the routine searches Cloudflare's developer documentation for the parts of the platform you actually run.
- It reports the current best-practice config for your areas and flags newly-documented features, then pairs that with a web search for recent changelog posts so you also catch what changed this week — not just the current state.
- Keep "Email me the result" on to get a prioritized digest every Friday, breaking changes first.
Make it yours
- Name your stack precisely — Workers only, Pages + R2, or "DNS and SSL for one domain" — so the digest stays relevant and short.
- Adjust the cadence — weekly by default, or daily during an active migration.
- Ask for a config-audit angle instead: "compare the docs' current recommendations against this setup: …" and have it flag drift.
This routine only reads documentation and reports — it never deploys, edits, or touches your Cloudflare configuration.
Run “Weekly Cloudflare docs & feature digest” on autopilot
Copy it to your account, tweak the details, and it runs fridays at 9:00 am.
Use this routine →More Engineering templates
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.
Each weekday, triages new, stale, and needs-triage issues across the repos you pick — grouped, prioritized, with a suggested label and owner per issue.
Logs each repo's weekly releases as rows in a Google Sheet, so nothing slips.