LOGUE MEDIA · WEBSITE DEVELOPMENT PROCESSES GUIDE
Know what happens between the brief and the live website.
Agree the decision before building the next stage.
A project guide to decisions, review checkpoints and handover.
Use it to understand the work and prepare the inputs.
Choose the appropriate service page for the website itself.
How does a website development project move forward?
A website project moves through an agreed brief, structure and design review, production, testing and acceptance. Each stage has decisions and required inputs. Logue Media uses those checkpoints to keep the build reviewable before launch and handover.
Is this a service description?
No. This page is a project guide. It explains the development sequence and responsibilities. The Website Design, Microsites & Landing Pages, WooCommerce and AI development pages describe the different services and their specific scope.
Do all projects follow exactly the same steps?
The same decisions still need consideration, but their depth varies. A focused landing page has fewer pages than a store. Custom software needs a behaviour specification. The proposal identifies the stages and reviews appropriate to the project.
Where do costs and payment arrangements appear?
In the current commercial resource and the agreed proposal. This guide does not set prices, deposits or a fixed payment schedule. Scope, milestones and commercial terms must be confirmed for the actual project.
Progress depends on clear decisions, not just completed screens.
A response such as “looks good” may approve the colours without confirming the navigation or required functions. Production can move forward while a material decision remains open. The next review then becomes a structural redesign.
Name the decision at each checkpoint. Review the page map, key layout or function against the agreed requirement. Record what is approved and what still needs revision so the next stage has a clear basis.
Use review gates that show what is ready for the next stage.
Each review needs a named version, a decision and a clear next action. Completing a screen alone does not authorise the next stage.
The cards appear in order. Hover, tap or focus to reveal each card’s detail.
-
Bring the right version to review.
Share the current page, prototype or function with the agreed brief and real content. Tell the reviewer which decisions are needed and which elements are still unfinished.
-
Make the approval specific.
Approve the item, request a correction or raise a scope change. Tie the decision to that version so a later edit does not inherit an approval it has not earned.
-
Give the team an actionable record.
Name the reviewer, date, approved version and outstanding actions. Give each correction an owner. The team should know what can move forward and what must wait.
Real content makes the design review useful.
Agree the decision before building the next stage.
Clear approvals keep the project moving.
Prepare the right review for the project you are building.
Website & campaign pages
Review the page map, customer route and content before expanding the design.
- Agree the website purpose and decision maker.
- Identify who supplies copy, images and access.
- Review the page map before extending layouts.
- Record changes that affect the approved scope.
- Confirm launch and editing responsibilities.
Choose the relevant website or campaign service for the detailed build scope.
WooCommerce store
A store review needs representative products and purchase scenarios.
- List catalogue, payment and fulfilment decisions.
- Approve sample products before bulk entry.
- Agree representative test orders and exceptions.
- Assign trading and customer-service responsibilities.
- Approve release after the agreed checks pass.
Resolve required product and fulfilment decisions before launch.
Custom plugin or AI feature
Custom development needs a specification of behaviour as well as an interface.
- Describe behaviour and data dependencies.
- Define permission and failure cases.
- Review a working staging example.
- Check the result against acceptance criteria.
- Document maintenance, access and handover.
Use Human Defined, AI coded and Human Quality Assurance.
Record the input and output at each development stage.
The table is a project preparation guide. The actual proposal determines which deliverables and checkpoints apply. A change to an approved requirement is assessed before the downstream work is revised.
| Stage | Input and review output |
|---|---|
| Discovery | Business objective, audience and source material → agreed brief. |
| Structure | Required pages and customer routes → approved page map or wireframe. |
| Design | Brand and real content samples → approved key layouts. |
| Production | Approved layouts, inputs and functions → staging implementation. |
| Testing | Acceptance examples → defects recorded and agreed checks completed. |
| Release | Owner acceptance and access → controlled launch responsibilities. |
| Handover | Operating tasks and scope → access, guidance and named care responsibility. |
Keep scope changes visible through the project.
Choose the service Package first, then agree its review and release responsibilities.
Published website Packages start at $2,950 + GST for a template-based site of up to five pages. Landing pages and WooCommerce have their own pricing resources. This process guide explains approvals; it does not sell a separate development service.
Record the supplied inputs, approval stages and scope-change process in the proposal. Confirm responsibility for hosting, licences, content and handover rather than assuming every task is included in the build price.
Compare landing-page scope and WooCommerce scope before choosing the proposal.
Four project checkpoints keep the next decision clear.
Four decisions move the build forward. Hover, tap or focus on a stage to open its detail. Once opened, the detail stays available.
Name deliverables, input owners and the decision-maker. Confirm the commercial scope and record the version of the brief everyone is working from.
Review the page structure, actual content and important functions before expanding the build. Record approved decisions and any change to the agreed scope.
Use agreed examples to check forms, bookings, purchases or custom features on staging. Record defects, retests and any accepted limitations.
Confirm the launch decision, backups and rollback responsibilities. Hand over access, operating instructions and the agreed care arrangements.
Website Project Planning on the Central Coast.
Meet to agree decisions, inputs and review responsibilities.
Questions about reviews, changes and website handover.
Use these definitions to make the review, scope-change and handover decisions clearer.
What is a wireframe?
A wireframe is a simplified view of a page’s structure. It shows the order and relationship of key elements before the full visual design. Its purpose is to review the customer route and information hierarchy, not final colours or imagery.
What is staging?
Staging is a review environment used for development and relevant testing before live release. It should have appropriate access and indexing controls. The project identifies what is tested there and what must also be checked on production.
What is User Acceptance Testing?
User Acceptance Testing is the business’s review of the agreed functions and journeys. The owner checks representative tasks against the brief. It complements technical testing and records whether the result is suitable for the agreed use.
Can we change the brief during development?
Yes, through a visible scope decision. The team assesses the request and its effect on approved work, cost and schedule. Material changes are agreed before they are implemented.
Does handover include ongoing maintenance?
Handover identifies access and the agreed operating guidance. Recurring maintenance is a separate responsibility unless included in the proposal. The business should know who handles updates, backups and support after launch.
Choose the next part of the project brief.
Website DesignHover, tap or press EnterWebsite DesignFor this project review, give several real services a connected website rather than stretching one campaign page beyond its purpose.Explore Website Design →
Website DesignHover, tap or press EntereCommerce Website DevelopmentHover, tap or press EntereCommerce Website DevelopmentFor this project review, scope the catalogue and buying journey when the website must take orders, accept payment and support fulfilment.Explore eCommerce Website Development →
eCommerce Website DevelopmentHover, tap or press EnterAI WordPress & WooCommerce DevelopmentHover, tap or press EnterAI WordPress & WooCommerce DevelopmentFor this project review, define an add-on when an agreed business rule or data task needs more than the existing site settings.Explore AI WordPress & WooCommerce Development →
AI WordPress & WooCommerce DevelopmentHover, tap or press EnterTell us which project decision you need to clarify.
Share the planned build and the scope, review or handover question you want to resolve.
Prefer to talk? 0411 199 997 · info@logue.group