This is a set of public, cross-product solution guides I authored for the Cloudflare developer documentation site. They sit outside any single product’s docs at /use-cases/solutions/ and answer a question product-siloed docs could not: which Cloudflare products do I combine to solve this customer problem?
Each guide starts from a customer goal, not a feature, and walks a complete workflow across multiple Cloudflare products. The guides prioritize paths available to lower-tier plans where possible, while clearly marking higher-tier capabilities in the main flow.
Before this collection existed, the docs site had no cross-product, goal-first content for this kind of workflow. I built the content type, the authoring model, and the first guides. This case study covers the guides themselves as writing samples; the companion case study, Solution Guide Content Type & Authoring System, covers the content model and the agentic authoring workflow.
Project context
Customers regularly asked how to combine Cloudflare products to accomplish a security or delivery outcome, but the existing documentation assumed the reader had already chosen a product. A reader who knows they want to “stop malicious bots” had to already know which products and features to assemble before the docs were useful.
The solution guides close that gap. They are organized by workflow stage rather than by product, each section has a clear outcome, and the core workflow is achievable on a Free or Pro plan, with higher-tier capabilities placed in plan-aware callouts rather than the main path.
My role and ownership
I authored four of the first cross-product solution guides:
- Defined the goal-first structure: outcome-oriented titles, workflow-stage organization, applicable plan tiers, and plan-aware headings so a scanning reader could immediately see which sections applied to them.
- Wrote the guides against source product documentation as the canonical truth, reusing existing procedures through shared partials rather than paraphrasing them, so the guides stayed correct as the underlying products changed.
- Curated each guide’s related-resources section as a short next-step reading list rather than a bibliography of every page consulted.
What the work solved
Cross-product assembly. Readers got one workflow that connected multiple Cloudflare products instead of having to stitch together separate product docs. Goal-first discovery. A reader could start from a problem, such as stopping malicious bots or protecting forms from abuse, without already knowing which product path to follow. Plan-aware execution. The guides kept the main path broadly usable and marked higher-tier capabilities clearly, so readers could tell what applied to their account before investing in the workflow.
Deliverables
Documentation produced:
- Four authored cross-product solution guides covering bot mitigation, encrypting site traffic, protecting forms from fraud and abuse, and account-takeover defense
- The
/use-cases/solutions/hub that organizes the collection - Shared procedure partials extracted from product docs so guide steps and source pages render from one maintained file
Tools and workflow:
- Markdown/MDX in the public
cloudflare/cloudflare-docsGitHub repository - Git, pull-request-based docs-as-code workflow with peer review
- Reusable partials and components from the Cloudflare docs platform
What this sample demonstrates
- Goal-first, Jobs-to-be-Done information architecture across product boundaries
- Cookbook-style procedural writing for real customer workflows
- Source-of-truth discipline: writing from canonical product docs and reusing shared partials where possible
- Docs-as-code authoring and review in a large public GitHub repository
- Plan-aware judgment that keeps guidance useful without flattening product differences
Live documentation
Live links go to the production guides. Because public documentation evolves as other contributors maintain it, each entry also links an archived snapshot that preserves the page close to when I authored it.
- Solutions hub — all cross-product guides — archived snapshot
- Stop malicious bots while allowing legitimate traffic — archived snapshot
- Encrypt all traffic and keep your site secure — archived snapshot
- Protect sensitive forms from fraud and abuse — archived snapshot
- Stop account takeover attacks — archived snapshot
Source pull requests
Each guide was merged through the public cloudflare/cloudflare-docs GitHub repository. These pull requests are a verifiable record of authorship — the commit history, diff, and date stay fixed even as the live pages are maintained over time.
- Stop malicious bots (#29531)
- Encrypt all traffic (#30251)
- Protect sensitive forms (#30456)
- Stop account takeover attacks (#30049)
- Create the cross-product solutions section (#29874)
Documentation excerpt (curated)
A short excerpt from “Stop malicious bots while allowing legitimate traffic” shows the two signature moves of the content type. The title leads with the customer’s goal and names the applicable plans, and section headings carry the plan tier so a reader sees at a glance which sections apply to them.
Stop malicious bots while allowing legitimate traffic (Free, Pro, and Business)
The right defense against malicious bot traffic depends on the traffic patterns on your site and your plan. This guide covers a layered approach using Cloudflare Bots, Cloudflare Application Security (also known as Web Application Firewall or WAF), and Turnstile, from baseline protection to targeted custom rules. The core workflow uses features on Free, Pro, and Business plans, with callouts for Enterprise options.
Block automated traffic with Bot Fight Mode
Bot Fight Mode identifies requests that match known bot patterns and issues a computational challenge. It reduces automated traffic across your entire site without requiring you to write any rules.
Turn on Bot Fight Mode (Free plan)
Dashboard steps omitted for brevity.
Enable Super Bot Fight Mode (Pro, Business, and Enterprise)
Super Bot Fight Mode adds verified bot allowlisting, per-category actions, static resource protection, and JavaScript detections.
I managed Cody at Cloudflare, and he came in and built something we didn’t have yet. Customers had been asking for help navigating across products, and nobody had cracked how to do that well in the docs. Cody designed the solution guides experience from the ground up. He developed the strategy, reuse framework, and AI-assisted authoring so other writers could contribute without it becoming a bottleneck. Solution engineers and customer support managers started sharing them with customers almost immediately.
— Caley Burton, engineering manager, Cloudflare (managed Cody directly)