Content maps before station: target user, core task and page list

Templates are not the first step in building a station.

Many sites start with the first page template: pick a color and change. Logo Finally, it is asked what to write. It is easy to get a website that is so complete and has content that fights with each other. There is a solution in the navigation, and the text is a company introduction; more than a dozen blogs have been published, and readers can still not find a way to start. The content planning is not about whether the text is beautiful or not. I'm used to turning off the design tools and making content maps with a table. It doesn't need to be sophisticated, and it's enough for the team to answer, within an hour, "Who's coming, why, where to go."

Pick one of the main readers first. Don't write "all of us."

Write the target user as a judgementable scene. For example, "The first time a website is deployed to a cloud server, copy orders are not familiar with them. Linux Personal station chief is more useful than “persons with building needs”. The former can determine the extent to which the terms are interpreted and whether to provide a rollback step, and can judge whether an article should be written. Four things have been completed for the main reader: the current situation, the tasks that you want to do, the most feared risks, and how to identify them. A secondary reader can keep, but the front page and the core line give priority to the same category of people.

Replace the word "what I want to say" with the word "what the reader wants to accomplish."

List tasks first, then pages. For example, site-type websites, readers may have to perform these tasks: to decide which station to choose, to buy a domain name, to deploy, to open HTTPS 502. Each task corresponds to a page that can solve problems independently, rather than inserting all content into the Service Description. It is suggested that the task should be marked with three levels: completion, decision-making and confidence-building. The pages that must be completed are prioritized; the pages that help decision-making are responsible for ICP; and the confidence-building pages include author descriptions, sources, updates of records and contact details. This order prevents teams from taking two days to make a rotation when the core curriculum is not finished.

Organization of articles with content pillars, not by labels

The content pillar is a few stabilization themes, such as " Site Guides" and " Servers and Deployments " . A shallow-to-deep learning path follows each pillar. Labels can be described. Docker, Caddy, SEO , but it should not replace the field. Too many columns can turn navigation into a word warehouse, and there are many empty categories of only one or two articles. For each pillar, write a boundary note: what does it contain, what does it contain. “Services and deployments” include, for example, production deployments, backups, surveillance, and mistying, and do not write news about cloud vendors.

Make an executable page list

Tables keep at least seven columns: page name,URL, target reader, main task, core keyword, next page, header. The following is an example of a reduced version:

URL There are rules for this move, and there is no hurry to create empty pages. URL, keep priority; when you do want to change, record old addresses, target addresses, and re-direction plans, and cannot simply change names in the menu.

Check the content map for a break.

Take three real jobs and walk from the portal: can readers reach the target page within two or three options after the search results or the front page enter? Is there a reasonable next step to reading the article? If you write "Welcome to Us" at the end of each article, the learning path is cut off. Make another deletion: entries that do not have a clear reader, have no separate task, and repeat content with other pages first move out of the first range. The site has 12 solid pages in one issue, which are usually more credible and easier to maintain than 50 placeholders.

The delivery of this piece.

Once completed, a list of pages should be obtained, not a slogan: a major reader, two to four content pillars, the first page of each pillar, stability URL Rules and clear relationships. Next steps in. Static stations,WordPress and Next.js Technical Options, converts content requirements into maintenance costs and technical constraints.