The outcome

Produce a maintainable website with clear control over files, credentials, and future updates.

Step by step

A workflow you can repeat.

  1. 01

    Write the audience, pages, content, visual direction, functional requirements, and explicit exclusions.

  2. 02

    Ask for the information architecture and technical plan before Manus writes or deploys code.

  3. 03

    Build one complete flow with realistic content and test desktop, mobile, empty, and error states.

  4. 04

    Inspect the generated files, dependencies, forms, analytics, secrets, accessibility, and legal content.

  5. 05

    Export or connect the code, assign ownership, and use a controlled production deployment with rollback.

Working standard

What good use looks like.

  • Own the source code.
  • Never paste production secrets into a task.
  • Test forms and failure paths manually.

Official references

Check the current product documentation.