Aspecten
Download (3.2 GB)
A code editor and visual design tool for building websites, Dreamweaver sits somewhere between a plain text editor and a full local development environment. On a Mac, it can complement tools like BBEdit or Visual Studio Code by adding a live, rendered view of your HTML and CSS without leaving the application.
Code hints and live preview cut browser trips
- Code hints for HTML, CSS and JavaScript reduce the need to switch between browser documentation and your editor.
- Chromium-based live preview lets you check layout changes immediately, which a standard code editor alone does not offer.
- Basic Git support inside the app means you can commit or push without opening Terminal or a separate Git client.
Part of a larger suite
Dreamweaver shares installation and update mechanisms with Photoshop, Illustrator and other Adobe apps. It also picks up library updates through that channel; the current release includes refreshed OpenSSL, Node.js and jQuery components. This common infrastructure can simplify maintenance if Adobe's creative tools are already part of your setup, though it adds little benefit for someone who only needs a lightweight HTML editor.
Building a responsive landing page from scratch
Here's a walk-through that shows how the pieces fit together when you're not just tweaking a single file, but assembling a small site page with CSS and media queries.
- Create a new site in the Site Setup dialog. Point the local site folder to a clean directory on your Mac and leave the advanced settings at their defaults for now.
- Add a blank HTML5 document. Dreamweaver inserts the doctype, charset meta tag and a basic structure. Switch to Split View so the code sits on the left and the live preview on the right.
- In the CSS Designer panel, click the plus button and choose "Create a New CSS File". Name it
styles.cssand link it to your HTML document. The panel now shows a media selector at the top. - With no media query selected, define the base styles: a max-width container, a flexbox row for a hero section, and font sizes in rem units. As you type property values in the panel, the live preview shifts — the Chromium renderer paints the result without a manual refresh.
- Click the + button next to the media selector and add a
max-width: 768pxquery. With that query highlighted, override the flex direction to column and shrink the heading size. Switch between the two media contexts by clicking each one; the preview resizes accordingly. - Drop an image into the hero area by dragging it from the Files panel into the code. Dreamweaver writes the
<img>tag with a relative path. Use the Properties inspector to add alt text. - Open the Git panel, initialise a repository in the site folder, stage the two files and write a commit message. The basic operations — commit, push, pull — sit in a small toolbar at the bottom of the panel.
What the workflow lacks is a build step: no Sass compilation, no minification. For a simple landing page that goes straight to a shared host, that's a fair trade for seeing every layout change alongside its code.
SFTP sync hardening arrived quietly in 21.8
Version 21.8 arrived as a maintenance and library refresh rather than a feature-packed release. The updated OpenSSL and Libcurl components are invisible in day-to-day editing, but they matter if your workflow includes site synchronisation over SFTP or HTTPS connections to remote servers. Older library versions could cause handshake failures with modern server configurations; those should now be resolved.
The Node.js update affects anyone who relied on older JavaScript tooling within Dreamweaver's extension layer. Extensions built with the CEP framework now run against a fresher runtime, which can improve stability when panels like the CSS Designer fetch external data or process SCSS through an installed extension. jQuery, Lodash and RequireJS bumps are similarly under the hood; they reduce the chance of a panel freezing during long sessions with many open files.
The addition of built-in server behaviours and database bindings marks a more visible shift, though its impact depends on the kind of sites you build. Server behaviours — loops, recordset navigation, form insert and update routines — now appear without manually installing a third-party extension. If you maintain older PHP or ColdFusion sites that use these patterns, the behaviours panel is functional out of the box again. For anyone who moved on to a JavaScript-based back end, the change barely registers.
One nuisance that persists: file modification times can drift from the local time zone. In site synchronisation, the timestamp on a remotely updated file may not refresh after your Mac's system clock changes zones. A practical effect is that Dreamweaver sometimes marks a file as newer or older than it actually is during a sync comparison, which can lead to overwriting the wrong version if you click "Put" without double-checking.
Spotting the cause of a recurring freeze or sync fail
Over time a few recurring issues surface, and most have straightforward fixes once you recognise the cause.
Live view shows a blank screen for PHP files
The Chromium renderer cannot process server-side code. If you open a .php file directly from a local folder, Dreamweaver tries to render it as plain HTML and often shows nothing. Set up a testing server in the Site Setup dialog — point it to a local MAMP or Apache installation — and preview through that server path instead. The live view then requests the page through HTTP and gets the processed output.
Code hints stop appearing for JavaScript
When hints vanish, the usual culprit is a large minified library loaded somewhere in the project. Dreamweaver's parser can stall on a single huge file and stop offering completions for anything. The workaround: right-click the minified file in the Files panel, choose Cloak and exclude it from site operations. Hints return for the rest of the project. You can also restrict the scope of hinting to specific folders in Preferences — Code Hinting.
Git panel shows "Cannot connect to repository"
This error often appears after a macOS system update that changes the location of SSH keys or resets permissions. Open Terminal and run ssh -T [email protected] (or your Git host) to confirm the key works outside Dreamweaver. If it does, restart the application; the Git panel picks up the SSH agent on launch. If the error persists, remove and re-add the repository in the Git panel — it rewrites the internal reference to the remote URL.
Site synchronisation overwrites local changes with older server files
The time-zone issue introduced in recent builds can flip the "newer" status of a file. Before running a full synchronisation, click Select Newer Files in the sync dialog and visually scan the list. If a file you recently edited locally appears as a download candidate instead of an upload, right-click it and choose Put manually rather than trusting the batch operation.
Template-first builders versus a blank canvas editor
Dreamweaver, RapidWeaver, Nova and Visual Studio Code on macOS all produce a website, but the experience of the tool shapes what kind of site you end up building.
RapidWeaver takes a template-first approach. You pick a theme, add pages and fill in content blocks; the app generates the HTML, CSS and JavaScript for you. Dreamweaver sits one layer deeper: you write the code or at least see it, and the visual tools assist rather than abstract. For a brochure site with a blog, RapidWeaver gets you online faster. For a custom layout where you need to control every breakpoint and selector, Dreamweaver gives you access that RapidWeaver's theme engine conceals.
Nova (from Panic) is a native Mac editor with a strong focus on remote workflows — built-in SFTP, publishing shortcuts and a sidebar that remembers server paths. Its CSS and JavaScript support is modern and fast, and it feels lighter on disk and memory than Dreamweaver. However, Nova has no design view, no live preview pane and no visual CSS tools. If you work entirely in code and want a fast, native file browser connected to a remote server, Nova feels more immediate. If you want to see a rendering of your CSS while you write it, or drag elements into place, Dreamweaver covers that and Nova does not.
Visual Studio Code with extensions covers much of the ground Dreamweaver claims, and then some. Its IntelliSense for HTML and CSS can match Dreamweaver's code hints, and the Live Server extension gives you a hot-reloading browser preview. Git integration in VS Code is deeper — side-by-side diffs, branch visualisation and merge conflict resolution are all richer. The difference is assembly: VS Code arrives as a blank editor and you build the environment through extensions and configuration files. Dreamweaver comes preassembled; the design view, CSS panel, server behaviours and sync tools are there from the start. For a developer comfortable with configuring their toolchain, VS Code is more flexible. For someone who wants a single install that covers coding, previewing and site management without hunting for extensions, Dreamweaver still has a purpose.
Adding a seasonal menu page to a two-year-old static site
Lena works from a desk in her Utrecht apartment, juggling a handful of small-business clients. One of them, a local bakery, needs a spring menu page added to their existing static site. The site was built two years ago — plain HTML, a single CSS file and a few hand-written media queries.
She opens Dreamweaver and the Files panel shows the site structure already mapped from a previous session. She duplicates the menu.html page, renames it and opens it in Split View. The CSS Designer still has the original site's media queries listed. She adds a new query for larger bakery photos on wide screens, tweaks the grid and watches the layout respond in the live pane as she adjusts padding values.
Halfway through, the bakery owner emails a last-minute photo of a new pastry. Lena drags it from her desktop into the images folder in the Files panel, drops it into the code, and writes alt text in the Properties inspector. She switches to the Git panel, stages the new page and the image, writes a commit message and pushes to the private repository. The bakery's web host runs a simple deployment script that pulls from that repo; the page goes live without Lena opening an FTP client.
Before closing the project, she checks the Sync dialog to see if anyone else touched the server files — the time-zone quirk means she eyeballs each file timestamp instead of trusting the "newer" badge. Satisfied, she closes Dreamweaver. The whole task, from blank page to published menu, took under forty minutes in a single application.
