27 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
platform-mcp	1707a246f7	pre-agent: Swap the 3-team-members stat	2026-06-17 13:22:21 +05:30
platform-mcp	8ae947b1ae	feat(home): add pricing + timeline band above inline lead form ... Adds a new PricingTimelineBand component that sits directly above the homepage InlineLeadForm with two side-by-side cards answering the two final pre-conversion questions every buyer has: 1. "Projects from $X,XXX" — includes discovery, design, build, QA, and post-launch support. 2. "Typical timeline: 4–8 weeks" — discovery week 1, weekly demos, launch by week 8. A subtle "Custom quote available — tell us about your project" line with a downward chevron visually bridges the band into the form below. Implementation notes: - Anchor id="pricing-timeline" so the mobile sticky CTA bar / nav can deep-link to it. - grid-cols-1 md:grid-cols-2 → stacks vertically on mobile, side-by- side on md+ (>=768px). - Each card has an explicit min-h-[260px] sm:min-h-[280px] so the band reserves its own vertical space at first paint, keeping Lighthouse CLS unchanged. - Uses existing design tokens (primary-* / accent-* / secondary-*, rounded-3xl, container-wrapper, gradient-br) so the band feels native to the page. - Placeholder copy ($X,XXX and 4–8 weeks) is flagged with data-stakeholder-confirm markers + HTML comments so the marketing/ leadership team knows what still needs sign-off. - Reduced-motion-respecting CSS animation on the bridging chevron.	2026-06-17 13:21:58 +05:30
platform-mcp	dc84e3ebe8	pre-agent: Add pricing and timeline band above lead form	2026-06-17 13:15:15 +05:30
platform-mcp	624f8532a5	feat(home): replace "Why Choose Us" benefits grid with ProofNumbers band ... Swaps the soft-adjective benefits section (Rapid Development, Enterprise Security, Built to Scale, 24/7 Support) for a compact horizontal stat band so the first below-the-fold surface leads with hard, scannable numbers instead of generic copy. - New src/components/ProofNumbers.astro renders 4 large gradient numbers with one-line captions: 20+ Projects Delivered, 5★ Client Rating, 11 Districts Deployed, < 2s Avg Page Load. Numbers carry a TODO for stakeholder confirmation; defaults mirror existing hero/stat copy. - Responsive grid: 2×2 on mobile (<md), 4×1 horizontal band on desktop, with subtle vertical dividers between columns on md+. - Matches site typography tokens (text-secondary-* / text-primary-*) with full dark-mode parity (gradients shift to primary-400/300). - Removes now-unused `benefits` data array and inline SVG icons from src/pages/index.astro along with the surrounding section markup.	2026-06-17 13:14:51 +05:30
platform-mcp	5e943584d9	pre-agent: Replace why-choose-us with proof numbers	2026-06-17 13:09:02 +05:30
platform-mcp	e418650757	feat(homepage): add testimonial photos + outcome metric badges ... - Add `image`/`imageAlt`/`initials`/`metric`/`metricLabel` fields to the homepage testimonials data so each card surfaces a concrete client outcome (e.g. "3× faster loan processing", "+42% organic traffic") next to the quote. - Render a 56–64px rounded avatar with lazy-loaded `<img>` (width/height set to prevent CLS) and a brand-tinted metric badge in the card header. Initials sit behind the image as an automatic fallback if the avatar 404s or fails to decode. - Ship 3 neutral SVG initial-avatars under public/images/testimonials/ (ajay-pruthi, dhirendra-singh, dilip-raj) as placeholders until real headshots are licensed — flagged in the data-array comment so future edits know to swap in JPG/WebP at the same path. - Tighten responsive sizing: card padding scales 8→14, quote text scales 20→30, avatar 56→64, and the star+metric row now wraps on narrow viewports so the layout reads cleanly at 360/768/1280.	2026-06-17 13:08:38 +05:30
platform-mcp	3394c246b2	pre-agent: Add testimonial photos and metrics	2026-06-17 13:03:51 +05:30
platform-mcp	8dbbad4277	refactor(home): remove duplicate FAQ section, merge unique Q&As into HomepageFaq ... The homepage rendered two FAQ blocks — an inline "Common Questions" section plus the <HomepageFaq /> component above the final CTA — which produced two FAQPage JSON-LD entries and a redundant accordion. Consolidate on HomepageFaq (self-contained, polished accordion, better a11y) and: - delete the inline FAQ <section>, the `faqs` array, the `faq={faqs}` prop on <SEO>, the orphan .faq-question/.faq-answer/.faq-icon CSS, and the initFAQ() boot script + its call in index.astro - merge the 4 unique inline questions (support, process, team augmentation, security) into HomepageFaq's moneyFaqs; the 2 duplicates (technologies, timeline) were already covered there - refresh HomepageFaq's lead-in copy and comments to reflect it as the single canonical homepage FAQ Result: one FAQ heading + one accordion in the DOM, exactly one FAQPage JSON-LD with 10 Q&A pairs, no broken anchor links.	2026-06-17 13:03:29 +05:30
platform-mcp	5395a529dd	pre-agent: Remove duplicate FAQ section	2026-06-17 12:58:09 +05:30
platform-mcp	462d2058e1	fix(forms): harden honeypot hiding on contact + inline lead forms ... Both honeypots now use off-screen positioning (position:absolute; left:-9999px; width:1px; height:1px; overflow:hidden) instead of relying on a parent's aria-hidden alone, and the input itself carries tabindex="-1", autocomplete="off", and aria-hidden="true". Labels are sr-only and sit as siblings of the input (no nested label/input). Avoid display:none and visibility:hidden so bots that skip those still trip the trap. Verified: rendered honeypot HTML matches spec on both /contact and the homepage inline lead form, and /api/contact still 200s a populated `website` silently (bot path) while accepting empty `website` payloads as real leads.	2026-06-17 12:57:47 +05:30
platform-mcp	16c5f79f2b	pre-agent: Hide honeypot field on contact forms	2026-06-17 12:54:32 +05:30
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	0893078d73	pre-agent: Wire SMTP into contact and project inquiry forms	2026-06-17 12:16:51 +05:30
platform-mcp	8fb25ded08	docs(devops): document SMTP env vars for Hostinger mail integration ... Expand the CI/CD env-var table to list all SMTP_*, MAIL_ADMIN_TO, SMTP_FROM, SMTP_FROM_NAME and STARTTLS/timeout knobs that the contact and "Tell us about your project" forms now rely on. Adds a note that the production secrets live in the Default environment's platform env-var store and that the frontend service must be restarted after any change.	2026-06-17 12:16:17 +05:30
platform-mcp	9057ec8d11	pre-agent: Configure SMTP environment variables for email	2026-06-17 12:14:12 +05:30
platform-mcp	f0e755ef87	agent: Add Money-Focused FAQ Section to Homepage	2026-06-17 11:55:49 +05:30
platform-mcp	3e276375bf	pre-agent: Add Money-Focused FAQ Section to Homepage	2026-06-17 11:50:11 +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
platform-mcp	64be202f75	pre-agent: Add Inline Lead Form to Homepage	2026-06-17 11:40:43 +05:30
platform-mcp	85965e1a00	feat(contact): add global WhatsApp FAB and mobile sticky CTA bar ... - WhatsAppFab: 56px brand-green floating button (wa.me/919561417403), shown on every page; safe-area aware; lifts above the mobile CTA bar on <md. - MobileStickyCtaBar: 3-column sticky bottom bar (Call / WhatsApp / Quote) visible only below the md breakpoint, with safe-area padding, 48px+ touch targets, and dark-mode-aware styling. Bottom spacer keeps the footer clear of the bar on mobile. - Mounted both components globally via BaseLayout. - Added tests/sticky-cta.spec.ts covering 360px and 1280px viewports, link integrity, no-overflow, hidden-at-md, and FAB/bar non-overlap.	2026-06-17 11:40:23 +05:30
platform-mcp	b9ab4608fd	pre-agent: Add WhatsApp FAB and Sticky Mobile CTA Bar	2026-06-17 11:33:31 +05:30
platform-mcp	213aa5c128	agent: Replace Tech Stack Strip With Client Logos	2026-06-17 11:33:10 +05:30
platform-mcp	fd42eeade9	pre-agent: Replace Tech Stack Strip With Client Logos	2026-06-17 11:23:34 +05:30
platform-mcp	d9bd0cb86a	fix(homepage): stop stats counters from getting stuck at "0" ... The stats tiles ("Projects Delivered" etc.) could end up frozen at 0+/0%/0+/0 whenever the IntersectionObserver never fired (tall sections on mobile, threshold too strict, JS error, prefers-reduced-motion). - Server-render the final value as the initial textContent so the numbers are correct on first paint, with JS disabled, and on any hydration failure. - Lower observer threshold to 0.1 and add rootMargin so the animation triggers reliably on tall viewports. - Detect prefers-reduced-motion and render the final value without animating. - Fall back to immediate animation when IntersectionObserver is unavailable or the section is already in view at load. - Reset to 0 only at the moment the animation starts (and snap to the exact target at the end) so a mid-flight failure can never leave the counter visibly stuck. - Boot all homepage scripts after DOMContentLoaded.	2026-06-17 11:23:12 +05:30
platform-mcp	1289aa43c4	pre-agent: Fix Homepage Stats Counter Bug	2026-06-17 11:17:45 +05:30
platform-mcp	14df2d6867	agent: Implement Homepage Conversion Improvements	2026-06-17 11:13:33 +05:30
platform-mcp	347efa6742	feat(home): conversion-rate optimization pass on homepage ... Hero - Tightened H1 to a benefit-led, audience-first value prop ("Custom Software That Powers Enterprises & Governments") - Replaced generic subhead with a ~135-char outcome line that names the audience (startups, enterprises, government bodies) - Swapped primary CTA copy to an action verb ("Get a free consultation") and secondary to "See our work"; added source query params + data-cta hooks so analytics can attribute CTA clicks - Added a micro-trust line under the CTAs (free 30-min call, reply within 1 business day, no commitment) Social proof - New ClientLogos.astro component rendered below the hero. Grayscale strip with hover pop, image+wordmark fallback, TODO documenting the five required SVG assets in public/images/clients/ - Default roster sourced from the live portfolio (PLNR, RENTEC, IIT Patna, MOC Soft Technologies, Govt. of Bihar) - Existing testimonials carousel left intact (3 quotes with name/role) Services preview - Reframed the 4 cards around outcome headlines and added deep links to /services#<slug> for each service detail section - Renamed "Learn More" to "Learn more" and made it a real <a> link with aria-label for screen readers Final CTA band - New conversion-focused headline ("Ready to ship your next production system?") and a one-line offer with explicit response SLA - Added a "what you'll get" reassurance row (discovery call, fixed-price scope, NDA on request) - Primary CTA now "Get my free consultation" with source attribution; secondary "See case studies" preserved - Process-section CTA renamed to "Book a discovery call" and tagged SEO - Updated meta description on BaseLayout invocation to match the new positioning; FAQPage schema and existing structured data untouched	2026-06-17 11:13:03 +05:30