page skeleton

Page template

Base structure for a new OmenHall page: from hero to related doors, so every wing feels part of one house.

The template does not suffocate style; it gives it a spine: atmosphere above, clarity in the middle, next step below.

Hero

The first screen should say: where the user is, what they can do here, why it is safe, and where to go next.

  • Eyebrow names the wing.
  • H1 is no longer than one breath.
  • Subtitle explains value without jargon.

Core blocks

After hero, use 3-5 meaning blocks: how it works, who it is for, what is inside, boundaries, example use.

  • Blocks do not repeat hero.
  • Every block is scannable.
  • There is one practical example.

Exit path

No page should end in a dead corridor. Finish with CTA, related doors, or next reading path.

  • Primary CTA exists.
  • Secondary gentle path exists.
  • Related links exist.

checklist

  • Hero, core blocks, safety note, FAQ/empty state, CTA, related doors.
  • Text does not start with brand lore when the user came to solve a task.
  • Cards do not become a wall of identical words.
  • Mobile layout checked: grids do not break reading order.

red flags

  • H1 sounds pretty but does not explain the page.
  • All cards end with the same CTA.
  • No safety note on a reading page.

rewrite like this

Result wording

AvoidThis card definitely means the person will return.

PreferThis card points to the theme of return, but it does not replace conversation or a person's free choice.

Purchase call

AvoidBuy a deep scroll or the sign will remain closed.

PreferA deep scroll fits when you want context, positions, and a gentle next-step plan.

Hero

AvoidSecret gates glow in the night of fates.

PreferChoose a method for your question: quick sign, deep scroll, or daily ritual.

definition of done

User understands where they are and what to do within 10 seconds.
Page contains a next step without pressure.
Related doors help go deeper or step back.

related doors