From the maintenance desk
WordPress field notes.
For the people responsible when a client site stops working. Practical guides to updates, recovery and the work between.
- Agency operations
- AI workflows
- Backups and recovery
- Monitoring
- Publishing
- Security and access
- Updates and testing
-
Live Feedback: let clients point to what needs changing
Clients can mark an element on their WordPress site and send a request. Your agency receives a task, with the same public conversation in the widget and client portal.
-
White-label WordPress development, now available through IrmaWP and 5e Labs
Meet IrmaWP’s WordPress development service for agencies: an assigned developer, dedicated PM contact and monthly capacity, delivered by Costa Rica’s 5e Labs.
-
A security update lane still needs clear approval rules
A security release deserves prompt attention, but “security” is not permission to ignore every other control. Define the rule before an alert arrives.
-
Before updating a plugin, identify what it controls
Two plugin updates can need very different checks. A gallery extension may affect a landing page; a subscription extension can affect renewals and account access.
-
Hand a WordPress task to another developer without a call
A task handoff works when the next developer can find the current state without reconstructing the whole chat. Leave the useful evidence in one place.
-
When a small website edit becomes a different request
“Change this heading” can grow into rewriting the whole service page. The work may be worth doing, but the original task no longer explains its scope.
-
Separate urgent WordPress incidents from routine requests
A broken checkout and a new team photo can arrive in the same inbox. Treating them as the same kind of urgent work makes your queue harder to trust.
-
List or Kanban: choose the view for the question
A task list is good for scanning many requests. A Kanban board helps reveal work stuck between stages. Neither view replaces a clear owner.
-
A definition of ready for WordPress agency tasks
Moving an incomplete request into “In progress” does not make it actionable. A small readiness check prevents a developer from spending the first hour collecting missing inputs.
-
When should a client request become an AI task?
A client comment is a request for your agency to review. It is not blanket permission for an AI assistant to change a live website.
-
What to check before resolving client feedback
“Done” should mean someone checked the requested result. A saved edit and a resolved request are two different events.
-
A mobile website bug needs more than “on my phone”
A menu can fail only after scrolling, after accepting cookies or at a particular text size. Those details can matter more than the phone model.