Cville Computer Repair Website

Static website skeleton for Christopher "CT" Hoon's computer repair business in Charlottesville, Virginia.

The current working name is Cville Computer Repair. Other viable directions before launch: CT Computer Repair, CT's Cville Computer Help, or Hoon Computer Repair.

Pages

• index.html - home page with local positioning, service overview, trust promises, and repair request CTA
• about.html - owner/about page for CT's bio, values, and privacy-minded service promise
• services.html - repair service menu for diagnostics, malware cleanup, data help, networking, and setup
• request.html - static repair request form that prepares an email draft until a real form backend is connected
• styles.css - shared responsive styling
• site.js - shared navigation, icon initialization, and request-form email draft behavior
• assets/repair-workbench-hero.png - concept hero image; replace with a real CT/shop photo when available

Run Locally

This is a static site. You can open index.html directly, or serve the folder locally:

python3 -m http.server 4173

Then open http://localhost:4173.

Launch Checklist

• Replace placeholder email hello@cvillecomputerrepair.com.
• Replace placeholder phone (434) 555-0137.
• Add CT's real bio, experience, certifications, hours, service area, and policies.
• Decide whether the final brand is Cville Computer Repair or another CT-centered name.
• Replace the generated workbench image with real local photography if possible.
• Connect the request form to a production intake workflow.
• Add a short privacy policy before collecting real customer requests.

Service Request Intake

Static HTML cannot send reliable email or SMS by itself. The request page currently prepares a mailto: email draft so the skeleton is usable for review without pretending it has a backend.

Recommended MVP:

1. Keep the current HTML request form.
2. Connect it to a hosted form provider such as Formspree or Netlify Forms.
3. Send CT an email notification for each request.
4. Store submissions in the provider inbox or export to Google Sheets/Airtable if CT wants a lightweight work queue.
5. Keep call/text links visible for urgent jobs.

Recommended custom backend later:

1. Add POST /api/repair-request.
2. Validate fields server-side and block spam.
3. Send email through a provider such as Resend.
4. Optionally send SMS alerts through Twilio Programmable Messaging.
5. Store requests in a small database, Airtable, or Google Sheets.
6. Add a confirmation page and optional customer confirmation email.

Request Fields

The form intentionally collects only what CT needs for a first reply:

• Name
• Phone
• Email
• City or ZIP
• Preferred contact method
• Best time to reach the customer
• Customer type
• Device type
• Brand/model
• Issue type
• Urgency
• Problem details
• Consent to be contacted
• Optional SMS consent

Do not collect passwords, PINs, payment details, private files, or full street addresses in the MVP. Ask for those only after CT has confirmed a real appointment and has a safe process.

Technical Debt Notes

• The site repeats the header/footer markup across pages. That is acceptable for this small static skeleton, but a template system would be cleaner if the site grows.
• Lucide icons load from a CDN. For production, consider bundling icons locally or replacing the CDN dependency.
• The request form is not a real submission flow yet. Connect a provider or backend before launch.
• There are no automated tests because the site is static HTML/CSS/JS. Use browser checks before publishing changes.
• Metadata is basic. Add Open Graph images, local business schema, and analytics only after the brand/contact details are final.

Privacy and Compliance Notes

• Use HTTPS for the production site.
• Keep request data in one protected business inbox or system with a strong password and 2FA.
• Add spam protection with a honeypot first; add CAPTCHA only if spam becomes a real problem.
• If CT sends automated SMS, collect clear text-message consent and support opt-out language. Twilio notes that U.S. application-to-person SMS over 10DLC has registration/compliance requirements.