Description and Screenshots
The description and screenshots section is the publisher's primary sales pitch — a full Markdown document that explains what the package does, why users need it, and how it works, supported by visual evidence.
Description Sections
Package descriptions are written in Markdown and rendered by the MarketHub UI. Publishers can use the full Markdown feature set including headings, lists, code blocks, tables, and inline images.
| Description Section | Expected Content | Required? |
|---|---|---|
| Short description | One-liner in the header (max 140 chars) — "Automate employee expense approvals end-to-end" | Yes |
| Long description | Full Markdown — what it does, use cases, prerequisites, configuration notes | Yes |
| Features list | Bulleted list of key features — displayed as a quick-scan card on the detail page | Recommended |
| Requirements | What the user needs before installing — system requirements, integration prerequisites | Recommended |
| Configuration guide | Step-by-step setup instructions after install | Required for Certified |
Screenshot Gallery
Publishers can upload up to 8 screenshots per package. Screenshots are displayed in a horizontally scrollable gallery below the description. The first screenshot serves as the package card thumbnail on search results and category pages.
| Requirement | Value |
|---|---|
| Maximum screenshots | 8 per package |
| Recommended resolution | 1280 × 720px minimum (16:9 aspect ratio) |
| Accepted formats | PNG, JPG, WebP |
| Maximum file size per screenshot | 2 MB |
| First screenshot use | Displayed as card thumbnail in search results |
Demo Video
Publishers can optionally provide a demo video link (YouTube or Vimeo URL). The video is embedded as the first item in the media gallery, before screenshots. A well-produced 2–3 minute demo video significantly increases install conversion rates for complex packages.
- Lead with the business outcome, not the technical implementation: "Reduce expense approval cycle time by 70%" not "Uses parallel gateway nodes"
- Include a features list in the first screen — users scan before they read
- Show real screenshots of the workflow in action, not placeholder images
- Document every configuration option — unanswered questions become support tickets
- Keep the description updated when new versions add features
Dependency Section
If the package declares dependencies on other marketplace packages, a dependency list is displayed at the bottom of the description section. Each dependency shows the required package name, minimum version, and a link to that package's detail page — so users can evaluate the full dependency chain before installing.