Docs/CodeCanyon Listing Kit

CodeCanyon Listing Kit And Canva Prompts

This page explains what to prepare for CodeCanyon upload and how to use Canva to create the final cover, preview images, thumbnail, video thumbnails, and documentation graphics.

The final graphics are not generated inside the app. Use the prompts in marketplace/codecanyon/canva-prompts.md, export in Canva, and place the final files in marketplace/codecanyon/images/.

1) Listing Kit Files

File	Purpose
`canva-prompts.md`	Ready-to-copy Canva prompts for cover, preview, thumbnail, docs, and video assets.
`item-description.html`	HTML version of the listing description for the Envato editor.
`item-description.txt`	Plain-text backup of the listing description.
`tags.txt`	Focused marketplace tags.
`changelog.md`	Marketplace changelog.
`message-to-reviewer.txt`	Reviewer note with suggested review flow.
`listing-checklist.md`	Final upload checklist.
`asset-manifest.md`	Tracks source screenshots and pending Canva exports.
`qa/no-php-notices-report.md`	Production smoke report with `APP_DEBUG=false`.

2) Source Screenshots

Use these real app screenshots as Canva source images. Do not replace them with fake UI.

Dashboard source screenshot — Use as the main cover and dashboard preview source.

AI handoff source screenshot — Use for AI reliability, citations, confidence, and human handoff preview.

3) Canva Export Sizes

Asset	Recommended size	Export
Main cover	`2340x1560`	PNG
Preview images	`1920x1080` preferred for current Envato guidance	PNG
Legacy inline preview	`590x300`	JPG or PNG
Thumbnail	`80x80`	JPG or PNG
Docs header	`1600x900`	PNG
Video thumbnail	`1280x720`	JPG or PNG

Re-check the Envato upload form before final submission. Marketplace image requirements can change.

4) Main Cover Canva Prompt

Create a premium CodeCanyon marketplace cover image, 2340x1560, for a Laravel SaaS product named "OvionDesk AI".

Use a clean modern SaaS style. Show a realistic admin dashboard screenshot as the main visual, with smaller floating screenshots for AI handoff, billing, CRM, inbox, and integrations. Use a white/light background with subtle blue, teal, and dark navy accents. Avoid cartoon illustrations. Make it feel production-grade, enterprise-ready, and high-value.

Main text:
OvionDesk AI

Subtitle:
Laravel SaaS Helpdesk, AI Chatbot, CRM, Billing & Channels

Feature badges:
AI Support
SaaS Billing
CRM
Email Inbox
WhatsApp
Envato Support
Addons

5) Preview Image Prompt Pattern

Use this structure for every preview image. Replace the heading, screenshot, and callouts per feature.

Create a 1920x1080 marketplace preview image for [MODULE NAME].

Use [SCREENSHOT FILE] as the main product screenshot.

Heading:
[SHORT HEADING]

Callouts:
[4 to 6 short callouts]

Style:
Clean SaaS UI, light background, navy text, blue/teal accents, polished screenshot frame, no fake UI, no crowded text.

6) Required Preview Set

Preview	Screenshot	Heading
Dashboard	`dashboard.png`	Dashboard Overview
Billing	`billing.png`	SaaS Billing Built In
AI	`ai-handoff.png`	Reliable AI Support
CRM	`crm.png`	CRM-Lite Pipeline
Inbox	`inbox.png`	Unified Support Inbox
Channels	`channels.png`	Email + Messaging Channels
Envato	`envato.png`	Built For CodeCanyon Support
Addons	`addons.png`	Marketplace Addon Suite
Agent PWA	`agent-pwa.png`	Mobile Agent PWA
Public demo	`public-demo.png`	Buyer-Ready Public Demo

7) Item Description And Tags

Use marketplace/codecanyon/item-description.html for the Envato item description field. Keep the plain-text version as backup. Use tags.txt as the first pass for keywords, then trim if the upload form limit requires it.

Replace https://your-demo-domain.com with the real live preview URL before submitting.

8) Demo Upload Package

Upload artifact

Rebuild before final live preview upload

Root/Public

composer install --no-dev --optimize-autoloader
npm install
npm run build
scripts\build-demo-site-min-inode-zip.ps1

Upload oviondesk-demo-site-root.zip outside public_html and oviondesk-demo-site-public.zip into the demo domain folder. Generated demo ZIPs are rebuild artifacts and should not be treated as source files.

9) Production No-Warnings QA

Run this before upload:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts\production-smoke.ps1

The generated report should say PASS and show no PHP notices/warnings or HTTP 500 responses.