Painting-services website with service information, color exploration, paint-planning tools, project imagery, and an estimate-request interface.
π·οΈ Maintained in qamotech/npp Β· π Public repository
- π‘ Interior, exterior, cabinets, feature walls, and commercial service sections.
- π¨ Color-direction controls and project imagery.
- π Paint quantity, primer, and finish-planning tools.
- π¨ Project-request form, local business information, and alternate HTML entry.
Browse service categories, explore a color direction, use the planning tools with sample room dimensions, and review the request flow before deployment.
git clone https://github.com/qamotech/npp.git
cd nppUse Node.js and npm compatible with the versions in package.json. Install dependencies locally, then launch the declared development command:
npm install
npm run devOpen the address printed by the development server. The manifest is the source of truth for commands:
| Command | Declared operation |
|---|---|
npm run dev |
vite --port=3000 --host=0.0.0.0 |
npm run build |
vite build |
npm run preview |
vite preview |
npm run clean |
rm -rf dist server.js |
npm run lint |
tsc --noEmit |
Install/build scripts can execute code. Inspect project configuration and keep secrets in local configuration excluded from Git. No dependency installation or application build was performed for this documentation update.
- π
CNAME - π
index.html - π
metadata.json - π
new-perspective-painting-llc.html - π
package.json - π
tsconfig.json - π
vite.config.ts - π
publicβ source directory
A form interface does not establish that submissions are delivered. Confirm live contact details, service claims, form delivery, and custom-domain configuration with the business owner.
Keep credentials, private exports, customer records, and personal information out of commits and screenshots. A local browser demo is not evidence of account security, reliable persistence, or connected external services. Preserve exports before changing storage keys or resetting an application.
- π Confirm the entry file and asset paths above exist in your checkout.
βΆοΈ Start the documented runtime and inspect browser or terminal errors.- π§ Exercise the project-specific workflow described above using sample data.
- π± Check narrow and wide layouts when the project has a browser interface.
- πΎ Verify save/export and recovery behavior before trusting important work to it.
- π Record the exact command, browser, operating system, and outcome of your checks.
This guide was prepared from repository files and manifests. It does not claim a fresh build, deployment, security audit, or full functional test of this project.
Keep changes focused and explain the user-visible result. Preserve existing assets and configuration unless a change requires updating them. Include reproduction steps, expected and actual behavior, and relevant screenshots with personal information removed. For UI work, include the viewport and browser; for runtime issues, include the command and error text.
- π Keep this guide aligned with implemented behavior and current entry points.
- π§ͺ Add or maintain checks for the core workflow before expanding features.
- βΏ Review labels, keyboard navigation, contrast, and responsive layout.
- π¦ Document external services, asset rights, and deployment prerequisites.
This documentation update does not grant a new software or asset license. Consult existing license files, source headers, package metadata, and original asset terms; resolve inconsistencies with the owner before redistribution. Third-party names and resources retain their own terms.
The material below is retained verbatim for history and project-specific context. Template instructions and older claims may differ from the source inventory above.
This contains everything you need to run your app locally.
View your app in AI Studio: https://ai.studio/apps/26311fcd-b310-480a-bd5c-e1f083f4a4fd
Prerequisites: Node.js
- Install dependencies:
npm install - Set the
GEMINI_API_KEYin .env.local to your Gemini API key - Run the app:
npm run dev
