---
description: Plan a documentation page: choose its content type, structure it, and assemble the parts it is built from.
title: Product content
image: https://developers.cloudflare.com/og-docs.png
---

[Skip to content](#main-content)

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/style-guide/llms.txt  
> Use this file to discover all available pages before exploring further.

# Product content

Last updated Aug 24, 2026|Copy as Markdown|[View as Markdown](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/index.md)|[Agent setup](https://e8aee267.previews.developers.cloudflare.com/agent-setup/)

This section is the planning layer of the style guide. It tells you what kind of page to write, where it lives, and what parts it is built from. The three areas follow the order you meet them when you plan a page. Once the page is planned, [Style and grammar](https://e8aee267.previews.developers.cloudflare.com/style-guide/style-and-grammar/) covers how to write it in the house voice.

## What to write

[Content types](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/) catalog the defined page shapes and help you choose the right one. Every type documents how it is structured, scaffolded, and maintained.

## How to structure it

[Information architecture](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/information-architecture/) governs on-page section order and the folder shape a reader navigates. [File conventions](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/file-conventions/) governs the repo file, folder, and image naming a builder works with.

## The parts a page is built from

[Component attributes](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/component-attributes/) covers the content-strategy parts of a page, such as introductions, prerequisites, and next steps. Formatting and component mechanics live in their own sibling sections, linked from each part.

## All pages in this section

* [Content types](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/)
* [Information architecture](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/information-architecture/)
* [File conventions](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/file-conventions/)
* [Component attributes](https://e8aee267.previews.developers.cloudflare.com/style-guide/documentation-content-strategy/component-attributes/)

Was this helpful?

YesNo

## On this page

[![](https://e8aee267.previews.developers.cloudflare.com/_astro/logo.te5VL_aD.svg)Docs](https://e8aee267.previews.developers.cloudflare.com/)

```json
{"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/style-guide/documentation-content-strategy/#page","headline":"Product content · Cloudflare Style Guide","description":"Plan a documentation page: choose its content type, structure it, and assemble the parts it is built from.","url":"https://developers.cloudflare.com/style-guide/documentation-content-strategy/","inLanguage":"en","image":"https://developers.cloudflare.com/og-docs.png","dateModified":"2026-08-24","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}
```