Development workflow Practical
Define “done” before the work starts
Without a completion standard, handover becomes an exchange of impressions. Agreed acceptance criteria protect the client and shield the supplier from endless revisions.
Technote
WordPress know-how, from real work Technotes worth picking
16 articles· Development workflow · Founders
Development workflow Practical
Whose name are the domain, the hosting and the repository in?
The single most regretted item in this series. Accounts in someone else's name cause no trouble at all while the relationship is good — and every kind of…
Development workflow Intro
How to read a quote: scope, exclusions and what comes after
The most important part of a quote is not the number — it is scope and exclusions. Without both in writing, every later dispute becomes an argument about…
Development workflow Intro
Write requirements as goals and constraints, not screens
Handing over a folder of reference sites gets you a fast quote and the wrong result. Goals, constraints and acceptance — three headings fit on one page.
Cited
Technotes worth reading next
Topics outside WordPress are collected on Dongji Communication Tech Insights, run by the same team. The summaries below are quoted from the originals; the titles link to them.
-
Working with AI
Writing a CLAUDE.md — teaching an AI coding assistant your project
AI coding tools such as Claude Code, Cursor and Copilot do better work the more precisely they know your project. Here is a structure and a set of principles that hold up.
-
Working with AI
Prompting an AI for UI design — drafting with Claude and GPT
Asking an AI to "make a nice button" gets you a disappointing button. Structured prompts that carry constraints, references and a defined role get you the design you meant.
-
Themes & plugins
SCSS from the ground up — variables through module structure
The core syntax of SCSS (Sass) and what it solves that plain CSS cannot: variables, nesting, mixins, @use and module structure — organised around patterns you can use immediately.
-
Themes & plugins
Design tokens and theme colour systems — brand identity in SCSS variables
How to turn a colour palette from a pile of hex codes into a system that means something — semantic token structure and SCSS variable patterns, from a real project.
-
Performance optimization
Designing a responsive typography system — the science of readability
Hard-coded pixel font sizes are over. Type scales, fluid sizing with clamp(), Korean webfont optimisation and line-height ratios — building typography that reads well on any screen.
-
Development workflow
From Figma to SCSS — a designer-developer handoff guide
Minimising what gets lost between a Figma file and the code: extracting tokens, naming components, keeping the spacing system in sync — the whole workflow, step by step.