WordPress websites

A WordPress website your team can keep up to date.

Give your business in Vietnam a WordPress website with clear pages and editing tools, planned around your customers, content languages and the people who maintain it.

Edit within your role

WordPress content · illustration
DRAFTAbout

Prepared content for the about page.

Authorised reviewer

Review before publication

Published layout · illustration
SAMPLE PAGE
ABOUTClear information.
Find what you need.

Approved content, organised around the reader’s needs.

ContentNavigation
An illustration of content structure and editing workflow.
Scope to agree
  1. 01Choose WordPress for a defined need
  2. 02Separate editing from administration
  3. 03Hand over the maintenance process too

Define content types, editing permissions and tools before development. Handover includes guidance on drafting, reviewing and publishing; responsibility for system updates is agreed separately.

AT A GLANCE

Use WordPress when your team needs editing access and a clear handover.

Inputs
Editing needs, staff roles and required functions.
Delivery
Design, editing permissions and usage guidance.
Agree
Plugins, licences, backups and update ownership.

Platform

Choose WordPress for a defined need

Choose tools that fit the actual requirements.

Content your team updates

Identify pages, posts and changing information. Choose an editing approach suited to the responsible person and provide clear guidance.

Design within the agreed scope

The proposal identifies custom design, any existing theme or reused components, and the site-building tools. Agree these before development so you know what will be delivered.

Extensions with a purpose

Each plugin or connection should serve a requirement. Review licences, costs, access and update ownership before including it.

AN IMPLEMENTATION EXAMPLE

Who writes, who reviews and who maintains the site?

An example responsibility split for a WordPress site. Actual permissions are checked against its configuration.

Edit within your role

WordPress content · illustration
DRAFTAbout

Prepared content for the about page.

Authorised reviewer

Review before publication

Published layout · illustration
SAMPLE PAGE
ABOUTClear information.
Find what you need.

Approved content, organised around the reader’s needs.

ContentNavigation

Content is approved before publication; actual permissions follow the site configuration.

Content contributor

Prepare content and drafts within assigned permissions for the responsible person to review.

Reviewer / editor

Check copy, images and links; publish where the role has suitable permissions.

Administrator

Manage configuration, accounts and required tools, with ownership of agreed technical changes.

What belongs in an update check?

Record the owner, a recoverable backup, planned changes and checks afterwards. Test forms, content and essential functions before closing the work.

What is handed over?

The agreed accounts, editing guidance, tool and licence records, and renewal ownership. Any ongoing support is scoped separately.

A static example for discussing your project’s structure and workflow.

WordPress references: Roles and capabilities · Updating WordPress.

Editing

Separate editing from administration

Match access to the work each person needs to do.

Roles matched to work

Identify writers, reviewers and administrators. Test permissions in the actual setup; editing an article should not require giving everyone administrator access.

Draft, preview and publish

Explain editing within the assigned permissions. Check images, links and the published layout rather than only the editor screen.

Content transfer and forms

Inventory content to enter or migrate. Test forms, recipients and plugin-backed functions with sample data before handover.

Maintenance

Hand over the maintenance process too

Assign updates, backups and licence renewals.

Back up and check updates

Agree who updates WordPress, themes and plugins. Prepare backups and recheck essential flows; updates can introduce compatibility issues.

Accounts and licences

Hand over agreed accounts and configuration, with licence owners and renewals recorded. Keep access and documentation under business control.

Build and running costs

The quote covers page layouts, content, functions and any migration. Hosting, domains, paid plugins or themes, and update support are listed separately.

HOW WE WORK

Clarity at every step.

  1. Define editing needs

    Review content, roles and the existing site.

  2. Approve the approach

    Agree layouts, content structure and required tools.

  3. Build and test roles

    Check layouts, forms and tasks for each role.

  4. Guide and hand over

    Explain editing, backups and operating responsibilities.

PRICED BY SCOPE

Define the work before the quote.

Send your requirements and sample material so we can define a suitable scope.

Request a quote

What determines the cost

  • Page count, supplied content, content management, languages and integrations. For an existing site, we review its structure and functions; technical access is agreed where needed.
  • Booking systems, payments, data synchronisation and paid plugins are quoted where needed; domain and hosting are separate.
How costs are scoped →

FAQ

Before we begin.

A few useful answers to help define the right scope.

Does every website you build use WordPress?

No. The build approach follows requirements. WordPress is one option for suitable editing needs; custom-coded sites have a separate scope.

Can the design be custom?

Yes. The proposal sets out the custom design, any existing theme or reused components, and the site-building tools before work begins.

Can we edit the content ourselves?

Administration covers the agreed content and permissions. If the scope includes Vietnamese and English pages, agree who drafts, reviews and updates each version. Handover includes guidance; major structural or functional changes can need separate development.

Will we need paid plugins or a theme?

It depends on the solution. Agree paid components, licence ownership and renewals first. No single plugin bundle is assumed for every project.

Who maintains it after handover?

Your team can manage it or agree separate support. Assign updates, backups, renewals and checks; these are not automatically in the build fee.

WordPress websites

Let’s define the work you need.

Share your goals, available material and preferred timing. We will clarify the work, deliverables and cost.

Discuss your project