Development workflow Advanced
A growth checklist for the next six months
What a site that has started working needs in place so the next stretch does not break it — checked across four areas.
Technote
WordPress know-how, from real work Technotes worth picking
16 articles· Development workflow · Founders
Development workflow Advanced
Spotting the signals of technical debt without being a developer
You can see debt without reading a line of code. The signals appear first in schedules, conversations and screens.
Development workflow Practical
After payment is where it starts: automating handover
For the customer, payment is not the end but the beginning. A few silent minutes afterwards will shake the trust you just earned.
Development workflow Practical
The one-page handover document
If one person knows where the domain is registered, the business is tied to that person. A single page removes the problem.
Development workflow Practical
Thirty minutes twice a year to find what you stopped using
Fixed costs cause trouble not when they grow but when they are forgotten. Here is a review that starts from the statement rather than from a list of…
Development workflow Practical
The night-before launch checklist
Most problems found after launch could have been found in thirty minutes before it. Here is the list, in order.
Development workflow Practical
Freelancer or agency: the real difference is continuity
Neither is better. They carry different risks, and the contractual moves that cover those risks are different too.
Development workflow Practical
The work that costs more when you do it yourself
A founder's time is not free. Doing it yourself or handing it over is a calculation, not a preference — and the items that belong in the calculation…
Development workflow Practical
The point at which you need a staging site
Editing straight on the live site works only while the site is small. Once those thirty seconds touch revenue and trust, the rules change.
Development workflow Practical
What belongs in a maintenance agreement
If you pay a monthly fee and cannot say what you get for it, the agreement is missing scope and response times. Four clauses make it workable for…
Development workflow Practical
The handover list: what you must receive before it is finished
A site being live is not the same as a site being handed over. Three bundles — files, accounts and documents — decide whether the next person can…
Development workflow Practical
A publishing rhythm you can keep
Slower but unbroken beats a burst of writing followed by two silent months. Rhythm does not come from willpower — it comes from stock and a routine.
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.