Troubleshooting guide
Custom Websites: Diagnostic Guide
Custom Websites: Diagnostic Guide organizes the decisions that matter for organizations planning a new website, redesign, portal, directory, or online service: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
Custom Websites rollout scorecard
Use the scorecard to keep each phase tied to an operating outcome rather than a list of completed tasks.
| Phase | Required outcome | Proof before proceeding |
|---|---|---|
| Phase 1: Business and service website development | Reduce or resolve a template cannot support the required workflow | Verified result involving responsive HTML, CSS, React and modern web stacks |
| Phase 2: Custom portals, directories and booking systems | Reduce or resolve the current site no longer represents the business | Verified result involving laravel, PHP, Node and database backends |
| Phase 3: Responsive redesign and content architecture | Reduce or resolve content and navigation have become confusing | Verified result involving payments, booking, CRM and email integrations |
Record the symptom before changing it
A template cannot support the required workflow. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as responsive HTML, CSS, React and modern web stacks.
- Save exact error text
- Record the last known working date
- List recent code, content, vendor, DNS, or account changes
Separate reachability, data, and behavior
For Custom Website Development, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Reachability check for payments, booking, CRM and email integrations
- Data or content check related to business and service website development
- Behavior check for custom portals, directories and booking systems
Use stop conditions
Frame the first scope around business and service website development and one observable acceptance journey. Treat custom portals, directories and booking systems as a later phase unless the evidence shows it is a true dependency.
- No confirmed backup
- Unknown production ownership
- Security or payment data may be involved
Verify the repair in the real journey
Repair fits when the core remains sound. Extension fits when the boundary around responsive HTML, CSS, React and modern web stacks is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Business and service website development
- Responsive redesign and content architecture
- CMS and structured content architecture