Saskia Teichmann
A new drawing tutorial on TOPModel has its own content type, is displayed via the theme, and must work on the appropriate language sites within the WordPress multisite network. Nevertheless, it should be easy for the editorial team to maintain in a single, clear location.
Multiple Formats in a WordPress Network
On TOPModel It features magazine articles, drawing tutorials, downloads, community content, and interactive formats. Technically, they are hosted on a multisite network that bundles the language-specific sites under a single WordPress platform.
Every language site needs appropriate paths, content types, and editorial workflows. A change to a feature can affect more than one site. This should not make the system unnecessarily complicated to use: In day-to-day operations, the editorial team must be able to maintain its content without having to remember every technical detail of the multisite setup.
Clear Structures for the Editorial Team
There is a separate WordPress plugin for each of the different formats. Within it, magazine articles, tutorials, models, friends, pets, artwork, and games are set up as distinct content types. Anyone managing a tutorial, a piece of art, or a game uses the format intended for that purpose; the templates then handle the appropriate display on the front end.
I manage the project-specific custom code related to the theme and editorial workflows. For example, if a guide or community format changes, I review not only the visible output but also the content model, the theme, existing content, and the affected language sites.
Automation and mini-games are also part of the system
In addition to the custom theme and the content type plugin, the versioned project also includes its own subscription automation and static mini-games. A magazine article, an automation, and a game work differently from a technical standpoint, but they all run on the same platform. During maintenance, PHP updates, or changes to the multisite, I check which of these components are affected.
The project repository helps me keep track of exactly that. There, I can see which of my own components are part of the project and what changes have already been made. When reviewing a new requirement, I also refer to the current state of the website.
What the Search Console figures show
From the August 1, 2025, through July 31, 2026 Google Search Console recorded the following for TOPModel 3,409,829 impressions and 125,550 clicks from a Google search.
Impressions show how often content appeared in search results. Clicks track how often a search result was clicked. The data does not count unique users, does not provide any insight into revenue, and does not prove that a single technical change caused the increased visibility.
I use these metrics to track trends over a longer period of time. If I notice a significant change, I take a closer look at the relevant content and technical conditions, because the cause cannot be determined from these two figures alone.
When new requirements arise
An editorial change can start small: a set of instructions needs to appear differently on the front end. In a multisite setup, this can affect multiple existing pieces of content and language sites. I work my way from the content type through the template to the language sites and adjust the project-specific code accordingly.
The editorial team should be able to continue managing the content as they are accustomed to. My job is to integrate the technical change into the existing system in a way that fits with the current workflows.
I describe how I test established WordPress and WooCommerce systems before making a major change in the E-Commerce System Review.
Sources
- TOPModel — Public Platform
- Google Search Console, Report for August 1, 2025–July 31, 2026
- Versioned TOPModel project repository with documentation for multisite, themes, and custom post types
