Series

Some of the work here does not fit into one article. A REST integration against a live ERP, a Core Web Vitals pass on a real theme, a set of MCP servers wired into an Adminhtml — each one is a sequence of decisions where step four only makes sense once step two has landed. Writing that as a single 8000-word page makes it unreadable; writing it as unconnected articles hides the fact that they answer each other. So it runs as a series.

How to read these

• The order is authored, not chronological. Part 3 of 5 means the third step in the argument, not the third one published. Publish dates tie and reorder; reading order does not.
• Not every set is a sequence. Some are a hub plus deep dives: one page carries the framing and marks itself Start here, the rest go deep on one piece each and stand on their own. Those read as Deep dive 3 of 6 rather than Part 3 of 6.
• Parts still to come are listed with the date they land. They are named but not linked, so the outline of a set is visible before it is finished and no link here goes to a page that is not there yet.
• You can start anywhere. Every article in a set carries the full reading order at the top and the next part at the bottom, so landing on part four from a search result still shows you parts one through three.

Articles that touch the same subject without belonging to a run are not forced into one — they show up in the related grid on each article instead, and under Topics.

The sets