9 Commits

Include renames

Author	SHA1	Message	Date
platform-mcp	e4b962bb1b	feat(api/contact): wire env-driven SMTP for contact + project inquiry forms ... Both the contact form (/contact) and the homepage "Tell us about your project" inline lead form post to /api/contact. Updated that single handler to build the nodemailer transport from a clean set of SMTP_* env vars per spec: SMTP_HOST / SMTP_PORT / SMTP_USER / SMTP_PASS SMTP_FROM + SMTP_FROM_NAME -> "From: Ajay Ghanwat <ghanwat.ajay@workroot.in>" MAIL_ADMIN_TO -> admin notification recipient (falls back to SMTP_FROM, then legacy CONTACT_EMAIL_TO / CONTACT_EMAIL / SMTP_USER) SMTP_REQUIRE_TLS -> force STARTTLS upgrade on port 587 SMTP_CONNECTION_TIMEOUT_MS -> defaults to 10000 SMTP_GREETING_TIMEOUT_MS -> defaults to 10000 SMTP_SOCKET_TIMEOUT_MS -> defaults to 10000 Behaviour preserved: - Existing user-facing auto-reply (the block previously at L270) kept. Subject + body now adapt for project-inquiry sources (homepage-inline, homepage-hero, homepage-final-cta, mobile-sticky) so the admin inbox can triage [Project Inquiry] vs [Contact Form] at a glance. - Graceful degradation per FORM_INTEGRATION.md: missing env vars or a failed nodemailer import logs a structured warning and returns 200 — the site never 500s on email config. - Rate limiting, honeypot, CORS, validation, and fire-and-forget background dispatch are untouched. Observability: - Structured console logs at: transport created, admin accepted (with messageId), user auto-reply accepted (with messageId), and send-failure (with smtp code/command/response). SMTP_PASS is never logged. Misc: - .env.example updated to document the new variables and the legacy aliases that are still honored.	2026-06-17 12:25:08 +05:30
platform-mcp	a4505635e1	feat: add inline lead form to homepage ... Mounts a 3-field lead-capture form (name, email-or-phone, project type) between the FAQ/tech-stack block and the final CTA band so visitors who are ready to start a project can submit without leaving the homepage. Cuts the friction step of routing every CTA through /contact. - New src/components/InlineLeadForm.astro: * Heading, micro-trust subhead, honeypot, client-side validation * Smart contact-field routing: detects email vs phone and synthesises a placeholder email for phone-only leads so the existing /api/contact validator accepts them (the real phone is preserved and surfaced in the admin notification) * In-place success state with phone + WhatsApp fallbacks; no navigation * 48px touch targets, dark-mode safe, autocomplete + inputmode attrs - src/pages/api/contact.ts: accept and surface `source` / `projectType` metadata (allowlisted source values, free-text projectType capped at 80 chars), add `erp-solutions` and `government-systems` subject codes, and include the source/project info in both the admin email and logs. - src/pages/index.astro: import + mount InlineLeadForm above the final CTA section. - tests/inline-lead-form.spec.ts: 8 specs covering UI render, mobile attributes, blank-field validation, email-submit + phone-submit payload routing, and server-side acceptance of the new payload shape, new subjects, and unknown-source fallback.	2026-06-17 11:49:47 +05:30
Ajay GhanwatandClaude Opus 4.6	683ff54cdb	feat: add user confirmation email and admin BCC for contact form submissions ... Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-13 12:59:07 +05:30
Ajay GhanwatandClaude Opus 4.6	40ed89793b	feat: add SMTP connection verification and detailed delivery logging ... Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-13 12:58:02 +05:30
Ajay GhanwatandClaude Opus 4.6	d002516bc8	feat: implement fire-and-forget background email sending for instant API response ... Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-13 12:52:33 +05:30
Ajay Ghanwat	8f6e530dc4	fix: correct SMTP transporter config with env vars and STARTTLS settings	2026-04-13 12:51:29 +05:30
Ajay Ghanwat	c7bc4c724f	fix: make contact form response instant by sending email in background ... The POST handler previously awaited sendContactEmail() which blocked the HTTP response until SMTP delivery completed. Now the email is fired off as a background promise with error logging/Sentry capture in .catch(), so users get an immediate 200 response (~130ms vs seconds).	2026-04-13 12:50:20 +05:30
Clintchiz	0614ae6f85	Latest Updated Pages	2026-03-22 14:37:17 +05:30
Clintchiz	d402256547	First Init	2026-03-21 16:46:46 +05:30