Refto
Browse all DESIGN.md examples

Layout Principles

Browse DESIGN.md examples that explain layout principles through spacing logic, grid behavior, hierarchy, and section rhythm.

27 curated examples24 per pagePage 2 of 2

What To Look For

Study how these examples describe white space, grid logic, pacing, and layout hierarchy in a way implementation teams can actually reuse.

What To Compare

Focus on spacing rules, density control, rhythm between sections, alignment logic, and whether the layout principles feel operational instead of decorative.

Design Analysis

Common layout principles signals

--- version: alpha name: Flex Dev Toolkit description: A creative developer toolkit language with giant flexible sans type, central dark nav, lime membership CTAs, mono ticker strips, split-axis layouts, tilted resource... --- version: alpha name: Forest Play...

Recurring System Signals

    Related Keywords

    OverviewColorsTypographyLayout

    Osmo

    Home

    2026-02-22

    --- version: alpha name: Flex Dev Toolkit description: A creative developer toolkit language with giant flexible sans type, central dark nav, lime membership CTAs, mono ticker strips, split-axis layouts, tilted resource...

    Open example

    The Cozy Hollow

    Home

    2026-02-22

    --- version: alpha name: Forest Play Space description: A nature-play design language with layered forest illustration, hand-drawn display type, muted blue-green scenery, cream story cards, rounded FAQ rows, and warm ora...

    Open example

    Codex

    Home

    2026-02-22

    --- version: alpha name: Neon Data Terminal description: A high-contrast data API design language with giant uppercase grotesk headlines, black and pale shells, acid-lime CTAs, pixel bullets, floating protocol orbs, neon...

    Open example
    New
    Osmo
    Osmo - Home
    New
    The Cozy Hollow
    The Cozy Hollow - Home
    New
    Codex
    Codex - Home

    Layout Principles FAQ

    What should I study on this page?

    Study how these examples describe white space, grid logic, pacing, and layout hierarchy in a way implementation teams can actually reuse.

    Why browse this as a dedicated DESIGN.md collection?

    A focused collection makes it easier to compare how teams describe one system concern consistently across many examples instead of mixing unrelated signals on a single page.