Blueprint

Composition starter

Start from a clear business message, then choose the right composition.

Business message

Composition

Live primitives

This page shows the primary chains we prefer for new work: centered Content, zigzag Content+image, Timeline, features, sticky evidence, and a form column.

See How It Works

Discuss Your Business

Governing direction

Business reality → relationship → architecture → implementation.

Do not lead with technology, frameworks, AI, no-code, templates, an editor, feature inventory, or internal philosophy.

Primary audience: founder-led or executive-led, software-dependent businesses. Understandable to a business leader; serious enough for technical validators.

Starter blueprint

Page composition starter

Working template for new pages. Copy the full [seo, data, UI] set, replace data copy and placeholders, and drop sections you do not need. Not public marketing copy.

Content → image

Lead with the message; support with a figure on the right.

First split in a zigzag stack. Prefer imageSide right when the business message must lead.

Example milestones

Day 01

Frame the business problem

Start from the outcome the business needs — not from a feature list.

Day 30

Ship and refine

Replace placeholders, verify live primitives, and iterate with the steward.

Day 15

Choose the composition

Pick Content, Timeline, or Hero chains that match the section job.

Day 01

Frame the business problem

Start from the outcome the business needs — not from a feature list.

Day 15

Choose the composition

Pick Content, Timeline, or Hero chains that match the section job.

Day 30

Ship and refine

Replace placeholders, verify live primitives, and iterate with the steward.

Replace these steps with the page’s real sequence.

Content → image

Counterweight: figure on the left on the next split.

Alternate imageSide across stacked splits so the page does not tilt to one column.

Content → image sticky

Keep evidence in view beside longer copy.

Use sticky when the figure should remain visible while the reader scrolls the message.

Features grid

Four supporting points

FeaturesCentered2x2Grid — keep feature objects complete under UI (or full objects in data when merge depth allows).

Message first: Begin with business reality, not implementation.
Right composition: Match Content / Hero / Timeline to the section job.
Live primitives: Author against shipped primitives; propose code separately.
Replaceable media: Keep src/alt in data with PLACEHOLDER until steward picks art.

Content → centered

Short centered statement between heavier sections.

Use for a single idea that should not compete with a figure.

Platform Accumulated capability, continuity, and a governable business layer for authorized business users.
Engineering partnership Shared-foundation development, new reusable capabilities, architecture, security, integration, testing, operation, migration, technical evolution, and responsible judgment.
Not this Not a self-service developer tool, generic app builder, traditional agency, staff augmentation, shared multi-tenant SaaS across clients, or a replacement for all engineering.

Next step

Replace this call to action with the page goal.

Grid with copy column plus ContactForm — two real children, not a lonely full-width cell.

Discuss a Business Capability

See a Demonstration

Contact

Request a conversation

Form fields stay complete under the ContactForm node in UI.