NANDAX VendorDocs Help

Getting Started

NANDAX VendorDocs is designed to help game developers and vendors create professional, marketplace-compliant documentation and asset packages in minutes.

1. Create a Project: Choose Blank project or Sample project from the dashboard starter menu, then click + Start Project.
2. Choose Your Marketplace: Select your target platform (CodeCanyon, Scirra, etc.). The tool automatically adjusts required image dimensions and compliance rules.
3. Fill in the Details: Enter your game title, features, customization options, and support info.

Blank project starts empty for real work. Sample project loads demo text plus embedded placeholder images so new users can understand the full workflow immediately.

One-Click Sample Data

The dashboard sample project includes ready-made demo data and SVG image assets embedded inside the app:

• Hero banner for the generated buyer documentation.
• Vendor cover examples for CodeCanyon, Scirra, itch.io, GameJolt, and CrazyGames.
• A small thumbnail for the welcome popup and sidebar preview.
• Two sample screenshots for the ZIP package and compliance flow.
• Demo Sales & Promotion Kit text, sales links, and checklist items.

To change the default one-click sample for distributed copies, edit the sample fields and embedded sample asset generator in js/main.js, then run npm run build.

Managing Assets

High-quality visuals are key to marketplace success. Our tool handles the heavy lifting for you:

• Hero Banner: This appears at the top of your buyer documentation. Ideal size is around 1200x400.
• Market Covers: Each marketplace has specific cover requirements. Upload a high-res image and the tool will resize it to the exact specifications (e.g., 2340x1560 for CodeCanyon).
• Screenshots: Upload your game screenshots. During export, they are bundled and properly formatted for your selected marketplace.

The Publishing Process

When you're ready, click Publish Package ZIP. The tool checks compliance and generates a structured ZIP containing:

• Buyer_Documentation.html: A stunning, offline-capable guide for your customers.
• Marketplace_Description.txt: Pre-formatted text for the product page.
• README.txt: Essential package information including generated Market Tags.
• Assets/: Resized covers, banners, and screenshots.
• AI_Generation_Prompts.txt: Professional, high-fidelity prompts for Midjourney/DALL-E.

Sales & Promotion Kit

The final generated documentation section can include a YouTube promo video, official sales page links, live demo links, promotion copy, and a buyer action checklist.

• Use Fill Demo Content in that section to understand the expected format.
• Use one link per line in this format: Label: https://example.com.
• YouTube embeds may not play from local files or sandbox previews. In that case the generated docs show a custom Watch on YouTube fallback. Hosted documentation served from a normal web URL will try embedded playback.

Advanced Features

Editor Tabs

Use the tabs at the top of the preview pane to toggle between the Live Documentation Preview, the Plain Text Description, README, Checklist, and AI Prompts.

Saving & Persistence

The dashboard badge shows the current storage mode.

• Local mode: Projects are saved in the current browser using browser storage and IndexedDB. This is simple and private, but browser quota limits can affect very large image-heavy projects.
• Workspace folder mode: Use Tools → Workspace Folder to write project data to a folder on your machine. This is the recommended mode for many documents or larger assets.
• Manual Save: Use Ctrl + S to save instantly.
• Portability: Use the 📤 Export and 📥 Import buttons in the header to move your project data between different computers or browsers via .json files.

Distributing VendorDocs

For a customer-facing app package, include only the runtime files:

• index.html
• help.html
• css/main.css
• js/bundle.js

Keep owner/server files private: js/main.js, activate.php, activity_viewer.php, keys.php, key_gen_tool.html, owner guides, repository docs, backups, and archives.

Before distribution, run npm run dist:customer. It creates a clean dist/customer/ folder with the runtime files. If you change the default sample data, activation URL, About text, or version notes, always rebuild so js/bundle.js matches the source.

Keyboard Shortcuts

Power users can navigate the app using these built-in shortcuts:

• Ctrl + K : Open Command Palette
• Ctrl + N : New Project
• Ctrl + S : Save Project
• Ctrl + E : Publish ZIP
• Ctrl + D : Refresh Preview
• ? : Show Shortcut Overview

Compliance Checker

Before you publish, check the Pre-upload Compliance panel. It monitors your project for missing critical information like Support Email or Asset Credits, ensuring your submission doesn't get rejected by marketplace reviewers.