Skip to content

docs(quickstart): rewrite as a self-contained Diátaxis tutorial - #659

Open
dionlow wants to merge 9 commits into
mainfrom
quickstart-diataxis-tutorial
Open

docs(quickstart): rewrite as a self-contained Diátaxis tutorial#659
dionlow wants to merge 9 commits into
mainfrom
quickstart-diataxis-tutorial

Conversation

@dionlow

@dionlow dionlow commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Rewrites src/quickstart.mdx from a tutorial↔how-to↔reference hybrid into a proper Diátaxis tutorial — a first-time builder can now complete the MailMonkey ⇄ Salesforce integration start-to-finish on the page. The full sample it targets: https://github.com/amp-labs/samples/blob/main/quickstart/amp.yaml

What changed

  • Tutorial framing added: "What you'll build", "Prerequisites" (now includes installing the amp CLI, linked to /cli/overview), and "What you'll have at the end".
  • Delegated steps made self-sufficient: the minimum steps to create a Salesforce provider app (enable Dev Hub → External Client App → copy Consumer Key/Secret → paste into Dashboard) and a webhook destination are now inlined with screenshots, keeping the deep guides as "learn more" links.
  • Success checkpoints after each step, plus a "What's next" section.
  • Trimmed the reference-heavy amp.yaml to a minimal teaching manifest; the full option set is deferred to /manifest-reference and the GitHub sample.

Correctness fixes

  • Integration-name mismatch: the React snippet passed integration="readContactsAndLeads" while the YAML defines name: mailmonkey-salesforce. Now both use mailmonkey-salesforce, so the sample actually works.
  • Malformed link: [Destinations](destinations) (bare relative, no leading slash) → [Destinations overview](/destinations/overview).

Verification

  • Integration name is identical in the YAML block and the React snippet.
  • All internal doc links resolve to real files and use leading slashes.
  • All referenced /images/... paths exist under src/images/.
  • Formatting matches the sibling guides (plain Markdown, <img> for screenshots, doubled code-fence labels).

🤖 Generated with Claude Code

Turn the Quickstart into a proper learning-oriented tutorial a first-time
builder can complete without leaving the page, following the MailMonkey ⇄
Salesforce scenario.

- Add tutorial framing: "What you'll build", "Prerequisites" (now including
  the amp CLI install, linked to /cli/overview), and "What you'll have at the end".
- Inline the minimum steps for creating a Salesforce provider app and a webhook
  destination, keeping the deep guides as "learn more" links.
- Add per-step success checkpoints and a "What's next" section.
- Trim the reference-heavy amp.yaml to a minimal manifest; defer full options
  to /manifest-reference.

Fixes:
- Integration name mismatch: React snippet now uses integration="mailmonkey-salesforce"
  to match the amp.yaml name and the published sample.
- Malformed link: [Destinations](destinations) -> [Destinations overview](/destinations/overview).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Ampersand 🟢 Ready View Preview Jul 22, 2026, 7:36 PM

Replace em-dashes with commas, colons, and periods so the phrasing matches
the sibling provider/destination guides.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dionlow
dionlow force-pushed the quickstart-diataxis-tutorial branch from b066e8d to af4b9fd Compare July 22, 2026 19:40
dionlow and others added 2 commits July 22, 2026 12:44
Use a current dashboard screenshot of the API keys page and point the reader
to the "API keys" section instead of project settings. Added as a new image
so the shared create-api-key.png used by api/key-auth.mdx is left untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a small <Where> pill component and tag each step with where the action
happens (Ampersand Dashboard, Salesforce, Ampersand CLI, or MailMonkey), plus
a legend up front, so readers can track which tool they're in.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dionlow and others added 2 commits July 22, 2026 12:59
Switch the <Where> pills from solid saturated fills to soft tinted backgrounds
with desaturated text and a faint border, so they read as subtle labels.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Use a current dashboard screenshot of the OAuth Provider Apps page. Added as a
new image so the shared dd47b7a-Ampersand.png used by ~45 provider guides is
left untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment thread src/quickstart.mdx
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant