Whole pages and screens, grouped by what the person must do — each with the reason for its layout, live, with its phone version.

Whole pages and screens, grouped by what the person must do. Pick the intent, then copy the template that fits.

Convince

You come here when a visitor must decide: a landing, a product, a price, a comparison, a proof.

Krizaka — A visitor gets the promise in one screen, the product alive, the proofs and one call to act.
Pricing and credits — A buyer compares plans and sees what a credit buys before deciding to commit.
A product page — A visitor decides whether a product is for them: the promise first, the proof and the call after.
Orazaka plans and credits — A buyer compares three plans side by side and answers the last objections before choosing.
Orazaka — A visitor understands what a product does, the traps it avoids and the decisions behind it, then acts.

Explain

You come here when a reader must understand: how it works, a documentation hub or article, a changelog, a FAQ, a policy.

Components — A reader looking for the right piece scans a filterable catalogue instead of reading every page.
Krizaka UI releases — A user checks what changed in each release and whether it concerns them.
Button — A builder decides whether a component fits, sees it live and copies it, all on one page.
Orazaka's CLI — A reader follows one article, always knowing where they are, what it covers and what comes next.
FAQ — A reader finds the one answer they came for without reading a page.
krizaka.com/docs — A newcomer picks a collection, starts quickly and sees what is new, from one hub.
Orazaka's journey — A reader grasps a process as a few steps, each with the command that does it.
Privacy policy — A person finds a commitment in plain words, with a summary first and the detail by section.
A documentation hub — A newcomer finds the right documentation from one page of grouped entry points.

You come here when the work itself is the argument: a gallery, a story, a case study, an object and its details.

A video — A viewer sees the object itself first, with its facts and the actions that concern it beside it.
Made on this Mac — A visitor browses real results, each with how it was made.
Case study — A prospect trusts a result they can read: the before, the change, the proof in numbers.
Our story — A reader follows a story in chapters, at their own pace, with a break for the key line.
Feed (Mobile) — A person scans what is new, one card per item, and stops where something matters.
Profile (Mobile) — A person is recognised at a glance: the photo first, then the facts and interests that start a conversation.

You come here when a person must do something once: reach the team, sign in or up, set up, pay.

Onboarding — A new person completes a setup one step at a time, knowing how many remain.
Orochia · sign in — A returning person signs in fast, with the product's promise beside the form.
Talk to the team — A visitor reaches a human by the channel they prefer and learns what happens after they write.
Tip checkout — A person pays in a few taps and sees the exact total before committing.
Sign in (Mobile) — A person signs in with the least typing: the brand, two fields, the main action pinned above the keyboard.
Map (Mobile) — A person chooses a place by where it is, with every marker also a named button.
Find a place nearby — A person picks a place by where it is, with the list as an equal way in.

You come here when a person works every day: a dashboard, a console with a table, settings, an app shell.

Administration console — An administrator works a queue: scans it, sorts it and acts on many rows at once.
Orochia studio — A creator moves between the sections of an app and reads this week's figures at home.
Orazaka · Eric's console — An operator reads the key figures at a glance and acts on what runs, for the period they chose.
App shell (Mobile) — A person moves between the main sections of the app with one thumb, the tab bar always in reach.
Settings (Mobile) — A person changes a preference and sees it apply at once, grouped by what it concerns.
Account settings — A person changes one setting at a time, saves it at once and knows where each lives.

You come here when people talk: an inbox, a chat, comments, a notifications centre.

Chat (Mobile) — A person reads the thread and answers from the composer, which stays in reach.
Notifications (Mobile) — A person catches up on what happened without hunting for it.
Messages — A person reads a thread and replies without leaving the list of conversations.
Notifications centre — A person catches up on what happened and acts on one item without losing the list.

You come here when the way is blocked: an empty list, an error, a missing page, maintenance, a product still being built.

An empty page — A person facing an empty page knows what belongs here and how to start.
Not found — A lost visitor gets back on track with a search and a few ways out, never a dead end.
Under construction — A visitor learns honestly what is coming, how far it is and how to hear about it.
Planned maintenance — A person learns what is down, until when, and what they can still do.
Status — A person checks in one look whether the service works and which part is slow.