Deployment module
Continuous Improvement and Deployment Workflows
Use manual and Git-based deployment workflows to plan, build, test, deploy, verify, monitor, improve, and repeat.
Learning Objectives
By the end of this lesson, you'll be able to:
- Explain deployment as an ongoing improvement cycle
- Use manual and Git-based workflows safely
- Choose monitoring tools for specific problems
- Maintain a simple change log
Why This Matters:
Deployment is not the end. It is how the website starts receiving evidence from the real world.
Before You Start:
You should be familiar with:
- Testing and Troubleshooting a Live Website Review here
The Improvement Cycle
Plan -> Build -> Test -> Deploy -> Verify -> Monitor -> Improve -> RepeatDeployment is not a graduation ceremony for a website. It is the start of a cycle. After a site goes live, real browsers, real networks and real users provide evidence. The calm workflow is to make one sensible change, test it, deploy it, verify the result and record what happened.
Manual Workflow
Edit locally
-> Test locally
-> Back up live files
-> Upload changed files
-> Test live site
-> Record the changeManual updates are acceptable for small sites if they are deliberate. Keep a local copy, back up files before replacing them, upload only what changed when you can, and write down the change. Without a record, the next person has to solve the same mystery again.
Git Workflow
Create or choose a branch
-> Make changes
-> Test locally
-> Commit
-> Push
-> Preview deployment
-> Review
-> Merge
-> Production deploymentKeep this beginner-friendly. The point is not to perform ceremony; the point is to make changes traceable and reversible.
For beginners, the Git workflow can stay simple: commit working changes, push to the connected repository, review the preview if the platform provides one, then merge or deploy to production when ready. The value is not ceremony. The value is a trail of what changed and when.
Monitoring and Feedback Tools
| Tool | Problem it helps solve |
|---|---|
| Browser developer tools | Shows console errors, failed network requests and loaded files. |
| Lighthouse | Checks performance, accessibility, best practices and SEO signals. |
| Google Search Console | Shows indexing, search visibility and crawl problems. |
| Vercel Analytics | Helps Vercel-hosted projects understand traffic and performance patterns. |
| Cloudflare Web Analytics | Lightweight traffic analytics for sites using Cloudflare. |
| Uptime monitoring | Alerts when a live site becomes unavailable. |
| Deployment logs | Explain what happened during build and publish steps. |
| Change log | Records what changed, why, how it was deployed and what happened after. |
Improvement Log
Memory is not a reliable release-management system.
| Date | Change | Reason | Deployment method | Result | Follow-up |
|---|---|---|---|---|---|
| YYYY-MM-DD | Compressed hero image | Slow mobile load | Git push | Lighthouse improved | Check again next month |
Continuous Improvement Knowledge Check
Before moving forward, can you answer these?
- Why should live changes be recorded?
- What is the purpose of a preview deployment?
- Name one monitoring tool and the problem it helps solve.
Check Your Answers
- A change log helps future maintainers understand what changed, why, how it was deployed and what happened next.
- It lets you inspect changes in a live-like environment before production.
- Examples include Lighthouse for performance/accessibility checks, Search Console for search visibility, analytics for traffic patterns, uptime monitoring for outages, or deployment logs for build failures.
How confident are you with this concept?
Still confused | Getting there | Got it | Could explain it to a friend
Ready for the Next Deployment Step
Key Takeaways:
- Deployment is a publishing workflow, not just a button.
- The live URL is where deployment evidence is gathered.
- The right hosting path depends on files, update workflow, support needs and ownership.
- Troubleshooting starts with the first meaningful error.
Learning Objectives Review:
Look back at what you set out to learn. Can you now:
- Use manual and Git-based deployment workflows to plan, build, test, deploy, verify, monitor, improve, and repeat. Check!
If you can name which part of the system you are changing, test the live result and record the outcome, deployment is becoming a repeatable workflow.
Think & Reflect:
Deployment evidence
- What would prove this site works for someone else?
Next action
- What should be recorded so this deployment can be repeated later?
Looking Ahead:
Next: continue with Deployment Lab and Final Checklist.
Recommended Next Steps
Continue Learning
Ready to move forward? Continue with the next tutorial in this series:
Deployment Lab and Final ChecklistRelated Topics
Explore these related tutorials to expand your knowledge: