How content policy fits into web design

For web designers, how to organize and plan content is an important issue, at the same time it makes people very annoying. From the management point of view, this article from the content planning, development and maintenance three stages to tell the reader, what we should do to adopt and implement the correct content strategy, while providing a number of practical methods and content planning tools, such as Basecamp, Trello, Gathercontent.

I have a big problem creating my own digital organization: organize content.

For most of the projects we encounter, the content is a very obvious bottleneck. It's hard enough to collect content from customers themselves, but it's more cumbersome to manage infrastructure, workflows, publishing technical details and certification workflows.

Let's admit that the development of content is still a huge, frustrating process. The client threw it at you. A 200-page Word document, sometimes accompanied by a CD full of scattered pictures and only a partial consensus process. How much time can you spend on sending and receiving a Word document for proofreading?

Based on the experience of managing and operating a 14-person studio, and based on three different content development phases, I would like to share some tips to help you tame this troubling process:

• Content planning: Ask questions, get first-hand requirements, create information maps – Information architecture.

• Content development: Get content from customers, focus on requirements change and certification process.

• Content Maintenance: To create a more vivid information map, to conduct a review to ensure real-time requirements and content accuracy.

The above 3 steps help us streamline our plans, manage and publish content, and make our relationship with our customers more harmonious.

Let's take a look at the steps of these three content developments in detail.

{A, Content planning}

Content planning is the most important part of the process, and it's definitely worth spending as much time and manpower as possible.

The more time you invest, the less time you will need to spend in the later stages. Putting as many people as possible at an early stage will reduce confusion, help you set the right expectations, and contribute to a better understanding of your content strategy across the team.

There are a few things to be aware of when making a content plan, so let's be specific about these considerations.

Found

Discovery is about using known customer information to find out what they need.

Getting customers involved in ' discovery ' can give you a valuable insight into what they really need-what do they think their content should be organized? Why should it be organized in such a way?

Never forget that our customers are far more knowledgeable than we are about their customers.

Try the following methods:

• Mind map: What kind of content do you need for a brain storm and why do you need it?

• Card method: A very interesting way to test the usability of users and customers. Define how content should be categorized and organized.

• Whiteboard Sketches: help you look at the structure of your site in more detail.

These content organization tools and techniques are very useful for finding out what you need and how to organize it, and also for letting users see the importance of their site content. The importance of getting customers to buy is self-evident, which encourages discovering how content is linked to their business value. This way they will think more carefully about what is available to you and will be able to provide that information more punctually.

Demand

An important result of the discovery phase is that you should have a clear need for content. Since these requirements are almost the basis for all design-required services, the sooner these findings are recorded, the better. Let everyone in the team know that this will prevent future detours.

You can consider different kinds of requirements:

• Legal requirements: For example, in the UK, trade descriptions for goods and services must be clear and accurate.

• Business identity/Brand requirements: Some companies have special guidelines and regulations for how to use their trademarks.

• Technical Requirements: For the site, for example, the request picture maximum of 550 pixels.

Of course, it's important to keep the streamlining of each requirement, even if you have a long list of different requirements to worry about.

By adding rigorous rules early on, you will encounter as few delays as possible because the project has moved forward in the process.

Content Map

Now that you have a clear understanding of the business goals of the site, you know that you will need that content in order to achieve your goals and that you have a basic set of rules for that content.

At this stage, you should have a rough outline of the basic structure of the site and the content of each page in your mind.

But before you start making interactive drafts of web layouts, even before you make a site map, (the site map usually turns into a separate page, such as Apple's Sitemap), I suggest you take a moment to create a content map.

Content maps can help you create a better site map, such as the one on Apple's website

Creating a content map should take only a few minutes, which can be a great guide to the site map.

In addition to internal pages, your content map should include content such as emails and news emails, as well as external blogs and videos. This will provide a holistic view of the content flow based on your site.

You can use Mindmeister to create a content map

Present your findings.

Now that you have a solid understanding of the layout of the content, you can begin to map these to the layout of the site. Actually, you can start designing.

By showing the results of your research to the designers, they can start building a home that is truly optimized for your content.

Collecting and editing content

When it comes to scheduling everyone's tasks, I find it useful to encourage collaboration, and to allow everyone to discuss and make contributions. To do this, you need an online, content-based platform for everyone to discuss.

I'm sure you've heard the following tools more or less:

Basecamp

Trello

gathercontent (a tool created by the original author)

Using these tools allows everyone to see a complete roadmap and clear what they should do.

If there are potential delays and impact on the overall project schedule on the route map, the relevant principals will notice and proactively circumvent these risks earlier.

{Ii. Development content}

Perhaps you'll think of the "development content" phase, where everyone goes back to their seats and completes their personal deliverables.

All you need to plan is to set goals for everyone, and now the rest is waiting for things to be done. In my experience, this is not the case.

Even with detailed content requirements, style guidelines, content maps, site maps, frames, deadlines, and surprisingly CMS (site Content management systems), it's crazy to want everything to be a natural combination. This is like expecting two designers to create two completely free pages under the same grid structure, tonal collocation, and image set.

With this in mind, I will encourage as many ongoing communication, inspection and discussion as possible, and link these links throughout the actual production process.

Some suggestions:

• Continuous communication: keep things consistent through early detail discussions

• Everyone to participate: users, content strategists, designers, development, etc.

• Conventional technical commentary: avoid interruption, or do something humiliating;

Allow users to participate in regular technical reviews, while also opening their flexible ideas, finding ways to agile and continuously develop content, and making things easier when you talk to them about maintaining and updating the content process.

{Iii. Maintenance content}

The website is on-line, the consumer also can use normally, and everything goes according to plan. Is it time to consider going home and opening a bottle of cold beer to relax?

I don't think it's time to catch my breath, at least not yet.

Items that are never obsolete are extremely rare, and there are strategies (and funds) to update and maintain the content of the site that are important to keep the project fresh, relevant and responsive to your and your customers ' interests.

Developing a Content Maintenance strategy is simple and can include the following elements:

Keep Content Editable

You don't want to end up with a Web site project, but you're suddenly cut off from all the content. By keeping your content open and organized, it makes it easier to locate and update individual modules.

The way you open the repository may be different, if you don't want your content provider to access your CMS directly, you should consider perch (perch is a simple, lightweight CMS with a detailed view of the perch site: http://grabaperch.com /), Gathercontent (https://www.gathercontent.com/), or even a simple, shared Dropbox folder (dropbox:https://www.dropbox.com/)

Set an Edit calendar

It is self-evident that the most important thing is that your users and team members can understand their expectations (and they can set aside enough time to deliver)

Guide both sides of the review

Content reviews (sometimes called content summaries) are key to maintaining a well-functioning content strategy, and they are also recognized as daunting tasks.

One tool that can help you review the process is page trawler (http://www.pagetrawler.com/), which automatically checks most of your links.

The most important thing is that you not only test user-oriented content, but also be aware of what is hidden behind the scenes, such as testing your SEO (Search engine optimization), content labels, and link reliability.

Other common problems are inaccurate dates and prices, server availability, and the details of the site-related staff.

Analysis and experiment

The last thing to consider when maintaining and optimizing content is how to analyze and test quality, efficiency, and get useful insights into the experiment.

By taking into account commonly used analytical methods such as A/b test, you can improve the efficiency of your Web content by analyzing and experimenting with web layouts, (here you can refer to A/b test for content analysis in Google to get help: http://www.cardinalpath.com/ ab-testing-with-google-analytics-content-experiments/)

Summary｝

In our view, the three phases of content development are:

• Content planning: Research content requirements, including user research, and help users understand the importance of their website or business content;

• Content development: Good work and cooperation with others, according to the road map, inspire people to continue to work enthusiasm. Hold regular discussions to make people aware of the larger goals of their website content.

• Content Maintenance: The introduction of strict editing calendar, so that content has been maintained freshness. In the context of the content review, but also to consider the content of the technical background.

These steps may seem like a lot, but the benefits are obvious: by putting content strategies back into your web design process, you can build better sites that are less stressful and you can spend time on more important things.

The content itself is not complex, and its delay and scarcity are simply a lack of planning (and Guiding principles).

I hope that through these suggestions, you will be able to find more fun in the content management of the project;

The original author introduces:

Related reading:

the importance of Web Content strategy

7 Blog Design Tips from a Content strategist

The Web strategy pyramid:a well-balanced web strategy

7 Pricing Strategies Based on the studies