Tag: users
-

the pipeline that posts itself: how m4d’s instagram content actually ships
Every post on @march4orthdesign is decided, built, and shipped by one file, and nobody opens it to check what’s next. Most content calendars are a decision someone has to keep making: what format today, what topic, who’s writing the caption. M4D replaced that decision with a state machine. `content/queue.md` holds the whole rotation — carousel,…
-

-

-

how i built this site with the system i teach — one file, every decision derived
—
by
This site isn’t a demo of a design system. It runs on one — a single token file drives every color, spacing value, and type decision on the page you’re reading. Most design systems content has a credibility problem. The system gets taught from mockups. The examples live in a sandbox. The person explaining tokens…
-

-

vercel vs. godaddy: how we decide where to deploy each project
Not every project needs the same infrastructure — and using the wrong one costs you either speed or money. The M4D stack runs two different hosting setups for two different reasons. The projects site (static HTML, design system docs, blog) lives on GoDaddy — it’s a flat file site that deploys via FTP, loads fast,…
-

i built a design system business in 6 weeks using only claude code
—
by
in AI, Automation, Color, Components, Educational, Illustrations, Images, Sites, Styleguides, Tokens, Typography, UI/UX, Web DesignSix weeks from first commit to a deployed product site, a content pipeline, a Gumroad membership, and a MailerLite funnel — one designer, one tool, no team. On April 25, 2026 I ran git init in a Google Drive folder. On June 5 I had a functioning design system business: a static site deployed to…


