Page template: Product overview

Copy/paste structure for FluxRelay-style landing pages.

Overview

Tagline (Hero/Subtitle)

One crisp sentence. Explain the “why” in 8–12 words.

Example pattern: Do X with Y — fast, safe, and simple.

Home (Overview)

What is [Product]?

One sentence on what it is. One sentence on the user outcome.

Write for scanning. Prefer short lines over long paragraphs.

What it does

3–6 bullets. Use verbs.

• Action 1 (who it helps + result)

• Action 2 (who it helps + result)

• Action 3 (differentiator)

Where it lives (channels)

Say where users start today. List what’s coming next.

• Today: [Telegram / Web / iOS / Android]

• Coming soon: [iOS / Android / Extension]

Why [Product] exists

2–4 sentences. Name the pain. Name who feels it.

Removes:

• Pain 1

• Pain 2

• Pain 3

Vision & principles

Our vision

One sentence. Outcome-first.

Core principles

• Principle 1

• Principle 2

• Principle 3

• Non-custodial / privacy / safety (if relevant)

Getting started

1

1) First action

Command or UI action

Expected result. One constraint, if any.

2

2) Second action

Command or UI action

Expected result.

3

3) Optional: common next step

Do the next thing most users do

Call out variability across environments (clients, chains, networks).

Core features

Feature: Identity (e.g. @usernames)

What it is. Why it reduces mistakes.

Example:

@alice → 0x....

Feature: Payments (send / request / receive)

What it enables. What the user sees.

Feature: AI / automation (optional)

What it automates. What it never does without confirmation (if applicable).

Feature: Gasless execution (optional)

What the user pays (if anything). How sponsorship or fees work at a high level.

Feature: Multichain (optional)

What is automatic. What the user can specify.

Optional: edge cases / limits

• Limits (amounts, chains, tokens)

• Known behaviors

• Unsupported flows

How it works (high level)

3–7 bullets. Keep it conceptual. Link to deeper pages when they exist.

• Step A → Step B → Step C

• Key components involved

Optional: key concepts

• Concept 1 (one sentence)

• Concept 2 (one sentence)

• Concept 3 (one sentence)

Security & trust

Non-custodial / custody model

State it plainly.

• What users control

• What the system can’t do

Safeguards

4–8 bullets. Prefer concrete controls.

• Audits or reviewed libraries

• Rate limiting

• Isolation or privacy boundaries

• Transparent on-chain history

If transfers are irreversible, say it. Tell users what to double-check.

Roadmap

Short-term

• Item 1

• Item 2

Mid-term

• Item 1

• Item 2

Long-term

• Item 1

• Item 2

Contributing & get involved

We welcome collaboration:

• Developers (what areas)

• Designers / UX

• Community

• Partners

Connect

• Telegram: @[handle]

• Twitter/X: @[handle]

• Email: [address]