caelum0x 477355d545 docs(resend-migration): fix stale parity rows — path attachments + content_id inline images are live, not "Not yet"
Live-verified by sending a real test email through the production API
(mail-api.scribase.com) with a remote `path` attachment and a
`content_id` inline image: accepted by the OCI relay and sent with no
errors. Both features were already fully implemented (SSRF-guarded
server-side fetch for `path`, `cid` wired through to both the OCI and
SMTP providers) but the migration docs still told evaluators "Not
yet" and "use base64 content" instead — a false parity gap that would
make a developer comparing against Resend wrongly rule this out.
2026-10-29 09:51:24 +03:00
..
2025-06-08 10:41:56 +10:00

Mintlify Starter Kit

Click on Use this template to copy the Mintlify starter kit. The starter kit contains examples including

  • Guide pages
  • Navigation
  • Customizations
  • API Reference pages
  • Use of popular components

Development

Install the Mintlify CLI to preview the documentation changes locally. To install, use the following command

npm i -g mintlify

Run the following command at the root of your documentation (where mint.json is)

mintlify dev

Publishing Changes

Install our GitHub App to auto propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.

Troubleshooting

  • Mintlify dev isn't running - Run mintlify install it'll re-install dependencies.
  • Page loads as a 404 - Make sure you are running in a folder with mint.json