# Spec

## Capability
- Name: MarkupFlow launch marketing site

## Behavior
- the homepage must explain the three core product capabilities: HTML to annotated design, Figma to annotated design, and annotated design as MCP data service
- the homepage must establish that the product is for desktop-software teams
- the homepage must route users to a deeper workflow page
- the product detail page must explain the import, annotation, and publish pipeline
- the product detail page must describe the desktop workspace and its major modules
- both pages must preserve a consistent product voice and visual system

## States
- Success: both pages render the intended content blocks and cross-link correctly
- Error: not applicable for this static forward test
- Restricted: not applicable for this static forward test

## Inputs
- product description
- capability list
- Pencil screen structure and copy

## Outputs
- static homepage
- static product detail page
- implementation-to-Pencil traceability

## Acceptance
- the homepage includes hero, capabilities, MCP service, and CTA sections
- the product detail page includes desktop workspace, pipeline, modules, and CTA sections
- each page maps to one Pencil screen with a stable identifier
- implementation text and structure remain aligned with the requested product narrative

## Edge Cases
- if the active Pencil source changes names or screen ids, `pencil-bindings.md` must be updated before implementation continues
- if the live `.pen` file becomes unavailable, the current HTML outputs remain the fallback implementation baseline