When we do something often, it is tempting to keep the steps in our heads. An interruption can reveal how many of those small details are surprisingly difficult to recall.
Writing a process down gives the next attempt a dependable starting point.
Observe before organising
Choose a small recurring task, such as publishing an article. Complete it once and record the real steps before imagining an ideal system.
- Create a file with a title, date and description.
- Write the body and check the references and images.
- Preview the headings and mobile layout.
- Run the checks and build, then publish the static files.
Give repeated work a home
Folders, naming conventions and article templates are modest forms of automation. They remove the hesitation that appears before each fresh start.
src/content/posts/
en/
welcome-to-northline.md
reusable-workflow.md
zh/
welcome-to-northline.md
reusable-workflow.md
A useful rule does not need to account for every possible situation. It should make ordinary work natural and exceptions easy to recognise.
Remove steps that no longer help
Review the process after using it for a while. Some checks can move into tools; some steps have lost their purpose; some recurring exceptions deserve a clearer rule.
A good workflow can become shorter as you learn how to use it.