lumee: Women's community landing

lumee is a women's community built around shared experiences, events, and ongoing conversation. The community was growing through word of mouth and Instagram, but it had no home on the web. When someone heard about lumee and wanted to learn more, there was nowhere to send them. No landing page, no sign-up form, no way to capture interest and turn it into membership. The community was real; its digital presence was not.

The problem

The team needed a landing page that did three things: introduce lumee to someone who had never heard of it, make it feel safe and welcoming (the community is for women, and safety is a design requirement, not an afterthought), and collect sign-ups. The sign-ups had to go somewhere the team could actually manage — not into a black-hole email inbox.

The constraints were practical. The team had no backend infrastructure and no budget for a CMS. The page had to be deployable for free, maintainable by a non-developer, and live within a week.

The approach

We built the landing page as a static site: HTML5, CSS3, and vanilla JavaScript. No framework, no build step, no runtime dependencies. The page is a set of static files that can be deployed anywhere and edited in any text editor.

The design and engineering choices:

• AOS (Animate On Scroll) for motion. Lightweight, declarative, and no JavaScript framework required. Sections fade and slide in as the user scrolls, which gives the page a sense of flow without the weight of a full animation library.
• Google Apps Script for the form backend. The sign-up form posts to a Google Apps Script web app, which writes each submission into a Google Sheet. No server, no database, no API keys to manage. The team checks the sheet directly. This is the right tool for a community landing page with modest traffic — it is free, it is familiar to non-technical users, and it keeps the data in a place the team already works.
• Vercel for hosting. The static files deploy to Vercel from a Git repository. Push to main, the site updates. No build configuration, no server maintenance.
• Warm design language. The visual identity uses soft, warm tones — rounded shapes, generous whitespace, a palette that reads as inviting rather than corporate. The design had to feel like a community, not a product.

What was built

A single-page landing site deployed at lumee.vercel.app. The page introduces the community, shows what members get (events, discussions, resources), and collects sign-ups through a form backed by Google Sheets.

The form handling is secure by construction: the Google Apps Script endpoint accepts only POST requests from the landing page's origin, validates the input, and appends a row to the sheet. There is no database to compromise and no PII stored beyond what the sheet holds. The team manages responses directly from the spreadsheet — sorting, filtering, and reaching out to new sign-ups without leaving Google Sheets.

The page is responsive and mobile-friendly. Most of lumee's audience arrives from Instagram on their phones, so the mobile experience is the primary experience, not a responsive afterthought. AOS animations are tuned to be subtle on mobile — motion that feels natural on a fast scroll, not motion that fights the user.

Results

• Fast, mobile-friendly site. The static page loads in under a second on a mobile connection. No framework runtime, no hydration, no render-blocking scripts. The performance is a direct result of the technology choice — static HTML is as fast as the web gets.
• Secure form handling. Sign-ups flow into a Google Sheet through a validated, origin-restricted endpoint. No data leaks, no exposed API keys, no server to patch. The team has full control over the data without managing infrastructure.
• Community growth. The landing page gave lumee a permanent, shareable home. Word-of-mouth referrals now land on a page that explains the community and captures interest immediately, instead of losing people to a dead end.

The takeaway

Not every project needs a framework. lumee's landing page works because it is the simplest thing that could meet the requirements: a fast, warm, safe page that collects sign-ups into a tool the team already uses. The decision to use Google Apps Script instead of building a backend was not laziness — it was the correct engineering choice for a community landing page with modest traffic and a non-technical team. Static HTML and AOS kept the page fast and maintainable. The result is a site that does its job, costs nothing to run, and can be updated by anyone who can edit a spreadsheet.