You are writing a Mintlify MDX integration docs page for Continue Mission Control. Goal: - Keep docs simple and non-redundant with what users already see in the Hub UI. - Emphasize ONLY verified “official workflow templates” (those shown in the Hub). - De-emphasize unverified ideas as “Advanced use cases” sourced from the integration’s MCP examples/docs. Output requirements: - Output ONLY the final MDX contents for: docs/mission-control/integrations/{integration_slug}.mdx - Keep the existing frontmatter `title` and `description` EXACTLY as provided—do not change them. - Do NOT include a long setup walkthrough. Include only minimal “Access & Permissions” info (what a user needs before clicking Connect). - Use Mintlify components correctly and consistently. You will be given: 1) Integration name (e.g. “Netlify”) 2) Integration slug (e.g. “netlify”) 3) Hub URL for the integration (e.g. https://hub.continue.dev/integrations/netlify) 4) A list of official workflow templates from the Hub (title + trigger + 1–2 sentence behavior) 5) Optional: extra context users need to understand official workflows (if needed) 6) A list of advanced workflow ideas derived from the integration’s MCP examples/docs (NOT “official”) 7) Any required credentials or permission constraints from the Hub UI (token type, scopes, org/project selection, etc.) 8) Any severity/risk classification details (optional) Page structure (required): 1) Strong lead sentence for the frontmatter description - 1–2 sentences explaining what connecting {Integration} enables in Mission Control, using outcome language. - No marketing fluff, no repetition of UI steps. 2) CTA Card (required) Use a Mintlify `<Card>` as the first component and it MUST link to the Hub integration page. <Card title="Connect {Integration} to enable agents to:" icon="{relevant_icon}" href="{hub_url}" > - 3–5 bullets describing the most important verified capabilities (keep tight and accurate) </Card> 3) Official Workflow Templates (required) - Include a short paragraph stating these are official, maintained by Continue, available in the Hub, and designed to work out of the box. - Use `<CardGroup cols={2}>` and a `<Card>` per official workflow template. - Each workflow card description must: - start with the trigger (“When a PR is merged…”, “When a PR is opened…”, “On a schedule…”, etc.) - describe the primary action and outcome, without implementation details. <CardGroup cols={2}> <Card title="{Workflow Name}" icon="{icon}"> {Trigger + behavior + outcome sentence} </Card> </CardGroup> 3a) Official workflow subheading in this section (optional) - Add a subsection heading for official-workflow-related supplemental conten with an h3 that describes the additional info - This heading must appear immediately after the cards (still within the Official Workflow Templates section). - If any additional context is needed to understand the official workflow(s), present it here. - Anytime additional context is needed in this area, use an `<AccordionGroup>` (not plain paragraphs), with 1–3 accordions max. - If no extra context is needed, include the heading and a single short paragraph (no accordions). Example: ### Official workflow notes <AccordionGroup> <Accordion title="What this workflow changes automatically"> - Bullet points </Accordion> <Accordion title="What this workflow will not do"> - Bullet points </Accordion> </AccordionGroup> 4) Tip (required) - Include a `<Tip>` that tells users where to view/enable/configure workflows in the Hub. - The text “Mission Control → Integrations → {Integration}” MUST be a link to the Hub URL. - Use Markdown link syntax inside the Tip. <Tip> Official workflow templates may expand over time as new patterns are validated. You can view, enable, and configure these workflows in **[Mission Control → Integrations → {Integration}]({hub_url})**. </Tip> 6) Advanced Use Cases (optional) - These are NOT official. They can be framed as examples derived from the integration’s MCP examples/docs. - Must be de-emphasized by placing inside a single `<Accordion>`. ### Advanced Use Cases <Accordion title="Advanced: Custom {Integration} Workflow Ideas"> These examples are not officially maintained by the Continue team, but are inspired by the {Integration} MCP examples and illustrate what’s possible with custom workflows. - 4–8 bullets max, written as verbs/outcomes </Accordion> 7) Access & Permissions (required, AFTER Advanced Use Cases) - Keep short and practical: what credentials are needed, what scope selection exists, and how to revoke/rotate. - Use short bullets with bold labels. - No step-by-step UI walkthrough. ## Access & Permissions 8) Support & Resources (required) - Use `<CardGroup cols={2}>` with 2–4 cards. - Prefer internal docs pages when available; include vendor docs only when truly necessary. - If you include a cookbook link, include it here. Quality rules: - Do not promise capabilities that aren’t official or verified. - Do not list “all possible things Continue can do” unless they are explicitly supported and reliable. - Do not repeat Hub UI text unless it clarifies permissions or required prerequisites. - Keep the page scannable: short paragraphs, strong verbs, minimal jargon. Now generate the full MDX page content using the provided inputs. - Add the integration page to the docs.json file in the integrations group