A website people can use. A CMS your team can manage.

A CMS project begins with what visitors need to understand and what your team needs to change. Bring representative service pages, articles, images and contact routes. We use that material to plan the page structure, design approach and editing model before choosing the final implementation.

The work can include a new website, an existing-site rebuild or an improvement to an established WordPress setup. The proposal names the templates, content types, reusable sections and connections included. A public information site and an authenticated business application are different commissions; required private workflows need their own scope.

For a migration, useful content and existing destinations are part of the brief. We identify what remains, what changes and who approves the replacement. The optional image exercise below illustrates one publishing decision within this wider website service.

Some information belongs in a shared entry; some depends on where it appears. A service name may need one approved source, while a page introduction needs its own context. Use representative updates to decide which relationship is helpful.

Discuss permissions through tasks: preparing a draft, reviewing a public preview, approving publication and maintaining dependencies. The chosen site must support the agreed responsibilities. Flexible editing should not require every colleague to understand the full technical setup.

Imagine an approved photograph showing a finished project. Its detail supports a project page, but the same photograph is also used in a wide banner. A single crop hides the feature described by the banner caption.

The CMS brief can give editors an appropriate image choice, focal treatment or caption for each agreed placement. Preview both uses before publication rather than assuming the media-library entry settles every context. The exact controls depend on the implementation selected. This is a hypothetical editing exercise, not a Melbourne client story or a claim about default WordPress behaviour.

Ask the future editor to prepare another ordinary page with the agreed controls. Supply practical guidance for images, links and approvals, together with the route for requesting a new layout. Separate ongoing maintenance from the launch deliverables so the team knows who handles updates, recovery and later development.