Skip to content
Aa

Curated F5 documentation in Markdown

Product documentation, support articles, community guides, and solution pages converted to linked Markdown. Browse the collection or use it with your documentation tools.

Curation policies select relevant content and remove material outside the collection’s scope. Retained documents keep useful headings, examples, links, and reviewed images. See the active content filters.

Browse the collection

From sources to topics to documents

697 curated documents from 4 sources. Choose a source, narrow the topic, then open a Markdown document.

This collection is a reviewed subset of four public sources. It includes F5 Distributed Cloud product documentation and MyF5 support articles; F5.com is limited to the Distributed Cloud product family and three reviewed solution pages. Community articles come only from reviewed first posts in F5 Technical Articles, Community CodeShare, and F5 Security Insights. Forums, news, events, unrelated product pages, and community posts or media awaiting review are excluded.

Each snapshot applies these content filters in order:

  1. Authored legacy classifications: Remove pages explicitly limited to legacy F5 deployments. Mixed current guides require reviewed removal of retired sections, dependencies, and images. Delegated Domains and unsupported API namespace migration guidance are excluded.
  2. Secure Mesh Site transition: Remove SMSv1 Fleet and legacy cloud-site procedures. Keep Secure Mesh Site v2 guides and independent VPC, VNet, and TGW networking material.
  3. AppStack retirement: Remove AppStack and VoltStack site guidance, retired API identities, and managed Kubernetes procedures that require an AppStack Customer Edge site. Keep complete independent Kubernetes, vK8s, Mesh, and networking explanations.
  4. vesctl retirement: Omit every document that references vesctl in its title, metadata, text, examples, captions, or links. No replacement is added.
  5. Terraform provider: Remove instructions, examples, and linked modules for the retired volterraedge/volterra provider. Add current xcsh documentation links only where the mapping is qualified; keep independent cloud infrastructure and Terraform explanations.
  6. API reference: Exclude superseded docs-v2/api and platform/reference/api-ref pages. Move legacy links to the pinned enriched API reference using exact operation or resource identities, with a general index for unresolved matches.

Dependent sections, steps, billing and release-note entries, links, and diagrams are removed. A page is omitted when it no longer has a complete independent explanation. Source and media reviews are checked again when their inputs change.

The topic policy, AppStack review decisions, API-reference policy, and community reviews contain the exact rules. Use the publication details to identify the source commit for a published snapshot.