# ProInvoice — Product Documentation

Welcome to the official documentation for **ProInvoice**, a web-based **Invoice, Billing & Accounting** application built for small businesses, agencies, and finance teams. This manual is written for **first-time buyers**, **non-technical users**, and **hosting environments** ranging from **shared cPanel** to **VPS** and **aaPanel**.

---

## Who this documentation is for

- New CodeCanyon customers installing the product for the first time  
- Shop owners and accountants who will use the admin panel daily  
- IT staff or freelancers setting up hosting, email, and cron jobs  
- Support teams answering buyer questions  

---

## Document map

| Document | What you will find |
|----------|-------------------|
| **[INSTALLATION_GUIDE.md](INSTALLATION_GUIDE.md)** | Download from CodeCanyon, cPanel & VPS/aaPanel installation, installer wizard (all stages), cron, email basics, go-live checklist |
| **[LICENSE_GUIDE.md](LICENSE_GUIDE.md)** | Envato purchase code, external activation website, domain binding, activation keys, common license problems |
| **[USER_MANUAL.md](USER_MANUAL.md)** | Complete walkthrough of every major module: invoices, customers, accounting, reports, reminders, settings, and more |
| **[TROUBLESHOOTING.md](TROUBLESHOOTING.md)** | Step-by-step fixes for 500 errors, database issues, license failures, email, permissions, and assets |
| **[FAQ.md](FAQ.md)** | Short answers to the questions buyers ask most often |
| **[SECURITY.md](SECURITY.md)** | SSL, backups, passwords, file permissions, and ongoing security hygiene |
| **[CHANGELOG.md](CHANGELOG.md)** | Product version history (update this file with each release) |
| **[PRODUCTION_READINESS.md](PRODUCTION_READINESS.md)** | Pre-live checklist, caches, cron/queue, verify script (for authors & DevOps) |

**Start here if you are new:** read [LICENSE_GUIDE.md](LICENSE_GUIDE.md) and [INSTALLATION_GUIDE.md](INSTALLATION_GUIDE.md) in that order, then [USER_MANUAL.md](USER_MANUAL.md).

---

## Quick start (10-step overview)

1. Purchase the product on **CodeCanyon** and download the **installable** package.  
2. Obtain your **activation license key** from the **author’s license website** using your **Envato purchase code**.  
3. Upload and extract the software on your server (**cPanel** or **VPS / aaPanel**).  
4. Point your **domain** to the correct folder (**web root** must be the `public` directory — see Installation Guide).  
5. Create a **MySQL database** and database user with full privileges.  
6. Open your site in a browser and complete the **installation wizard** (4 stages).  
7. Log in to the **admin panel** and **change your password**.  
8. Configure **company settings** and **SMTP** so emails send correctly.  
9. Add a **cron job** so reminders, recurring invoices, and scheduled tasks run on time.  
10. Review the **Before going live** checklist in the Installation Guide.  

---

## Why this installer is beginner-friendly

- **Visual steps:** The installer checks your server before you enter database details.  
- **Clear errors:** Requirement failures usually name the missing PHP extension or folder permission.  
- **Optional demo data:** You can explore the software with sample customers and invoices, or start empty.  
- **No manual SQL required:** Database tables are created for you during installation.  

---

## Recommended hosting environments

| Environment | Suitability | Notes |
|-------------|-------------|--------|
| **cPanel shared hosting** | Excellent | Ensure PHP 8.2+ and MySQL; set cron if your host allows it |
| **cPanel VPS** | Excellent | Full control over PHP version and cron |
| **aaPanel (VPS)** | Excellent | Match PHP version and document root to `public` |
| **Other Linux VPS** | Good | Nginx or Apache; point vhost to `public` |
| **Local XAMPP / Laragon** | Good | For testing; use `php artisan serve` or virtual host to `public` |

**Tip:** Always confirm **PHP version**, **MySQL/MariaDB** availability, and **cron** support with your host before purchase if you are unsure.

---

## Best practices after installation

1. **Change the admin password** immediately.  
2. **Enable HTTPS (SSL)** on your domain.  
3. **Configure SMTP** and send a test email.  
4. **Set up cron** (`schedule:run` every minute).  
5. **Remove or protect** the installer if your build still exposes it (follow author’s post-install notes).  
6. **Take a backup** before your first real data entry.  

---

## How to keep your system secure

See **[SECURITY.md](SECURITY.md)** for a full checklist. In short: strong passwords, SSL, limited admin accounts, regular backups, and keeping your server PHP updated.

---

## Before going live checklist

- [ ] Installation completed without errors  
- [ ] Admin password changed  
- [ ] Company name, logo, and address set under Settings  
- [ ] Default currency and tax settings reviewed  
- [ ] SMTP tested (invoice or reminder test email received)  
- [ ] Cron job active (verify last run / queue if applicable)  
- [ ] SSL certificate installed  
- [ ] Demo data removed **or** you understand it is only for training  
- [ ] Correct **license domain** and activation status  

---

## Using this documentation elsewhere

This folder is designed so you can:

- Paste sections into **CodeCanyon “Item Documentation”**  
- Publish as **HTML** on a docs site (Markdown-compatible)  
- Export to **PDF** using any Markdown-to-PDF tool  
- Copy short paragraphs into an **in-app help center** (see the appendix in **USER_MANUAL.md**)  

---

## Screenshots

Throughout the guides you will see placeholders such as:

`[Insert Screenshot: Installer Stage 1]`

Replace these with your own product screenshots when publishing to CodeCanyon or your help portal.

---

## Support & updates

See **USER_MANUAL.md** (Support section) and **FAQ.md** for how to contact the author, what support covers, and how updates work.

---

**ProInvoice** — Professional invoicing and accounting, documented for real-world hosting.

*This documentation package is provided as part of your CodeCanyon purchase. Keep it with your project files for future staff and auditors.*
