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.
Technote
Development workflow
Git, .gitignore, CI/CD, WP-CLI and staging — treating a WordPress site like code rather than like a live server you edit.
63 articles· Development workflow
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
What to check before a theme update
Postponing an update is not a plan. Once you know what can break, updating stops being frightening and becomes a procedure with an order.
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.
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.