Practical use cases
What you can build.
A few ways to put Portal Audit, Projects and Portal reuse to work. Start with the portal and the problem—not a blank canvas.
01 / Portal Audit
An inherited portal.
A clearer starting point.
You need to understand a configuration before proposing work. Run a read-only audit, inspect scored evidence and bring relevant findings into a branded report or PDF.
- The artifact
- Scored findings and a report to review.
- The human decision
- Which issues belong in the implementation brief?
Configuration review / Workflows
A dependency needs attention.
A workflow references a property that needs review. Inspect the evidence before deciding whether to change the workflow or its prerequisite.
Report finding ≠ automatic fix
02 / Projects
A brief becomes
connected assets.
Scope a website enquiry process: a property for the enquiry type, a form to capture it, and a workflow for the agreed follow-up logic. Review the plan before generating the assets.
- The artifact
- A dependency-aware asset plan and generated assets.
- The human decision
- Does the generated setup match the brief, and is it ready to deploy?
- PropertyEnquiry typeDefine the values the form needs.
- FormWebsite enquiryReference the agreed property.
- WorkflowEnquiry follow-upReview enrollment and routing logic.
03 / Portal reuse
Keep the pattern.
Resolve the local detail.
Bring selected assets from an established setup into another portal. Match destination assets and remap their references rather than carrying source IDs into a different environment.
- The artifact
- A destination-specific mapping and deployment result.
- The human decision
- What can be reused here, and what needs a different implementation?
Studio portal
Harbour portal
- Property reference
- Match the destination schema
- Pipeline reference
- Resolve the destination ID
- Owner reference
- Review the local owner
Another destination means another review.