Artikel pembuatan website

Artikel August 2022

Company website content planning is the activity of determining information, the owner of the material, and the order in which it is presented before development progresses too far. Start with the reader's question, then organize the page's function, required materials, and approving parties. On this basis, the design can follow the content that will actually be used, instead of waiting for the text to be filled in after the entire display is complete.

Content includes more than articles: service descriptions, images, documents, form labels, and results messages as well as visitor experience sections. FourVM places material readiness in the needs discussion so the team knows what is available, needs to be updated, or needs to be created from scratch.

Inventory materials before creating new materials

Collect old websites, brochures, presentations, service lists, photos and documents that the team still uses. Note the version, owner information, usage permissions, and sections that need to be checked. Don't immediately assume that all materials can be published just because they are already available in the company folder.

Separate material that is still correct from information that has changed. Contact numbers, service names and experience claims need to be checked by someone who understands the data. Old materials can save work, but they can also introduce errors if moved without review.

List the gaps that affect the core page. For example, a service already has a name but there is no explanation of the work results or examples of customer needs. The list becomes preparatory work that needs to have a person in charge and a schedule.

Formulate reader questions for each page

Decide who will read and what decisions need to be made. Services pages can address job matches, while profile pages provide context to the company's identity. With this division, the team does not need to put all the information in each place.

Use questions that arise from sales or service conversations. For example, what the customer must prepare, who handles the request, and what the service limits are. Real questions help select more useful content than a list of slogans about professionalism.

Google provides content evaluation guidelines that emphasize the usefulness and reliability of information. Use it as an editorial tool, not a ranking formula. Material still needs to be checked according to the company's conditions and the actual needs of the readers it will serve.

Create a concise content brief

For each page, note the purpose, audience, main question, core message, supporting evidence, and next action. Add information sources as well as approvers. Briefs allow writers and designers to understand the function of a page before working on the details of its appearance.

Example of simulation: the training page is aimed at HR managers who need to know the target participants, materials, form of implementation, and how to submit requirements. The supporting material can be in the form of an approved syllabus. Uncertain parts are marked for clarification, not filled in with estimates.

Distinguish the content brief from the final manuscript. The brief provides direction, while the manuscript translates that direction into content that is ready to be examined. Changes to requirements in the brief can affect the structure, so it is best to agree before all the pages are written.

Determine the layout before calculating the length of the text

Sort the information from the most important answers to supporting explanations. Readers should be able to recognize the relevance of the page without going through a long preamble. Use sections that each answer one group of questions so the content is easy to scan.

W3C Page Structure Tutorial explains the relationship between semantic structure and navigation. Apply headings according to content relationship, not just visual size. A clear design helps visitors as well as editors understand the section being read or updated.

The length of the text follows the explanation requirements. Don't overstretch service descriptions with repetition just because there's empty space in the design. On the other hand, don't omit important work boundaries simply so that all sections have the same number of rows.

Prepare pictures and documents for information

For each image, note the function and context you want to convey. Activity photos require different captions than flowcharts. Make sure usage rights and publication approval are clear before material is included in the design.

W3C Writing for Web Accessibility describes the use of meaningful titles, links, and alternative text. Compile the material with the script, not as additional work forgotten at launch. Images that contain important information need to have context-appropriate explanations.

Check downloaded files separately. Documents can store different contacts or service versions of website pages. Note the file name, date and owner of the update so that information changes don't stop in one place.

Manage approvals and versions of materials

Determine one source of the manuscript as a reference. Revisions from text messages or meetings need to be summarized to that source before being implemented. Without version control, editors can work on old comments while reviewers read a different manuscript.

Use statuses that differentiate authoring, checking, approving, and deploying. The approved manuscript does not yet prove that the page uses the correct version. After implementation, the information owner needs to check the results in the environment to be published.

Determine who can change facts and who decides language style. Writers can tidy up presentations, but should not guess at operational data. This separation helps corrections occur more quickly because questions are directed to the owner of the appropriate information.

Connect materials to design and development

Use real content examples when reviewing plans, especially long titles, service lists, and documents to link to. Example text that is too short can hide display problems. However, the use of real materials still requires paying attention to access limits in the test environment.

For the overall development stages, read guide to creating a company website . Content planning helps provide the ingredients for that stage, not replacing functional testing and management readiness.

Keep a list of pending materials and their impact on the launch. If a section isn't ready, consider whether it can be delayed without breaking the main flow. Business owners and implementers need to know this decision so that no blank pages are published accidentally.

Simulation case study: design complete, services not yet agreed

This simulation is not a FourVM customer report. A company approves displays with multiple service cards. As of writing, the operations team explained that some services are part of the same package, not separate offerings.

The team created a content brief to differentiate the function of each page and combine similar sections. The design is adjusted before all the materials are included. They determine the owner of the information so that the description of the service does not change following the latest incoming opinion.

The lesson is that the content structure needs to be discussed before the design is considered final. Real materials can demonstrate needs that are not visible in the example text. Early clarification helps reduce changes that actually originate from service definitions, not display errors.

Simulation case study: lots of material, no final version

A team has brochures, presentations, and profile documents that are all up to date. Service and contact names differ between files. The author does not know which materials should be used for website pages and downloaded documents.

The team designates the owner of each group of information, flags applicable sources, and notes material that must be discontinued. The final manuscript is checked together with the attachments before implementation. After that, the next update follows the established source.

The lesson is that the amount of material does not equal the readiness of the content. The clarity of the version and approval determines whether the material can be used safely. Source notes help new editors get on with their work without redoing entire folders.

Frequently asked questions

Does all content have to be finished before development begins? The parts that affect structure and function need to be clear enough first. Some filling can take place in stages if the format, volume and approver have been agreed upon.

Who should write? Choose a party that is able to present material to readers, with facts checked by the owner of the information. In working with FourVM, agree on the division of writing and proofing from the start so that content requirements do not become hidden assumptions.

Source

  1. Google Search Central — Creating helpful, reliable, people-first content. Evaluate the usability and reliability of the content . The date of publication is not recorded; accessed 14 November 2026.
  2. W3C WAI — Page Structure Tutorial. Semantic structure and navigation . Updated April 8, 2026; accessed 14 November 2026.
  3. W3C WAI — Writing for Web Accessibility. Titles, links and alt text . The date of publication is not recorded; accessed 14 November 2026.
Share