pixel-perfect / PIXEL_PERFECT_FREE_CHAPTER.html
thedollartoolkit's picture
Publish Pixel Perfect open tooling (Guard Lite at /guard/)
5d45135 verified
Raw History Blame Contribute Delete
10.7 kB
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>The Design Bible: Free Sample Chapters | Pixel Perfect</title>
<meta name="description" content="Read the opening two chapters of The Design Bible: why consistent interfaces depend on decided rules and how to write a practical one-page brand brief.">
<meta name="robots" content="index,follow,max-image-preview:large">
<link rel="canonical" href="https://pixel-perfect-system.netlify.app/PIXEL_PERFECT_FREE_CHAPTER.html">
<link rel="alternate" type="application/rss+xml" title="Pixel Perfect Guides" href="https://pixel-perfect-system.netlify.app/feed.xml">
<meta property="og:type" content="book">
<meta property="og:site_name" content="Pixel Perfect">
<meta property="og:url" content="https://pixel-perfect-system.netlify.app/PIXEL_PERFECT_FREE_CHAPTER.html">
<meta property="og:title" content="The Design Bible: free sample chapters">
<meta property="og:description" content="Why consistent interfaces depend on decided rules, followed by a practical one-page brand exercise.">
<meta property="og:image" content="https://pixel-perfect-system.netlify.app/og-cover.jpg">
<meta name="twitter:card" content="summary_large_image">
<link rel="stylesheet" href="assets/site.css">
<link rel="stylesheet" href="assets/guide.css">
<script src="assets/guide.js" defer></script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Book",
"name": "The Design Bible: Free Sample Chapters",
"author": {"@type": "Person", "name": "Ogia"},
"publisher": {"@type": "Organization", "name": "Pixel Perfect"},
"isAccessibleForFree": true,
"inLanguage": "en",
"url": "https://pixel-perfect-system.netlify.app/PIXEL_PERFECT_FREE_CHAPTER.html",
"description": "The opening two chapters of The Design Bible, covering design-system decisions and a one-page brand brief."
}
</script>
</head>
<body>
<a class="skip" href="#main">Skip to content</a>
<header class="top">
<div class="nav">
<a class="brand" href="index.html">Pixel <em>Perfect</em></a>
<nav class="links" aria-label="Primary navigation">
<a href="index.html#products">Products</a>
<a href="index.html#guides">Guides</a>
<a href="Pixel%20Perfect%20Companion%20-%20FINAL.html">Free Companion</a>
<a class="btn primary small" href="https://edormon.gumroad.com/l/vlwod?utm_source=pixel-perfect-site&amp;utm_medium=organic&amp;utm_campaign=free-chapter-v2" rel="noopener">Buy the book · $20</a>
</nav>
</div>
</header>
<main id="main">
<section class="hero">
<div class="hero-in">
<div class="crumb"><a href="index.html">Pixel Perfect</a> / The Design Bible sample</div>
<span class="eyebrow">Chapters 00 and 01 · free sample</span>
<h1>A great interface is not decorated. It is <em>decided.</em></h1>
<p class="lead">The opening chapters explain the premise, then help you write a one-page brand brief before choosing colours, type or layout.</p>
<div class="hero-actions">
<a class="btn primary" href="#chapter-00">Start reading</a>
<a class="btn secondary" href="https://edormon.gumroad.com/l/aecmk?utm_source=pixel-perfect-site&amp;utm_medium=organic&amp;utm_campaign=free-chapter-v2" rel="noopener">Book and Companion · $24.99</a>
</div>
</div>
</section>
<div class="layout">
<article class="article">
<p class="quick"><b>What this sample contains</b>The complete book has fifteen chapters. This page contains the opening premise and the first practical exercise. It does not represent the full paid book.</p>
<h2 id="chapter-00">00 · Why capable developers still ship inconsistent interfaces</h2>
<p>You can write clean code, understand APIs and deploy a reliable application. Yet the finished interface may still feel less considered than the software underneath it.</p>
<p>The gap is rarely one missing effect. It appears when dozens of small visual decisions have no shared rule: one blue becomes three, spacing changes by section, headings lose hierarchy and components acquire different shapes.</p>
<p>Strong product teams do not solve every screen from taste alone. They restrict the decision space. Colours have roles. Typography has levels. Spacing follows a scale. Components have known states. Exceptions are visible rather than accidental.</p>
<div class="callout"><h3>The central rule</h3><p>Do not ask an agent to invent the visual system while it is also writing the interface. Decide the system first, then make the implementation answer to it.</p></div>
<h3>What the complete method teaches</h3>
<div class="ledger">
<div class="ledger-row"><span class="index">01</span><h3>Direction</h3><p>Translate the product and audience into a visual position with explicit boundaries.</p></div>
<div class="ledger-row"><span class="index">02</span><h3>System</h3><p>Define colour roles, typography, spacing, layout, components and interaction states.</p></div>
<div class="ledger-row"><span class="index">03</span><h3>Instruction</h3><p>Put those decisions into files and prompts that a coding agent can reuse.</p></div>
<div class="ledger-row"><span class="index">04</span><h3>Verification</h3><p>Inspect the rendered result rather than accepting the final message from the agent.</p></div>
</div>
<h2 id="chapter-01">01 · Write the brand brief before choosing the interface</h2>
<p>A useful brand brief is short enough to remain visible while you work. Start with four decisions. Avoid abstract language that could describe any software company.</p>
<div class="grid2">
<div class="card"><div class="num">QUESTION 01</div><h3>What should the product feel like?</h3><p>Choose three precise qualities. Explain each one through a visible consequence. “Calm” may mean quiet contrast and restrained motion. “Operational” may mean dense, aligned information.</p></div>
<div class="card"><div class="num">QUESTION 02</div><h3>Who is making the decision?</h3><p>Name the user, the task and the moment. “A freelance developer presenting a client build” is more useful than “developers.”</p></div>
<div class="card"><div class="num">QUESTION 03</div><h3>Which action deserves emphasis?</h3><p>Choose one primary action for the page or workflow. Hierarchy fails when every button and section asks for equal attention.</p></div>
<div class="card"><div class="num">QUESTION 04</div><h3>How should the product speak?</h3><p>Write one sentence describing the voice, then add examples of words it uses and words it avoids.</p></div>
</div>
<h3>One-page brand brief</h3>
<p>Copy this structure and replace every bracketed field. Leave an item unresolved rather than filling it with a vague adjective.</p>
<div class="code-wrap">
<div class="code-label">brand.md</div>
<button class="copy" type="button" data-copy="brand-template">Copy</button>
<pre class="code" tabindex="0" id="brand-template"># Brand brief
## Product
Name: [product name]
Audience: [specific user in a specific situation]
Primary task: [one task]
Primary action: [one action]
## Direction
The interface should feel: [quality], [quality], [quality]
This means: [visible consequence for each quality]
Avoid: [three patterns that conflict with the direction]
## Voice
Voice: [one sentence]
Use: [approved words or sentence pattern]
Avoid: [words or claims that do not fit]
## Colour roles
Canvas: [value and purpose]
Structure: [value and purpose]
Accent: [value and restricted purpose]
Muted: [value and purpose]
## Typography
Display: [family, role, weight range]
Body: [family, role, weight range]
Mono: [family and restricted role]
## Layout
Container: [maximum width]
Spacing unit: [base unit]
Primary composition: [approved structure]
Mobile rule: [how it reflows]
## Agent instruction
Read this brief before editing the visual layer.
Preserve product logic and existing routes.
Use declared values. Ask before inventing an undefined visual decision.</pre>
</div>
<h3>Review the brief</h3>
<ol>
<li>Can another person explain the intended feeling without using the word “modern”?</li>
<li>Does every colour have a role rather than only a hex value?</li>
<li>Is one action clearly more important than the others?</li>
<li>Does the brief name visual patterns that should not appear?</li>
<li>Could a coding agent tell when it needs to ask instead of guessing?</li>
</ol>
<div class="callout"><h3>End of the free sample</h3><p>The remaining chapters cover DESIGN.md, colour systems, typography, layout, spacing, components, motion, accessibility, agent prompts and final review.</p></div>
<div class="hero-actions">
<a class="btn accent" href="https://edormon.gumroad.com/l/vlwod?utm_source=pixel-perfect-site&amp;utm_medium=organic&amp;utm_campaign=free-chapter-v2" rel="noopener">Buy The Design Bible · $20</a>
<a class="btn primary" href="https://edormon.gumroad.com/l/aecmk?utm_source=pixel-perfect-site&amp;utm_medium=organic&amp;utm_campaign=free-chapter-v2" rel="noopener">Buy the complete system · $24.99</a>
</div>
</article>
<aside class="side" aria-label="Chapter navigation">
<div class="side-card">
<span class="kicker">In this sample</span>
<ul class="toc">
<li><a href="#chapter-00">00 · The premise</a></li>
<li><a href="#chapter-01">01 · Brand brief</a></li>
</ul>
</div>
<div class="side-card">
<h3>Continue with the complete book</h3>
<p>Fifteen chapters delivered as a separate paid HTML file through Gumroad.</p>
<a class="btn primary" href="https://edormon.gumroad.com/l/vlwod?utm_source=pixel-perfect-site&amp;utm_medium=organic&amp;utm_campaign=free-chapter-v2" rel="noopener">Buy the book · $20</a>
</div>
</aside>
</div>
</main>
<footer class="footer">
<div class="footer-in">
<p>The Design Bible sample · Written by Ogia in Accra, Ghana</p>
<p><a href="index.html">Home</a> · <a href="design-md-generator.html">DESIGN.md guide</a> · <a href="Pixel%20Perfect%20Companion%20-%20FINAL.html">Free Companion</a></p>
</div>
</footer>
</body>
</html>