Everything for your home, in one place.

• Open index.html and edit the CONFIG object at the top of the script at the bottom of the file: company name, office phone, office email, and the emergency maintenance number.
• Colors live in the :root CSS variables at the top of the file (--navy, --teal).
• Replace the placeholder 555 phone numbers and contact@sarkadyrentals.com everywhere they appear before publishing.
• Review the privacy notice in the footer and replace it with your final wording (see step 8).

Create a .env file on your server / serverless host (never in this HTML file) from this template — .env.example:

# Who receives form notifications (same or different addresses)
MAINTENANCE_RECIPIENT_EMAIL=you@example.com
APPLICATION_RECIPIENT_EMAIL=you@example.com

# Verified sender on your own domain
FROM_EMAIL=Sarkady Rentals <notifications@yourdomain.com>

# Transactional email provider (Resend, SendGrid, or equivalent)
EMAIL_PROVIDER_API_KEY=replace_with_your_key

• Sign up with a transactional provider (e.g. Resend or SendGrid), verify your sending domain by adding the SPF/DKIM DNS records they give you, and confirm a test send lands in your inbox — not spam.
• The server sends notifications from FROM_EMAIL and sets the tenant/applicant’s email as Reply-To, so hitting Reply reaches them directly.
• Subject lines: Maintenance Request — [Property/Unit] — [Urgency] and Rental Application — [Applicant Name] — [Property/Unit].
• The tenant/applicant also gets a confirmation email containing their reference number. If sending fails, the server must keep the saved submission, flag it for retry, and the confirmation on this page must not claim the email was delivered.

Venmo QR code (no API, no merchant account) — already set up:

• The Payments tab shows a QR code generated for your Venmo handle @Bob-Sarkady. Scanning it opens https://venmo.com/u/Bob-Sarkady, and the handle is printed under the code. The image lives at assets/venmo-qr.png next to this page’s index.html.
• Test it: scan the published code with your phone and confirm it opens the @Bob-Sarkady profile before you tell tenants to use it.
• If your handle ever changes, generate a new QR code for the new venmo.com/u/… link, save it over assets/venmo-qr.png (same filename), update the handle shown in the Payments tab and in CONFIG at the bottom of this file, then republish.

Form email backend (optional, for automatic email delivery):

• Deploy two small serverless endpoints alongside this page (Netlify Functions, Vercel Functions, Cloudflare Workers, or any Node host): POST /api/maintenance and POST /api/applications — re-validate every field server-side, save the submission to a private database, store photos in private object storage with expiring signed links, assign the reference number, then send the two emails from step 2. Add rate limiting and the honeypot field check (the hidden field is already in both forms).

1. Submit both forms with bad data (missing fields, bad email) and confirm the error messages are clear; then submit valid test entries and confirm the notification email, the confirmation email, and the reference numbers all match.
2. Scan the Venmo QR code in the Payments tab with your phone and confirm it opens the correct Venmo profile. Send a small test payment (e.g. $1) with the payment note shown on screen, and confirm you can match it to the right property and purpose in Venmo.
3. Check both forms and the payment review + QR step on a phone.
4. Deploy to your host with HTTPS enforced (all the free hosts above provide it automatically with a custom domain), and re-test the live URLs.
5. Privacy notice: the footer notice is a starting draft — have it reviewed before launch, and update the contact details in it to match step 1.