The aesthetics of a short domain: making three letters memorable
Use the rhythm of jqj.cc to build a consistent identity across icons, page headers, and written names.
THE ANNALS / READING ROOM
Writing to return to.
Observations, questions, and the details that remain after the noise settles.
PUBLISHED CHAPTERS
Follow a reading path →↗
A seeker's digital garden: room for unfinished ideas
Organize a personal site with clear states, connections, and revision notes so developing ideas can be presented honestly.
From bookmarks to curation: a directory people can use
Add purpose, audience, and conditions to turn a private bookmark into a useful recommendation.
From draft to publication: a small-site checklist
Review real content, complete interactions, and clear boundaries instead of treating a finished appearance as a finished product.
Celestial circles and sundials: the ritual of space in an interface
Revisit Junction's original imagery of circles, dials, paper, and ink, and turn the idea of space into a reading practice.
Give type a range—and reading some room
Build a reusable typography starting point by considering body size, scale, spacing, and viewport together.
Punctuation and wrapping: a rhythm for both languages
Test real headings, long links, and bilingual paragraphs without forcing both languages into the same visual rhythm.
What to check after the contrast ratio
A color-pair check is a beginning; text size, backgrounds, focus, and error states still need review in the actual page.
From SVG to favicon: start small
Move from an editable source to a browser tab by separating coordinates, pixels, and file formats—and testing each destination.
One seal, three iterations: give every change a reason
Compare shape, spacing, and accent on one canvas, turning “make it nicer” into decisions you can review.
Article share cards: give people a reason to open the page
Build a card around a clear title, a specific benefit, and an honest source, while distinguishing an image from a web preview.
A small project's README: make the result usable by someone else
Explain purpose, inputs, outputs, limits, and repeatable steps so a project remains understandable without its maker beside it.