This page is for people editing this docs repo (Mintlify). For ImageMagick itself, use Getting started.Documentation Index
Fetch the complete documentation index at: https://hackmamba-3f164318.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites:
- Node.js 20.17 or newer (LTS recommended; required by current Mintlify CLI)
- A clone of this repository with
docs.jsonat the project root
Custom ports
By default, Mintlify tries port 3000. Set an explicit port with--port:
Mintlify versions
Each CLI release pins a Mintlify framework version. If your local preview does not match production, update the CLI:Validating links
The CLI can assist with validating links in your documentation. To identify any broken links, use the following command:Documentation Index / llms.txt callout (Mintlify)
If the live site shows a blockquote such as “Documentation Index” or “Fetch the complete documentation index at …/llms.txt” on every page, that UI is produced by Mintlify’s hosted shell, not by MDX in this repository. Toggle or report that behavior in the Mintlify dashboard for your deployment (AI / ingestion or support) if you want it hidden; there is often no repo-local switch for that banner.
This project still exposes the machine-readable index at /llms.txt (and /.well-known/llms.txt) and links it from the site footer under Tools. Root-level style.css hides the Mintlify “Documentation Index” blockquote everywhere via blockquote:has(a[href*="llms.txt"]) so the promo does not compete with article content; MDX blockquotes without an llms.txt link are unchanged. The heading ## Snippet verification (CI) {#snippet-verification-ci} in this file is the stable anchor for /development#snippet-verification-ci.
Site-wide blurbs for SEO and generated llms.txt use the optional description field in docs.json; keep it aligned with the homepage when you change positioning.
Snippet verification (CI)
ImageMagick examples in MDX are checked by a small shell harness so obvious regressions are caught in CI.- Either ImageMagick 7 on your
PATH(magick --version), or a working Docker daemon (the script runsdpokidov/imagemagick:latest).
**/*.mdx, docs.json, or scripts/**. For a full platform matrix (Linux, macOS, Windows) and sign-off, use the checklist in VERIFICATION.md in this repo (maintainer reference, not part of the Mintlify navigation).
Deployment
Connect the GitHub repo in the Mintlify dashboard and install the GitHub app so pushes to the default branch deploy the site. In GitHub Actions or your host, a successful deploy shows all checks passing on the pull request or workflow run. If production does not match GitHub: In Mintlify, confirm the project is wired tohttps://github.com/Fimber/docs (or your fork) and the production branch is main. Compare the footer commit or your deploy log to the latest commit on main. Trigger a manual redeploy from the Mintlify dashboard if the integration missed a push, and hard-refresh the browser (or try an incognito window) to bypass a stale CDN cache.
Code formatting
We suggest using extensions on your IDE to recognize and format MDX. If you’re a VSCode user, consider the MDX VSCode extension for syntax highlighting, and Prettier for code formatting.Troubleshooting
Error: Could not load the "sharp" module using the darwin-arm64 runtime
Error: Could not load the "sharp" module using the darwin-arm64 runtime
This may be due to an outdated Node version or a mismatched global install. Try the following:
- Remove the CLI:
npm remove -g mint - Upgrade to Node 20.17 or newer (see
node -v). - Reinstall:
npm i -g mint
Issue: Encountering an unknown error
Issue: Encountering an unknown error
Solution: Go to the root of your device and delete the
~/.mintlify folder. Then run mint dev again.