Docs/CodeCanyon Package

CodeCanyon Package

RevenuePilot CRM ships from a repeatable package folder with buyer-ready ZIP files, HTML documentation, screenshots from the live app, demo setup files, and checksums.

Release folder: final artifacts are generated under packages/revenuepilot-crm-codecanyon-v1.0.0/. Do not upload the repository root directly.

Submission Links

Field	Value before upload	Rule
Public documentation URL	`TO_BE_FILLED_BEFORE_UPLOAD`	Enter the hosted documentation URL in the Envato upload form and marketplace copy.
Live preview URL	`TO_BE_FILLED_BEFORE_UPLOAD`	Enter the hosted demo URL after the staging demo is installed and reviewed.

Final submission gate: do not submit to CodeCanyon until both hosted links are filled in the Envato upload form and the marketplace copy. Do not hardcode fake URLs in the package.

Build Command

.\scripts\build-codecanyon-package.ps1 -Version 1.0.0

Use the full gate before the final marketplace upload:

.\scripts\build-codecanyon-package.ps1 -Version 1.0.0 -RunTests -DocumentationUrl "https://your-demo-domain.com/documentation/" -LivePreviewUrl "https://your-demo-domain.com" -FinalUpload

Final upload mode rejects missing, fake, localhost, placeholder, and /public URLs. If documentation is hosted with the live preview, use the clean base URL for the preview and the /documentation/ URL for public docs.

Run the reviewer text scan whenever marketplace copy or documentation changes:

.\scripts\check-codecanyon-reviewer-readiness.ps1

ZIP Files

File	Audience	Contents
`revenuepilot-crm-v1.0.0-complete.zip`	Shared hosting and cPanel buyers	Application source, `vendor/`, compiled assets, installer, docs, and clean storage skeleton.
`revenuepilot-crm-v1.0.0-source.zip`	Developers and agencies	Application source and tests without `vendor/` or compiled assets.
`revenuepilot-crm-v1.0.0-demo.zip`	Online demo setup	Demo install checklist, demo environment template, screenshots, credentials, and demo flow.

Package Contents

README-FIRST.txt with immediate install and demo instructions.
documentation/ with HTML documentation suitable for offline reading.
documentation/pages/asset-licenses.html with third-party asset and vendor attribution notes.
screenshots/ with root-sourced dark/night and light/day marketplace screenshots plus screenshot-manifest.json.
demo-online/ with staging/demo deployment material.
release-manifest.json and checksums-sha256.txt for audit evidence.

Excluded Files

The package builder blocks local and unsafe files from entering buyer ZIPs: .git, .env, real credentials, node_modules, generated logs, cache, sessions, local storage uploads, private keys, raw database dumps, and previous package builds.

Live Screenshots

The root /screenshots folder is the canonical screenshot source. Recapture these files from the staging demo after final demo setup, then rebuild the package so packages/.../screenshots/ receives matching copies and a hosted manifest.

Screenshot QA: run the Full Product Tour, Portal Client Tour, and Revenue & Billing Tour before capture. Confirm both dark/night and light/day themes, readable KPI cards, no placeholder captions, no broken images, no sidebar overlays, no stale tour overlays, and consistent RevenuePilot CRM branding before rebuilding ZIPs. The final scan requires all 40 PNGs, the screenshot manifest, ZIP files, checksums, no placeholders, no /public URLs, and no forbidden live-provider claims.

CRM dashboard screenshot — `crm-dashboard-light.png` - admin dashboard and revenue cockpit.

Leads index screenshot — `leads-index-light.png` - lead capture and qualification.

Deal board screenshot — `deal-board-light.png` - pipeline board and stage movement.

Portal dashboard screenshot — `portal-dashboard-light.png` - client portal workspace.

Envato Notes

The package is organized around current Envato Code item expectations: grouped files, English HTML documentation, source code, and buyer-friendly installation guidance. Verify the latest Envato rules before upload.

Marketplace wording for v1.0.0 must stay sandbox/readiness-focused for payment, ads, mailbox, and accounting workflows unless separate live-provider tests and credentials are proven. Reverb chat can be described as realtime only when Reverb is configured. Mobile delivery is PWA/responsive only; no native APK/AAB/IPA binaries are included in this release.