This document specifies lunar-landing, a public landing page for local service business owners. Its current product commitment is to build a landing page that clearly presents the product and lets an owner choose whether to get started or sign in. The page should make the product understandable and reassuring without asserting capabilities, prices, or claims that have not been established.
The accepted audience is the Local service business owner. The landing page is the current product scope; no additional product workflows are established.
The landing page succeeds when a local service business owner can understand the stated product proposition, view the product preview, and find the available “Get started” and “Sign in” choices. The page must remain readable and usable across the specified viewport widths and with reduced motion enabled.
lunar-landing is a React landing page served as a public entry surface. It presents the product proposition and a focused product-interface preview to local service business owners. The page offers “Get started” and “Sign in” choices; their destinations and downstream workflows are not specified in the current scope.
The provisioned infrastructure consists of a React frontend, a shared FastAPI backend, and a MariaDB database. The landing-page commitment does not establish a need for application APIs, persistent domain data, authentication, or additional services.
The Landing page is publicly accessible and does not require application identity to view. It is the sole accepted page and the owner of the landing-page experience. The page’s “Get started” and “Sign in” actions are choices presented to the visitor; no trial, sign-in, account, or post-click workflow is specified, so this document does not define their destinations or behavior beyond presenting them as actions.
The uploaded screenshot is optional visual context only. It does not authorize copying its section structure, claims, navigation, pricing, or product features. The current page follows the supplied creative direction and uses only the accepted product proposition and preview.
Information and state
Primary and supporting actions
Components and responsibilities
explicit; the audience and page ownership are required_inference.required_inference from the Planning Scope persona contract.The visual direction is Humane technology for local service businesses, with Yves Béhar as its named muse. The design should feel clear, reassuring, warm, and practical. Use the supplied direction’s palette, typography, layout, shape language, and restrained motion.
Color tokens
#123C35#F5F2EA#F8F7F2#C9F778#E8A842#AFC8BCTypography
Shape and layout
Responsive readability
Build the Landing hero as a deep-green field with the large, left-aligned headline and two choices above a wide, warm-cream product preview. The preview is the visual anchor: use lime highlights and small status labels beside its content to make the interface legible without implying unaccepted functionality. Keep the primary action lime and the secondary action quietly outlined. The composition uses only the accepted proposition, preview, and choices; it adds no new behavior or destination.
Interaction Model: Animated
Motion Tempo: restrained
Hero Dimensionality: layered_2d
Responsive readability
Reduced-motion usability
Visual restraint

Give local customers a clear path to share feedback, and see the product before you decide.
Get started and sign in destinations are not configured.
Customer feedback
Review response
Illustrative feedback
★★★★★
A simple example of how customer feedback could appear in a product preview.

Give local customers a clear path to share feedback, and see the product before you decide.
Get started and sign in destinations are not configured.
Customer feedback
Review response
Illustrative feedback
★★★★★
A simple example of how customer feedback could appear in a product preview.
No comments yet. Be the first!