Day
Open sky, pale stone and moss. A bright field guide.
The field notes / design reference
Design, theme & brand.
A pixel-punk character. A clear, comfortable field guide. Blocks, recipes and builds should be easy to explore—and easy to read.
The identity
The Block Graph A VANILLA MINECRAFT FIELD GUIDE
From your first resource to a repeatable supply.
01 / Identity
A name with a purpose.
The Block Graph is a field guide to how vanilla Minecraft resources connect. Its identity combines the familiarity of a workbench with the curiosity of a map: explore the connections, compare editions, and plan the next build.
- Name
- The Block Graph
- Descriptor
- A vanilla Minecraft field guide
- Promise
- From your first resource to a repeatable supply.
- Character
- Pixel-punk, practical, curious and precise.
The wordmark
Use the full name in Jersey 15. Keep the letterforms upright and give the name breathing room. A text-only lockup works when the crafting-table mark is too small.
The current mark
The textured crafting table connects the guide to making things. Preserve the block’s proportions and native colors; keep surrounding interface surfaces quiet.
The current mark uses Minecraft artwork. Keep its texture attribution with the project; the game artwork is not an original Block Graph logo.
02 / Typography
Character in the headings.
Comfort in the reading.
Use Saira for the home hero headline and the design page’s introductory title. Use Jersey 15 for other headings and the wordmark. Use readable sans-serif text for paragraphs, build instructions, forms and dense information: Arial or Helvetica in the tools and Saira on the home page. Keep long text left aligned, with a generous line height and a short enough line to follow comfortably.
Home hero headlineShared site typography
Chart a course to every block.
Design page titleShared site typography
Design, theme & brand.
Page titleShared site typography
Cobblestone production
Section headingShared site typography
Setup & outputs
Card headingShared site typography
Choose your route
Reading textShared site typography
Mine only the centre cobblestone. Keep both fluid sources and the supporting blocks in place, then wait for the output to reform before mining again.
Home page textShared site typography
Get turn-by-turn directions to your next build. Start small. Think big.
55–70 characters for sustained reading1.6–1.7 line height for paragraphsSentence case for labels and headings
Keep compact tool labels at a readable size; use 16 px for longer reading surfaces. These are live specimens using the same CSS rules as the site. Font names and metrics above are read from the rendered text and update with the viewport. Download Jersey 15 · Font license.
03 / Theme
Daylight and blue slate.
Day uses pale stone and moss beneath an open sky. Night moves to blue slate and moonlight. Keep blocks, item textures and biome colors recognizable in both. Use the controls above to preview the page; select a swatch to copy its color.
Night
Blue slate, moonlight and muted moss. A quiet workbench.
Colors and layout widths are read directly from the shared application CSS.
Edges, not decoration
Use square corners, thin divisions and restrained bevels. Let selected controls carry the accent. Keep large reading surfaces calm and textures out from behind paragraphs.
State stays legible
Pair color with a label, underline or pressed state. Show clear keyboard focus. Keep body text stronger than dividers and decorative details.
04 / Layout
Give the task room to breathe.
The layout should follow the reader’s question. Lead with the useful result, keep related controls close, and put conditions beside the claim they qualify. Let supporting detail open on demand.
Introduction
Shared CSS widthA clear promise, a useful preview, and a short route into the tools. Let sky and terrain frame the content.
Workbench
Shared CSS widthUse the available width for inventory, paths and inspection. Keep the selected edition and task visible.
Farm detail
Shared CSS widthOne flat workspace: a prominent Edit blueprint action, then blueprint and materials beside setup and instructions. Conditions, evidence, other versions and sources stay visible. Stack in reading order on narrow screens.
A flat farm workspace
Keep the title, edition and a prominent Edit blueprint action at the top. Show the build and its instructions side by side, using spacing and thin rules instead of nested cards. Conditions, evidence and other versions stay visible without expansion. Keep long instructions at the shared reading size.
Blueprint & materialsVersion choice → interactive build → operation → inventory → visible conditions and evidence
Setup & instructionsOutputs and inputs → build and operation → visible source designs and other versions
A steady rhythm
Prefer a 4 px base and repeat a small spacing scale.
4816243248- Collapse columns into a single reading order on narrow screens.
- Give the home compass its own space beside the headline. Stack the farm preview before the hero gets cramped, and center the compass below the headline on mobile.
- Keep edition and version visible when behavior depends on them.
- Give touch controls at least 44 px of usable height.
- Reserve wide canvases for spatial tools; keep reading columns narrower.
- In the blueprint editor, put save and export actions above an always-visible block list and coordinates.
05 / Components
A useful kit of parts.
Actions are direct. Alternatives are explicit. Required materials use real item images and quantities. Evidence appears as written status, with more detail available where it matters.
Cobblestone production
Illustrated example
Water
LavaGenerate
CobblestoneConnection pattern: sources → process → output.
Conditions & evidence
Both sources are setup stock. Mining consumes pickaxe durability. This is a connection diagram; inspect the farm page for a spatial build and its verification status.
Actions & choices
Edition specimenBedrock · 1.26.40.05. The farm link follows this choice.
Illustrated exampleVersion check needed
Keep review state separate from visual polish. A convincing blueprint is not proof of in-game behavior.
06 / Voice
Say what the world does.
Write like a patient builder showing someone the next step. Use concrete objects and verbs. Keep the excitement of discovery, and be precise about what is known.
The voice in practice
Mine only the centre cobblestone. Keep both fluid sources and the supporting blocks in place. Wait for the output to reform, then repeat.
Action → what to preserve → what happens next.
Useful and specific
Say “waterlog the spruce stair,” “collect the drops,” or “check the selected edition.” Keep instructions in short paragraphs, with one action or idea at a time.
Honest about evidence
Say “version check needed” when it is. Distinguish a family reference, an illustrated layout and an in-game test. Avoid promises of universal compatibility or guaranteed output without evidence.