FAQ Template
A repeatable structure for FAQ question, answer, category, related service, and SEO context.
A content structure for product documentation and help articles — summary, prerequisites, ordered steps, examples, and related links, kept consistent as a Custom Content Type.
Use this structure for product documentation and help articles published as a Custom Content Type, so every document shares the same backbone.
Consistent documentation is faster to write, easier for Client Reviewers to check, and simpler to keep current as the product changes.
A starting set of fields for this structure. Adapt the labels, keys, and which fields are required to match your project.
The minimum fields every item should have before it can move to review.
Useful additions you can include per item, or leave out when they don't apply.
Search metadata for the item. Keep titles and descriptions unique per item.
How the structure looks as frontmatter in a Git-backed content file. Field keys map directly to your content type.
---
title: "Connect a repository"
summary: "Connect your GitHub repository through the GitHub App."
category: "Getting started"
seoTitle: "Connect a repository"
---
## Before you start
Content body…Confirm these before publishing the item through GitHub. The trigger result is recorded in Publish Logs.
Use Acrosite to create the structure, review content, schedule publishing, and keep output in GitHub.