For a company website, prepare five sets of materials: a page list, copy confirmed by the business owner, images and brand files with traceable sources, product or service information, and contact details for each language. Give each item a purpose, an owner and a confirmation status so designers and editors can see which pages are ready and what still needs work.
This guide is for businesses preparing a new informational website or a redesign, particularly teams whose materials are spread across sales, marketing and technical staff. A practical starting point is one real product or service: complete its content handover, then extend the approach to the remaining pages. Use the company website CMS selection guide when choosing the platform.
1. Agree on pages and material owners
A suggested first release includes the homepage, About page, product categories, product detail pages, news or useful articles, and a Contact page. Service businesses can use service categories and solution pages for the corresponding information. For every page, record its audience, the next action a visitor should take, the material provider and the person confirming the facts.
- Company owner or manager: confirms the public company and brand names, business scope, contact details and release scope.
- Product or business staff: provide specifications, application conditions, service boundaries and supporting materials, and confirm public claims.
- Marketing staff or editors: organize copy, image purposes, translations and missing items, and maintain the handover list.
- Website staff: confirm display positions, required fields, image cropping and mobile readability against the actual theme.
Also confirm the domain administration contact and the email address and telephone number intended for enquiries. Technical staff should coordinate deployment and the environment used to receive enquiries. Transfer accounts through an agreed secure channel; keep the public-page material pack limited to information approved for public display.
2. Prepare the homepage, About, news and Contact pages
Homepage: help visitors recognize the business
Suggested materials include a clear business introduction, links to main products or services, verifiable company information and an obvious contact entry. The opening copy should name the intended customers and what the company offers. Support descriptions of strengths with identifiable facts. Choose factory, product, team or application images to suit the actual layout, and mark the subject that should remain visible after mobile cropping.
About: make identity and capabilities specific
Prepare the formal company name, brand name, business scope, office or production location information, and team or facility photographs approved for publication. Have the owner check the sources and current validity of founding dates, qualifications and service-region claims. For client names, project photographs and logos, record the confirmed scope of public use.
News or useful articles: complete one source pack first
A suggested pack contains a title, event or question background, body copy, image captions, sources and actual dates. Company news should explain what happened and why customers might care; a useful article should answer one customer question with practical steps. Supply the listing summary and cover image as well. Base the initial article count on the material available. See the website content maintenance checklist for ongoing handover.
Contact: check that the next step works
Prepare the public company name, address, telephone number, email address and service regions. Add opening hours or appointment details where applicable, and confirm the purposes of Chinese and English address versions. For an enquiry form, specify what customers should submit, who receives enquiries and the confirmation copy. Arrange an acceptance test with a submission clearly marked as a test.
3. Build categories and product pages from consistent facts
For category pages, agree whether products are organized by application, series or another business dimension. Provide a short description and representative image for each category. Sales and product staff should confirm the grouping so customers can find an entry that matches their needs.
A suggested product detail pack includes the name and model, applications, main features and supporting evidence, specification names and units, optional configurations and their conditions, image captions, related documents and an enquiry entry. Have the business owner confirm which items can be public. For changeable information such as lead times, specify the applicable conditions and how customers can obtain confirmation.
Use one complete product as a sample to agree the specification order, listing summary and detail layout before preparing the rest. Check differences between similar models individually. See the product catalog implementation guide for fields and page planning.
4. Supply original images, display copies and usage records
Keep a vector source or high-resolution master of the logo in the brand pack so designers can create suitable display files. Verify upload formats against the current system configuration and page implementation. Preserve original product photographs alongside cropped display copies, with the product model, camera angle, caption and destination page.
Size example: a particular theme might display an image area at 16:9. A designer could test a 1600 × 900-pixel image, then adjust it for clarity, file size and mobile cropping. These are illustrative layout-testing values; determine delivery dimensions from the chosen theme and device checks. Put essential model names and explanations in page text as well, making them easier to read and maintain.
A suggested usage record includes the filename, source, provider, date photographed or obtained, purpose, usage scope and location of related confirmation documents. Confirm the relevant conditions for purchased images, employee portraits, client project photographs and trademarks. Refer uncertain items to the responsible owner. This is a team material-management recommendation; verify actual usage arrangements against the applicable agreements.
5. Review Chinese and English against the same facts
Start with a terminology list for product names, models, units, company names and industry terms. Then prepare complete English titles, body copy, search descriptions, image captions and contact text. Keep models and specifications aligned; adapt language, address formats and service-region explanations to the audience. Open downloadable files and check their language, applicable models and revision.
AI can help organize and translate confirmed materials. Product or business staff should verify the facts, and a language reviewer should check the writing. Record each language's review status and confirmation date on the page material card.
CatchCMS maintains multilingual values by field. Enable the relevant translation setting for dynamic fields that need language-specific values. A missing field translation falls back to that field's base value, so inspect the English page item by item. See multilingual content management for setup and fallback behavior.
6. Copy this material card for each page
The following suggested format can be copied into a team document. Create one card per page; add the particular model's specifications and documents for a product detail page.
- Page: name / type / category / planned languages / existing URL or proposed path.
- Purpose: audience / main question to answer / next contact or browsing entry.
- Copy: page title / short introduction / body / search description / related pages.
- Facts: specifications and units / applicable conditions / source document location / business reviewer and date.
- Images: originals location / display copies location / subject and captions / source and usage-scope records.
- Languages: Chinese draft location and status / English draft location and status / terminology reviewer.
- Delivery: provider / editor / reviewer / gaps / target completion date / scope ready for this release.
- Acceptance: public URL / mobile check / language switching / images and files / contact entry / check time.
Suggested statuses are “awaiting materials,” “awaiting confirmation,” “ready for entry” and “accepted.” Maintain them in the team document according to the agreed process. The card serves as a handover record.
7. Handle missing materials in stages
Fictional workflow example: an equipment company is preparing a page for PX-100. It has a confirmed model, applications and specifications, plus one genuine product photograph. Permission to use an installation photograph is being confirmed, and the English manual is under review.
A suggested first release covers the core information the company can truthfully deliver: confirmed product copy, specifications, the product photograph and an enquiry entry. Use a complete, reviewed translation for the English page. Track the installation photograph and English manual download as outstanding items, adding them after confirmation. When a missing fact affects a customer's assessment of suitability, obtain it before publishing the associated content.
This example illustrates a decision process. For every gap, record an owner, affected pages, completion conditions and a target date. Agree the current release's acceptance scope with the website team. Where the project needs a visual preview, clearly label placeholder material in the internal preview and replace or remove it before public release.
8. Enter the materials in CatchCMS and complete handover
CatchCMS provides content models, dynamic fields, multilingual content and admin content management. Website staff configure the content structure from the material list and connect the relevant fields to the theme. Verify both data entry and public display. See content models and dynamic fields for configuration, and the theme development and launch checklist for page delivery.
A suggested division of responsibility has the business owner confirm facts, editors maintain confirmed materials, and website staff handle theme and technical issues. Keep usage records, material cards and manual confirmations in team documents. Formal approval workflows, automated asset review and automatic file version management require project-specific implementation and acceptance.
Before release, check each page's title, description, body, image cropping, mobile readability, language switching, files and enquiry entry. Technical staff should verify URLs, canonical addresses and applicable structured data. Complete the homepage, one product and the Contact page first, then extend the handover to the remaining pages. Share planned pages, languages, available materials and gaps through project enquiries to agree the scope of CatchCMS configuration, theme work and content preparation.