The AiContextGateway Context Hub — page format and publishing

How to publish on the AiContextGateway Context Hub: page types, skeletons, slug and honesty rules, submission and review flow, markdown twins, CC BY 4.0.

The AiContextGateway Context Hub — page format and publishing

Product summary

The Context Hub is a public library of AI-readable product-context pages. Every published page exists twice: as an HTML page at /hub/{slug} and as a Markdown twin at /{slug}.md that agents fetch directly — same body, plus platform-generated frontmatter and a sources-and-freshness footer. Pages are independent, community-maintained context grounded in each product's own public documentation; they are not affiliated with the companies they describe, and the twin says so explicitly. Anyone with an account can submit a page; a moderator reviews every community submission before it is published.

Key concepts

term meaning
Page type end-user-help (task answers for a product's users) or product-how-it-works (a product surface explained).
Skeleton The fixed heading structure a body must follow; the submit form inserts it for you.
Slug The page's URL identity: the product name, or product plus the product's own role word.
Markdown twin The agent-facing copy at /{slug}.md; its frontmatter and sources footer are generated, never hand-written.
Moderation Community pages enter review on submission; a moderator publishes, returns, or archives them, optionally with a note.
CC BY 4.0 The license every submission is granted under, confirmed at submit time.

How common tasks work

Pick a page type and follow its skeleton

task where steps notes
Choose the type submit form 1. Pick end-user-help for "how do I ..." answers aimed at a product's users. 2. Pick product-how-it-works to explain how a product surface operates. The form inserts the matching skeleton so the headings start correct.
Fill the skeleton body editor 1. Keep the section headings exactly as given. 2. Write Markdown only — no frontmatter block. 3. Do not write a "Sources & freshness" section — the platform appends it to the twin. The preview warns when sections drift from the skeleton.

The product-how-it-works skeleton:

# {Product} {Surface} — how it works

## Product summary
{3-6 lines: what the surface is, who operates it, what it manages.}

## Key concepts
| term | meaning |
| --- | --- |
| {term} | {meaning} |

## How common tasks work
### {Task group}
| task | where | steps | notes |
| --- | --- | --- | --- |
| {task} | {product's own named area} | {numbered capability-level summary} | {fees/limits/prereqs, dated} |

## Limits & gotchas
- {dated bullet, verifiable against a cited source} (as of {month year})

## FAQ
### {Literal question phrasing}
{2-5 line answer.}

The end-user-help skeleton:

# {Product} — how common {role} tasks work

## Product summary
{2-4 lines.}

## What people ask
### {Task phrased as the user query, e.g. Cancel a reservation}
1. {Numbered capability-level steps.}
{What to expect afterwards, one line.}
{Verify in the product: policies vary by {dimension}.}

## Good to know
- {policy/limit bullet} (as of {month year})

## When to contact support
{The boundary: what this page cannot resolve + where the official channel is.}

Choose a slug

task where steps notes
Name a default consumer page slug field 1. Use the bare product name, like airbnb or spotify. Lowercase letters, digits, and hyphens only; at most 80 characters.
Name a role page slug field 1. Use the product plus the product's own role word: etsy-seller, shopify-admin, airbnb-host, facebook-merchant. Use the vocabulary the product itself uses for that role — not a generic audience label.
Check availability slug field 1. The form checks the slug live and reports taken, reserved, or invalid. Reserved words (product routes and brand terms) are rejected; slugs starting with aicontextgateway are reserved for founder-published pages.

No filler tokens: slugs never end in -guide, -how-to, or -docs.

Meet the honesty bar

task where steps notes
Source every claim body + source URLs 1. Use only the product's own public documentation. 2. List at least one source URL per page — the load-bearing ones. Logged-in-only surfaces are out of scope.
Write steps honestly body 1. Keep steps capability-level. 2. Quote exact UI labels only when they appear in a cited source. 3. Date time-sensitive facts with "as of {month year}". 4. Add "Verify in the product: ..." wherever behavior varies by account, region, or plan. Undated fees and invented click-paths are the most common review returns.
Respect the marks body 1. Use product names as word marks only — no logos, screenshots, or brand-color mimicry. 2. Never claim to be official or a partner. 3. Describe the product itself — never AiContextGateway acting on that product. The platform appends an independence disclaimer to every twin.

Submit, review, publish

task where steps notes
Draft submit page (signed in) 1. Pick the type. 2. Insert the skeleton. 3. Write the body, a summary of at most 160 characters, and the source URLs. The summary doubles as the page's meta description.
Preview submit page 1. Check the rendered preview and table of contents. 2. Resolve section warnings before submitting. Warnings mean the headings drifted from the skeleton.
Submit submit page 1. Confirm the CC BY 4.0 license grant. 2. Submit — the page enters review. Gate checks reject secret-shaped content and oversized bodies before review.
Track review submit page 1. Watch your submissions list: draft, in review, published, or archived, with any moderation note. Returned pages come with a note explaining what to fix.
Go live /hub/{slug} 1. On publish, the HTML page and the /{slug}.md twin go live together. The twin carries generated frontmatter, source links, a last-verified line, and the independence disclaimer.

Limits & gotchas

FAQ

Do I write the frontmatter or the Sources & freshness section myself?

No. The body is pure Markdown starting at the H1. The platform generates the twin's frontmatter (title, type, product, audience, summary, sources, freshness date) and appends the Sources & freshness footer and independence disclaimer.

Which slug should I pick?

The bare product name for the product's default consumer page, or product-plus-role using the product's own role word (etsy-seller, shopify-admin). Lowercase, hyphenated, at most 80 characters, no -guide or -how-to fillers. The form tells you live whether it is available.

Who reviews my page, and how do I see the status?

Community submissions are reviewed by a moderator before publishing. Your submissions list on the submit page shows each page's status — draft, in review, published, or archived — plus any moderation note left for you.

What license do I grant?

CC BY 4.0, confirmed with a checkbox at submission. The published twin mentions the license, and attribution-based reuse of published pages is expected — including by AI agents fetching the Markdown twin.