Website maintenance has a reputation for being endless, and the reason is usually structural rather than technical. A content manager, a developer and a marketer all have requests, and each request arrives with its own urgency. The team ends up context-switching all day and fixing very little properly. One way to cut through this is to give each week a single theme for the site: a content week, a speed week, a link-and-redirect week, a catch-up week. The questions below look at how that works for a CMS-driven website, and what evidence you can gather to decide whether it is helping.
What does a weekly theme mean for a website team?
It means that during any seven-day period the team commits to one category of website work and defers the others. If this is content week, editors update, merge and retire pages, and developers do not schedule a theme migration for the same days. If this is speed week, the focus is image weight, caching, plugin load and template bloat. Requests that fall outside the theme are logged with a short note and attached to the week they belong to. The theme is not a ban on urgent fixes; it is a rule for everything that is merely important.
Why would themes beat a rolling to-do list?
A rolling list mixes tasks that need different tools, different people and different kinds of attention. A content edit needs a calm review of wording. A performance fix needs a profiler and a test environment. Each switch carries a cost in setting up context again, and the cost is easy to underestimate because it is spread thinly across the day. With a weekly theme, the setup is paid once. The reviewer stays in reviewing mode, the developer stays inside the template layer, and fewer half-finished changes are left on staging.
There is also a decision-count argument. If every request prompts the question “should we do this now?”, the team spends a surprising portion of its week deciding. A theme answers it ahead of time.
Which themes make sense for a CMS site?
A reasonable first set, based on what most editorial sites need repeatedly:
- Content week: update stale pages, combine overlapping ones, check headings and summaries.
- Structure week: menus, categories, internal links and the pages that show visitors where to go next. For a refresher on which pages a business site should carry, see the structural guide on which pages every business website should include.
- Speed week: measure, optimise, re-measure.
- Housekeeping week: updates, backups, user accounts, unused plugins.
- Catch-up week: everything parked, nothing new.
Teams with a service-led site might add a “service pages week”, reviewing the pages that exist to convert enquiries. The article on turning visitors into clients through service pages is a decent prompt for what to look at.
How do you decide the order?
Let the evidence pick. Pull your own data: which pages receive the most visits, which forms are abandoned, which pages load noticeably slowly on a mid-range phone. Do not rely on generic ranking lists of what “should” come first. If your analytics show that visitors arrive on category pages and leave quickly, structure week deserves an early slot. If editors complain about broken embeds and outdated screenshots, content week comes first. The order is a hypothesis, and you can revise it after a cycle.
What should be measured within a theme week?
Each theme gets one or two simple measures that you record before and after, using your own tools. Avoid borrowing figures from other sites; they say little about yours.
- Content week: number of pages reviewed, number retired, number merged, plus a note on whether search queries for those topics now land on a single page.
- Structure week: clicks to reach key pages from the homepage, and the number of orphaned pages found.
- Speed week: a lab measurement of the main templates before and after changes, noted with the date and the test conditions.
- Housekeeping week: plugins removed, updates applied, accounts reviewed.
Record these in a plain table. After two or three cycles you will have a record of what each theme actually delivered, which is better than the vague impression that “we were busy”.
What about requests that cannot wait?
Genuine incidents, such as a checkout failure or a broken form, interrupt any theme. Treat them as exceptions, log them, and look at the log at the end of the month. If a certain kind of request keeps interrupting, a missing theme is likely hiding in the data. A team that keeps patching redirects mid-week, for example, probably needs a dedicated redirect week every cycle.
A related point: set a small daily window for small requests, perhaps the final half hour of the working day. Stakeholders accept a predictable response time more readily than an unpredictable one.
How do you keep the whole team aligned?
Publish the theme calendar somewhere visible and short. A single shared page that states the current week’s theme, the next three, and the parked-request list is enough. When the site also serves visitors who need to find a physical location or pay for something, the same discipline applies to supporting pages. One example of such a tool is Proezi, a site for making arrival, payment and business pages that people open from a link or by scanning a code. Whatever you use, give the work of producing such pages its own week, so they are not squeezed between content edits.
Who owns each theme?
Name one person per week as the owner, not the whole team. The owner sets the definition of done on Monday, receives the parked requests, and signs off on Friday. Rotating the role spreads knowledge and stops one person from becoming the only holder of context. For smaller teams the owner may well be the same two people in alternation, and nothing is wrong with that provided the role is spelled out. An unowned theme tends to drift into a general backlog, which is precisely what the approach is meant to prevent.
Ownership also clarifies communication. When a stakeholder asks for something, the answer becomes “that belongs to speed week, which starts on the fourteenth, and the owner will confirm what fits.” People generally accept a dated answer more readily than a vague “soon”.
How long before the effect is visible?
Expect to need at least two full cycles. The first cycle mostly exposes how many tasks have no home, and the parked list will grow. During the second you begin to see the real benefits: fewer reopened tickets, shorter review rounds, and a clearer sense of what the site needs. Resist the urge to alter the system after one week. A fair test requires enough weeks for patterns to appear.
What are the main ways it goes wrong?
- Themes that are too broad. “Marketing week” covers too much. Break it into specific themes with a defined output.
- No owner for the parked list. Somebody has to triage it at the end of each week, or it becomes a graveyard.
- Measuring everything. Pick one or two measures per theme and record them consistently.
- Skipping the catch-up week. Without it, deferrals pile up and the team loses trust in the system.
Does a small team gain anything?
Yes, probably more so than for a large one. A team of two or three has no spare capacity to absorb context switching, so a pattern that removes it is valuable. Start modestly: pick two themes and alternate them for a month. Compare the number of tasks completed and the number reopened with the previous month’s records. If the comparison favours the themed approach, add a third theme. If it does not, adjust the length or the boundaries and try again. The point is not to follow a method for its own sake, but to test whether grouping the work reduces the scatter, using the data your own site produces.