LeCoqRoti
A designer opens a project with fifteen interconnected pages, a library of custom SVGs and three breakpoints to check. The usual drag-and-drop surface is familiar, but the tools that keep a complex build orderly live just beneath it.
How does the device simulator handle multiple viewports?
You can open several simulator windows at once, each set to a different device — iPhone, iPad, iMac — and watch layout changes propagate live across all of them. It turns a single preview into a simultaneous multi-device check, which is invaluable when you are adjusting spacing or typography across screen sizes.
What makes the asset browser useful for larger projects?
Site assets are managed by simply dragging files into the browser, where they stay available project-wide rather than being buried inside a single page. For a site with repeating icons, brand marks or downloadable PDFs, this central pool keeps everything consistent and easy to swap out later.
How precise is the page management system?
Page management follows a straightforward logic: create a page, rename it, then drag it to reorder the site structure. There is no hidden hierarchy to decode — the drag order is the navigation order, which removes a common point of friction when a client requests last-minute menu changes.
A freelancer’s morning with a tight deadline
Picture a freelance brand consultant who has just landed a small restaurant group. The client wants a holding page with a logo, a short manifesto and a gallery of interior shots — live by lunchtime. They have no budget for a developer and no time to explain a CMS. Inside RapidWeaver 9, the job starts with a blank project, the restaurant’s wordmark dropped straight into the asset browser, and a series of full-bleed images pulled from Unsplash without leaving the app. A single page becomes the home screen; a second, nested beneath it, holds the gallery. The device simulator runs an iPhone 15 view alongside an iMac view while the consultant adjusts vertical rhythm and image scaling. By 11:15 the site is ready to export — no code, no staging server, just a folder of static files that can go live the moment the domain propagates. The speed comes not from shortcuts but from the absence of friction: assets, page order and responsive previews all sit inside one quiet, focused workspace.
Native ARM support: no emulation, no Rosetta prompt
One of the first things people ask is whether RapidWeaver Classic 9 runs natively on Apple Silicon. It does — the binary supports both ARM and x86 64-bit architectures, so there is no emulation layer and no Rosetta prompt when you launch it on an M-series Mac. The interface remains in English, and the minimum requirement is macOS 10.14 Mojave, which keeps it viable for older machines still in service at small studios.
Another recurring question concerns export control. RapidWeaver generates plain HTML, CSS and JavaScript — no database, no proprietary server-side language. You own the output and can host it anywhere, move it between providers, or archive a complete site in a single folder. People coming from hosted platforms often ask whether this complicates updates; in practice, you reopen the project file, make your changes and republish the affected files, a workflow that suits sites updated seasonally rather than hourly.
A third point of hesitation involves the “Classic” label. Realmac Software uses it to distinguish this version from newer product lines, but it does not signal an abandoned codebase — version 9.6.6 is actively maintained, and the app remains a full-featured Mac website builder for anyone who prefers designing locally over working inside a browser.
Beside other Mac site builders
Compared to Blocs, which favours a visual stacking model with pre-made sections, RapidWeaver 9 feels closer to a traditional page-layout tool. Blocs often appeals to users who want to assemble sites from ready-made blocks; RapidWeaver rewards those who prefer building their own structure page by page. The subpage system in RapidWeaver — simply dragging one page onto another — makes multi-level navigation feel natural, whereas Blocs handles hierarchy through a separate outline view.
Placed next to Pinegrow, the difference sharpens further. Pinegrow exposes the underlying code more directly and suits web designers who move fluidly between visual editing and HTML/CSS. RapidWeaver Classic 9 keeps the code at a distance; you can inspect it if you wish, but the application assumes you would rather shape a site through its inspector panels and drag-and-drop management. For a designer who writes CSS only when necessary, the RapidWeaver approach reduces cognitive load without removing control.
Sparkle occupies a middle ground, with a strong emphasis on layout canvas freedom and animation support. Its page management is flatter than RapidWeaver’s, and it lacks the built-in asset browser paradigm that makes reusable brand elements easy to keep consistent across a large project. The trade-off is that Sparkle’s canvas feels more immediately playful, while RapidWeaver 9 leans toward disciplined, repeatable site architecture — a distinction that matters most once a project crosses ten pages.
Correspondence 0
Take a chair or join the table to send a letter.
No correspondence on this note yet. Letters are read before they appear.