Projects Live

Lúmina W

I designed and implemented the complete Lumina W landing: Astro architecture, Tailwind CSS styling, Formspree-integrated contact form, full technical SEO, and continuous deployment.

By Valentina Ramírez · Updated: June 19, 2026

View live site

Summary

I designed and implemented the complete Lumina W landing: Astro architecture, Tailwind CSS styling, Formspree-integrated contact form, full technical SEO, and continuous deployment.

Stack

AstroTailwind CSSFormspreeSEOA11yGA4Performance

The problem

Every company needs a digital presence that clearly communicates who they are and what they do.

No digital presence

Without a landing, Lumina W had nowhere to send prospects, communicate the proposition, or close a commercial conversation.

Two services hard to communicate together

Custom development and SaaS have different buyers. Mixing them without structure confuses instead of converting.

What I built

01
Astro with static output: section components, optimized build, and continuous deployment to Netlify.
02
Full technical SEO: title, meta-description, og:*, twitter:*, canonical, and schema markup.
03
Accessibility (a11y): heading hierarchy, aria-labels, and WCAG AA contrast.
04
Performance: static output, WebP images, and immutable cache on Netlify.
05
Google Analytics (GA4): session tracking, scroll depth, and user behavior.
06
No own backend contact form using Formspree: name, company, email, and message with automatic confirmation to the user.
07
Responsive design with Tailwind CSS and light/dark mode.
08
Two-track business structure: custom development and SaaS rental (TerraCore), each with its own phase flow.

Architecture decisions

1. Two explicit tracks instead of one service

Context: Lumina W offers custom development and SaaS. Buyers for each track have different needs, timelines, and budgets.
Trade-off: A generic 'we make software' landing does not convert. Separating the tracks adds visual complexity but clarifies the proposition.
Decision: Services section with two clear columns: custom development (4-phase process) and SaaS rental (TerraCore). Each track has its own CTA.

2. TerraCore as proof of capability

Context: A potential client needs to see a real product, not just custom development promises.
Trade-off: Dedicating space to TerraCore on the agency landing may distract. Not doing it leaves the capability argument without evidence.
Decision: Section dedicated to TerraCore with modules, features, and CTA. It works as a proprietary case that proves Lumina W builds what it preaches.

3. Contact form without own backend

Context: An agency landing needs to capture leads from day one without own backend infrastructure.
Trade-off: Building an own contact backend takes time and is oversized for a landing. Formspree solves the use case 100%.
Decision: Formspree for the contact form: no own backend, no maintenance, with automatic confirmation to the user.

Results

Complete Lumina W landing in production with two differentiated service tracks and functional contact form.
TerraCore visible as a proprietary product within the landing, functioning as proof of agency capability.
Active contact form via Formspree without own backend: captures name, company, email, and message with automatic user confirmation.

Learnings

Communicating two distinct services (custom development and SaaS) on a single landing requires clear structure: without separating tracks by buyer, the proposition is diluted.
Formspree eliminates the need for an own endpoint on the landing: for a starting agency, that decision reduced launch time without compromising lead capture.

One click away

Your next idea deserves
code that can carry it.

I design and build complete products: from the backend to the interface your users love. With integrated AI and security by design.

Projects from COP 2,000,000 / USD 500 depending on scope (MVP from 3-6 weeks).

Limited availability, I respond within 24h.

Start my project See services