Capstone — Choosing the Right Platform for Three Real Scenarios
No-Code Site Builders
Chapter 8 · Capstone — Choosing the Right Platform for Three Real Scenarios
Seven chapters have built the pieces: a real spectrum, four platforms covered honestly, five separated trade-off dimensions, and a five-question framework. This capstone runs three realistic projects through that exact framework — deliberately landing on three different recommended platforms, since a single universal answer would contradict everything this course has argued.
Scenario 1 — A Local Bakery
| Question | Answer for this project |
|---|---|
| Portability cost | Low — no realistic reason to ever need to leave |
| Cost structure preference | One predictable bundled fee genuinely preferred — simple budgeting matters |
| Real ceiling risk | Minimal — a menu, hours, location, and basic online ordering, all within a hosted platform's own app marketplace |
| SEO priority | Secondary — local "bakery near me" visibility, which modern hosted platforms handle adequately |
| Maintenance appetite | None — the owner is running a bakery, not a website |
Recommendation: Wix
All five questions lean cleanly toward a hosted, no-code platform. Between Wix and Squarespace specifically, Wix's own app marketplace (Chapter 2) — genuine built-in ordering and booking apps — edges out Squarespace's own design-forward strength here, since a bakery's functional needs (online ordering) matter more than the more visually-driven advantage Squarespace offers.
Scenario 2 — A Freelance Photographer's Portfolio
| Question | Answer for this project |
|---|---|
| Portability cost | Low-to-moderate — personal branding, but not extreme stakes |
| Cost structure preference | Indifferent — either shape is acceptable |
| Real ceiling risk | Minimal — showcasing images well is the core, achievable need |
| SEO priority | Secondary — visual first impression matters more than search ranking for winning client trust |
| Maintenance appetite | None — wants to focus on photography, not technology |
Recommendation: Squarespace
This lands on the exact same conclusion Chapter 3's own exercise reached for a nearly identical scenario — but now arrived at through the full five-question framework rather than the editor-philosophy comparison alone, confirming the same answer two different ways. Squarespace's own design-forward templates (Chapter 3) directly serve this project's real priority: a professional-looking result without requiring design expertise.
Scenario 3 — A Growing SaaS Startup's Marketing Site
| Question | Answer for this project |
|---|---|
| Portability cost | High — a scaling company can't risk being permanently locked into a platform with no escape hatch |
| Cost structure preference | Flexibility over predictability — subscription tiers that scale with usage become expensive at real growth |
| Real ceiling risk | High — real chance of needing custom integrations (analytics, CRM, A/B testing) no page builder supports |
| SEO priority | Primary — organic search is often a core growth channel for SaaS marketing specifically |
| Maintenance appetite | Manageable — a growing company has, or will hire, real technical resources |
Recommendation: WordPress — likely a custom theme, not off-the-shelf
All five questions lean toward the self-hosted end of Chapter 1's spectrum. Given genuine growth plans and the real chance of needing custom functionality (Chapter 6's own ceiling material), this is a strong candidate for real custom theme and plugin development, exactly the territory WordPress Intermediate/Advanced covers — not just plain WordPress Fundamentals-level site ownership.
Why Dreamweaver Doesn't Win Any of These Three
An honest, deliberate observation
None of these three scenarios recommends Dreamweaver — and that's consistent with Chapter 4's own honest framing, not an oversight. Dreamweaver's genuine relevance today is largely in maintaining existing legacy sites, not starting new ones; none of these three scenarios involves inheriting an existing Dreamweaver-built site, so the question never actually arises for any of them.
Chapter Attribution
| Piece | Source chapter |
|---|---|
| The overall spectrum framing | Chapter 1 |
| Wix's own app marketplace (Scenario 1) | Chapter 2 |
| Squarespace's own design-forward strength (Scenario 2) | Chapter 3 |
| Why Dreamweaver doesn't apply here | Chapter 4 |
| WordPress + custom development as a real escape hatch (Scenario 3) | Chapter 5 |
| The five separated trade-off dimensions | Chapter 6 |
| The five-question framework itself | Chapter 7 |
Honest Scope Note
What this course deliberately doesn't cover
- No hands-on build-along for any specific tool — this course is comparative, not a tutorial, per Chapter 1's own stated scope
- No dedicated e-commerce deep dive for any platform — a genuinely large enough topic to warrant its own separate treatment if pursued later
- No specific pricing figures treated as durable facts — platform pricing changes too often for any number stated here to remain accurate for long
Hands-On Exercises
Exercise 1
Explain why the bakery scenario recommends Wix specifically over Squarespace, even though both are "fully hosted, fully no-code" platforms per Chapter 1's own table.
📄 View solutionExercise 2
Explain why the SaaS startup scenario recommends WordPress Intermediate/Advanced-level custom development rather than plain WordPress Fundamentals-level site ownership.
📄 View solutionExercise 3
Explain why this chapter treats Dreamweaver's absence from all three recommendations as consistent with Chapter 4's own honest framing, rather than as evidence Dreamweaver is simply a worse tool overall.
📄 View solutionChapter 8 Quick Reference — Course Complete
- Bakery → Wix (five questions lean cleanly hosted; app marketplace edges out Squarespace)
- Photographer's portfolio → Squarespace (design-forward strength directly serves the stated priority; confirms Chapter 3's own earlier conclusion via the full framework)
- Growing SaaS startup → WordPress, likely custom-developed (all five questions lean self-hosted; real ceiling risk is decisive)
- Dreamweaver's absence from all three is consistent with its real, legacy-maintenance-focused relevance today, not a ranking judgment
- This completes No-Code Site Builders — closing the Web Platforms subject's current roadmap alongside the completed WordPress track