"No-code" gets used as though it names one single category of tool. It doesn't. This chapter lays out the real spectrum it actually spans — and previews exactly where each of this course's own later chapters sits along it, including WordPress Fundamentals, already covered in real depth elsewhere on this site.

A Spectrum, Not a Category

This Course's Own Roadmap

What This Course Is — and Isn't

This is a comparative, decision-focused survey — not a build-along tutorial for any single tool. WordPress Fundamentals teaches you to actually run a WordPress site step by step; this course exists one level up from that, helping decide whether WordPress (or Wix, or Squarespace, or something else entirely) is even the right starting point for a given project in the first place.

Hands-On Exercises

Wix sits at the "fully hosted, fully no-code" end of Chapter 1's own spectrum — this chapter covers what that actually means in practice, both the real convenience it buys and the one real cost that comes with it.

The Drag-and-Drop Editor

Wix's own signature feature is genuine freeform positioning — elements can be placed anywhere on the canvas, pixel by pixel, rather than being constrained to a fixed template grid. This is real design freedom within the platform's own boundaries, closer to a visual design tool than a fill-in-the-blanks template system.

Wix ADI — AI-Generated Starting Points

Wix ADI (Artificial Design Intelligence) builds a starter site automatically from a short questionnaire — business type, style preferences, existing content — genuinely useful for getting from nothing to a reasonable first draft quickly, before manually refining it further in the drag-and-drop editor.

The App Marketplace

Wix's own app marketplace extends site functionality — booking systems, contact forms, online stores — in the same spirit as WordPress Fundamentals 6's own plugin ecosystem, but architecturally different: every app runs entirely within Wix's own closed platform, not as portable, independently-owned code the way a WordPress plugin's files are.

Real Strengths

The Real Limitation — Portability

Hands-On Exercises

Squarespace sits at the exact same "fully hosted, fully no-code" position on Chapter 1's own spectrum as Wix — but the editing philosophy underneath that shared position is genuinely different, and the lock-in it shares with Wix shows up from a second, distinct angle worth naming separately.

Template-Driven, Not Freeform

Where Wix's own editor allows placing elements anywhere on a blank canvas, Squarespace starts from professionally-designed templates and edits within defined sections and blocks rather than free positioning. This constraint is deliberate, not a missing feature — it exists specifically to guide design decisions the user might otherwise get wrong.

Design-Forward Strengths

E-Commerce Features

Squarespace includes built-in online store functionality — inventory management, payment processing — comparable in spirit to Wix's own store apps, but more tightly integrated into the core platform by default rather than added on separately.

The Same Lock-In, From a Different Angle

Squarespace shares Wix's own structural platform lock-in exactly, per Chapter 2's own reasoning — a Squarespace site can't be exported to run elsewhere any more than a Wix site can.

Hands-On Exercises

Wix and Squarespace share one deep architectural trait: both are hosted platforms managing everything end to end. Dreamweaver shares almost nothing with either — it isn't a competitor occupying a nearby spot on Chapter 1's own spectrum, it's a fundamentally different category of tool entirely.

What Dreamweaver Actually Is

Dreamweaver is a desktop application (part of Adobe Creative Cloud) combining a visual "Design" view with a real "Code" view, often shown side by side — you can drag elements visually or write HTML/CSS/JavaScript directly, watching both stay in sync. Critically, Dreamweaver produces real, standalone HTML/CSS/JS files — it doesn't bundle hosting the way Wix or Squarespace do. Those files still need to be uploaded to independently-purchased hosting, historically via FTP, before anyone else can see them.

Where This Actually Sits on Chapter 1's Own Spectrum

Historical Context, Honestly

Dreamweaver (originally Macromedia's, acquired by Adobe in 2005) was the dominant professional web design tool through the 1990s and much of the 2000s — the default choice before hosted platforms and modern frameworks existed in anything like their current form. Wix (2006) and Squarespace (2004) hadn't yet captured the "no-code, no hosting hassle" audience Dreamweaver was never built to serve in the first place.

Why It's Still Genuinely Encountered Today

This isn't purely historical — real, current reasons keep Dreamweaver relevant in specific contexts: legacy sites originally built in it still exist and occasionally need maintenance; some creative-agency workflows still favor designers comfortable with a visual tool over a pure code editor; some small studios and individuals who learned it years ago have simply never had a reason to switch.

Hands-On Exercises

Chapter 1's own spectrum table already separated WordPress into two distinct positions — "self-hosted CMS alone" and "self-hosted CMS + page builder." This chapter goes deep on both, and places them honestly against Wix, Squarespace, and Dreamweaver rather than treating WordPress as automatically superior just because this site already covers it in depth.

WordPress Without a Page Builder

WordPress Fundamentals covers exactly this position — content-level editing via the Block Editor (its own Chapter 4) is already genuinely no-code, letting a site owner build real, flexible page layouts using blocks, patterns, and reusable blocks with no PHP at all. Full site-wide design control — headers, footers, complex custom templates — traditionally required either a classic PHP theme (real code, covered in WordPress Intermediate/Advanced) or, on modern block themes, Full Site Editing, itself also block-based and no-code.

Page Builders — A Further No-Code Layer

Plugins like Elementor add a more Wix-like freeform, drag-and-drop visual builder on top of WordPress — letting a site owner construct full page layouts (in some cases including headers and footers) visually, without touching PHP templates or the classic theme system covered in WordPress Intermediate/Advanced at all.

An Honest Caveat — Page Builders Aren't Free of Trade-Offs Either

Hands-On Exercises

Chapters 2 through 5 surfaced real trade-offs one platform at a time. This chapter pulls five of them out as their own named dimensions, deliberately kept separate rather than folded into one vague "it depends" — because a platform can genuinely win on one dimension and lose on another, and collapsing them together hides exactly that.

1. Portability & Vendor Lock-In

2. Cost Structure — Not Just "Which Is Cheaper"

This is about the shape of the cost, not simply which option is cheapest overall — that depends heavily on how long a site runs and how it's used.

3. The Real Ceiling

What happens when a project needs something the platform's own built-in tools genuinely can't do?

4. SEO Control

This deserves an honest, non-oversimplified treatment rather than a blanket verdict either way.

5. Ongoing Maintenance Burden

Hands-On Exercises

Chapter 6 named five real trade-off dimensions, deliberately kept separate. This chapter turns each one into a concrete question you can actually ask about a real project — this course's own central chapter, and the one every scenario in Chapter 8's own capstone will run through directly.

Five Questions, One Per Dimension

These Answers Don't Have to Agree — That's the Point

A Light Worked Example

Chapter 8's own capstone applies this same framework to three genuinely harder cases, where the five answers pull in real, different directions.

Hands-On Exercises

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

Scenario 2 — A Freelance Photographer's Portfolio

Scenario 3 — A Growing SaaS Startup's Marketing Site

Why Dreamweaver Doesn't Win Any of These Three

Chapter Attribution

Honest Scope Note

Hands-On Exercises