Thornebrook Landscaping Co. — Landscaping Company Website (Frontend + Backend)

Five pages and a real lead-capture backend — this is a DYNAMIC website: services, before/after highlights, service areas, testimonials and FAQ are static editorial content, while the "Get a Free Quote" form writes to your own database in real time. 1. Home (index.html) — hero, trust indicators, services overview, before/after gallery, service areas, testimonials. 2. About (about.html) — company story, 3 team profiles, guiding values. 3. Services (services.html) — 6 services in detail. 4. FAQ (faq.html) — 7 honest answers on quotes, timelines, warranties and pricing. 5. Contact (contact.html) — the real quote-request form (project type, timeline, contact details). WHOSE DATABASE, WHOSE EMAIL PROVIDER. Yours, not this platform's. Before anything here does something real: 1. Create a Postgres database anywhere you like — Vercel Postgres, Supabase, Neon, or your own server — and run schema.sql against it once. 2. In your Vercel project's Settings -> Environment Variables, set: DATABASE_URL your database connection string LANDSCAPING_QUOTES_ADMIN_KEY any secret string you choose Optional, for automatic email confirmations on new requests: RESEND_API_KEY from your own Resend (resend.com) account QUOTE_REQUEST_FROM_EMAIL an address on a domain verified in that account Without the two optional variables set, requests still save correctly — no confirmation email sends, that's all. MANAGING QUOTE REQUESTS. Once published, this purchase's library page shows a "Manage live data" panel — paste in your LANDSCAPING_QUOTES_ADMIN_KEY and you can see every request as it comes in and mark ones you've handled. WHAT YOU CAN CUSTOMIZE, HONESTLY: - Every page's copy, images, services, before/after photos and layout — through the same AI-guided editor as any other template, no coding involved. - One optional field at a time on the "landscaping_quote_requests" resource (for example, a "property size" or "preferred start date" field), through the "Backend customization" panel in your library once you've purchased — fully guided, no coding. Fields are always optional, never required, so existing requests are never affected. - Building entirely new resources, forms, or logic (a live project-scheduling system, automated crew dispatch, a client portal) isn't something the editor automates. Every purchase includes the full source code — frontend and backend, no lock-in — so you or a developer you hire can extend it freely outside the platform. PREVIEW LIMITATION. The quote-request form calls a real endpoint that only exists once deployed — this platform's own preview has no backend to call, so it shows a friendly "try it once deployed" message here. That's expected, not a bug. WHAT THIS ISN'T. This template captures and organizes leads — it does not run a live project-scheduling system, automated crew dispatch, or an actual landscaping engagement. Every request is a lead your team follows up on by phone or email. Before/after photos, stats and testimonials shown are illustrative sample content, not verified project records. Replace the sample company name, before/after photos, address, phone, hours and team bios with your business's real, verified details before publishing. Thornebrook Landscaping Co. is a fictional placeholder name — replace it before use.