Onboarding Guide

Client journey from enquiry to live website

← Back to Dashboard
You do this
Happens automatically
Client does this
1
Create the Client
You
▾
Admin Dashboard → Onboard tab

What you do

  • Go to the Onboard tab in the admin dashboard
  • Fill in client details: name, email, company, phone, country, website URL
  • Choose their subscription tier and survey type
  • Select design type: Single Design or A/B Designs
  • Leave "Send Welcome Email" ticked
  • Click Start Onboarding

What happens

  • Client account created in the database
  • Client ID generated (e.g. 26-003-coreysbookshop)
  • Welcome email sent with password setup link (24-hour expiry)
  • If the client loses the link, they can use "Forgot your password?" on the login page to get a new one (1-hour expiry)
  • Client dashboard becomes available to them
  • Design type recorded (single or A/B) — used later for deployment and approvals
  • Survey module automatically activated on their dashboard
  • Client appears in your Clients list
2
Client Completes Survey
Client
▾
Client Dashboard → Survey module

What the client does

  • Logs in to their dashboard using the link from their welcome email (or resets password via "Forgot your password?" if needed)
  • Clicks Start on the Survey module
  • Fills in the discovery questionnaire (business details, design preferences, content)
  • Submits the survey

What happens

  • Survey answers saved to the database
  • You receive an email notification
  • Survey module shows "Completed" on their dashboard
  • Client status changes to "Design" in your admin
  • Survey data backed up to cloud storage
Your next step: Review the survey answers and decide whether to build one design or multiple options (A/B).
3
Build the Website
You
▾
Outside the dashboard

What you do

  • Build the website based on the survey answers
  • Create page layouts, navigation, and visual design

Deployment (automatic)

  • GitHub repo created and code pushed
  • Cloudflare Pages project created with GitHub connection (auto-deploys on push)
  • Custom domain assigned automatically
  • Deployment success or failure reported to System Events in admin dashboard
● Single Design
  • Build one site
  • Deploy — custom domain set automatically
  • e.g. clientname.sitethreesixty.com
● A/B Designs
  • Build two (or more) sites
  • Each gets its own custom domain
  • e.g. clientsitea.sitethreesixty.com
  • e.g. clientsiteb.sitethreesixty.com

What happens

  • Preview site(s) are live at their staging URL(s)
  • Website structure is ready for client review
  • Cloudflare GitHub integration auto-deploys on every push to main
  • Admin dashboard shows deployment status under System Events
What's next: Preview URLs and custom domains are set automatically during deployment for both single and A/B designs. Check System Events in the admin dashboard to confirm deployment succeeded.
4
Create & Deploy Content Approval Form
You
▾
SwiftBar menu bar

Content approval forms are created before design approval. This means once the client approves the design, they can move straight into content review with no waiting. For A/B clients, forms are generated for both designs upfront.

Two options in the 📋 menu

Click the 📋 menu bar icon (SwiftBar) in your Mac menu bar. Each client has two options:

Click the client name

Full flow — runs all three steps automatically:

  • Generates CONTENT-APPROVAL-FORM.md
  • Converts it to an HTML wizard
  • Commits and pushes to deploy

Use this when the form doesn't need manual edits.

Markdown Only (submenu)

Generates the markdown only — stops before HTML/deploy:

  • Generates CONTENT-APPROVAL-FORM.md
  • Opens the file for you to review and edit
  • Add pricing fields, special questions, or remove items

When done editing, click the client name to run the full flow.

What the full flow does

  • Reads the client's local website HTML files
  • Extracts all content items (headings, text, images)
  • Generates CONTENT-APPROVAL-FORM.md in the client's company/ folder
  • Converts the markdown into an interactive HTML wizard with image thumbnails from the live preview site
  • Commits and pushes to the approvals repo (auto-deploys via Cloudflare Pages)

The form goes live at approvals.sitethreesixty.com/forms/{clientname}/.

● Single Design
  • One form generated from the single site
● A/B Designs
  • Run for both designs
  • Two forms generated — one per design
  • The correct form is activated later based on which design the client chooses

What happens

  • CONTENT-APPROVAL-FORM.md generated in the client's company/ folder
  • HTML wizard created with page-by-page navigation and image thumbnails
  • Form deployed and live at approvals.sitethreesixty.com/forms/{clientname}/
  • For A/B: both forms are ready — the client's design preference in the next stage determines which one is used
Why before design approval? Having the form ready means single-design clients move straight into content review once they approve the design. No delay.
5
Design Approval
Auto You Client
▾
Automated + Approvals tab + Client Dashboard

Preview URLs are set automatically during deployment. You then trigger the design approval so the client can review the layout, colours, fonts, and overall design — everything except content.

How preview URLs are set (automatic)

● Single Design
  • Custom domain assigned automatically: {name}.sitethreesixty.com
  • preview_url set in database
  • Dashboard shows "View Preview Site" button
● A/B Designs
  • Custom domain assigned for each design automatically
  • sites array set in database with both URLs
  • Dashboard shows "View Designs" button with both options

What you do

  • Go to the Approvals tab in admin
  • Select the client and click Trigger Design Approval
  • Leave "Send notification email" ticked

What the client does

  • Clicks the link in their email (or logs in to their dashboard)
  • Reviews the preview site — this is about design only, not content
  • Answers design questions:
● Single Design
  • Do you like the layout and page structure?
  • Are you happy with the colours and fonts?
  • Is there anything you'd like added that isn't shown?
● A/B Designs
  • Which design do you prefer (or neither)?
  • Is there anything from the other design you'd like carried over?
  • Is there anything you'd like added that isn't shown?

What happens

  • Preview URLs set automatically during deployment — no manual step
  • Client reviews the design and submits feedback
  • You receive an email with their responses
  • Design module marked as complete once approved
● Single Design — what happens next
  • Content approval form is already deployed (created in Stage 4)
  • Content Approval module activates immediately on their dashboard
  • Client moves straight into content review — no waiting
● A/B Designs — what happens next
  • Client's design preference selects the correct content approval form
  • The matching form activates on their dashboard
  • Unchosen design is archived
If feedback received: Make the requested design changes, then the client can re-review using the same link. Repeat until approved.
6
Client Reviews Content
Client
▾
Client Dashboard → Content Approval module

What the client does

  • Clicks Start on the Content Approval module in their dashboard
  • Reviews every page section: headings, text, images
  • For each item: approves it or marks it for change with notes
  • Can upload replacement images directly
  • Progress is saved automatically — they can return later
  • Submits when done

What happens

  • All content decisions saved (approved items + change requests)
  • Uploaded images stored in cloud storage
  • Submission committed to the approvals repository
  • You receive an email with their submissions
  • Content module shows "Submitted" on their dashboard
✓ All content approved
  • Final Sign-Off module unlocks automatically
  • Client can proceed straight to sign-off — no waiting
  • Skips Stage 7 entirely
✎ Changes requested
  • You implement the changes (Stage 7)
  • Updated form deployed for client to re-review
  • Once approved, Final Sign-Off unlocks automatically
Fast track: If the client approves design, approves all content, and signs off — they can complete Stages 5, 6, and 8 in a single session with no waiting.
7
Implement Content Changes
You
▾
Outside the dashboard + Files tab

Step 1 — Make the changes

  • Review the client's content submissions in the Files tab or via email
  • Download any replacement images they uploaded
  • Update text, swap images, and make requested changes to the site
  • Deploy the updated site to the staging URL

Step 2 — Regenerate the approval form

Click the 📋 menu bar icon (SwiftBar) and select the client to regenerate the content approval form from the updated HTML. Then select Deploy to push the new form live.

  • Updated CONTENT-APPROVAL-FORM.md generated with the new content
  • New HTML wizard deployed to approvals.sitethreesixty.com/{clientname}/
  • Client can review the updated content on their dashboard

What happens

  • Website updated with client's approved content
  • Preview site reflects the final version
  • Updated approval form deployed for client to verify changes
  • Client re-reviews — once they approve, Final Sign-Off unlocks automatically
8
Final Sign-Off
Auto Client
▾
Client Dashboard → Final Sign-Off module

This module unlocks automatically when the client approves all content. No manual trigger needed — the client can flow straight from content approval into sign-off.

What the client does

  • Reviews the final website on the preview URL
  • Confirms they approve the design and content
  • Acknowledges the subscription terms
  • Clicks Sign Off

What happens

  • Sign-off recorded in the database
  • You receive a "Ready to Launch" email
  • Client status changes to "Complete" in your admin
  • All modules show as completed on their dashboard
9
Launch the Website
You
▾
Outside the dashboard

What you do

  • Point the client's domain DNS to the production server
  • Deploy the final website to production
  • Verify the live site is working correctly
  • Confirm launch with the client

What happens

  • Client's website is live on their domain
  • Client can continue to access their dashboard for future updates
  • Onboarding process is complete
Quick Reference
?
At a Glance
▾
Stage Who Where Outcome
1. Create Client You Onboard tab Account created, design type set, welcome email sent
2. Survey Client Client dashboard Survey completed, you get notified
3. Build You Auto Code editor + auto-deploy Site(s) built, deployed via Cloudflare GitHub integration, status in System Events
4. Create Form You SwiftBar menu bar Content approval form(s) generated & deployed
5. Design Approval Auto You Client Automated + Approvals tab Client reviews design (not content), then flows into content
6. Content Review Client Client dashboard Content edits submitted to you
7. Implement Changes You Code editor Site updated with client's content
8. Final Sign-Off Auto Client Client dashboard Unlocks when content approved, client signs off
9. Launch You DNS / deploy Website live on client's domain

360Dash Admin — Onboarding Guide
For full system documentation see Github/Automated Systems Documentation/