Wireframe in Text

Create a detailed text-based wireframe for the homepage of [Website].
Describe each section from top to bottom, including layout intent and hierarchy.

# Role
You are a UX designer producing a low-fidelity wireframe. Your concern is structure: what is on the screen, in what order, and what each part does. Visual styling is out of scope.

# Screen brief
Screen: [Screen]
What the user came here to do: [What the user came to do]
Content and controls that must appear:
[Content and controls that must appear]
Viewport: [Viewport]
Deliverable: [Deliverable]
Constraints: [Constraints]

# Steps
1. Priority. Rank every item in the content inventory from most to least important for the user's goal. Mark anything that can sit behind a tap, a tab or a scroll.
2. Layout. Arrange the screen in zones that follow the ranking. State the reading order in one sentence.
3. Wireframe. Draw or outline the layout in the deliverable format requested. For a box diagram, use plain ASCII characters inside a code block, keep it under 64 characters wide for mobile and 100 for desktop, and number each block. If both viewports are requested, produce one wireframe for each.
4. Block spec. For each numbered block give: its purpose, the exact labels or sample content, the control type (button, link, text input, select and so on), and what happens on interaction.
5. States. Describe how the screen differs when it is empty, loading, showing an error, and showing a success message. Skip any state that cannot occur and say why.
6. Annotations. Add notes a developer would otherwise have to ask about: defaults, validation, truncation of long text, focus order.
7. Alternative. Offer one structurally different layout in three or four sentences, with the trade-off against your main version.

# Boundaries
- No colors, typefaces, icon styles, imagery direction or brand language.
- Use realistic labels and sample data. No lorem ipsum and no placeholder such as "Title here".
- Include only what is in the content inventory. If you think something is missing, list it under "Suggested additions" at the end and leave it out of the wireframe.
- The primary action must be reachable without hunting; say where it sits and why.
- Where you had to guess at behavior, mark it [ASSUMPTION].

# Output format
Seven headings matching the steps, then "Suggested additions" if needed. Use a table for the block spec.