Buy

Getting started

Free & Premium

WebDonkey Pages builds websites through conversation. You describe what you need in the chat, Pages writes the website, checks it after every change and puts it online, either as a ZIP for your host or straight to your own server. You never have to touch code, a terminal or build output. This chapter takes you from installing the app to your first draft.

Pages runs on your Mac. Every website is a folder of its own inside WebDonkey Pages in your home folder, and building, previewing and checking all happen locally. You don't need WebDonkey for any of it, though it adds a few extras.

What you do here

The window

Title bar

  • WebDonkey Pages with the logo on the far left always takes you to the Your websites overview.
  • Next to it you see where you are, for example All websites › website name, Settings, Changelog or Docs. Clicking All websites brings you back to the overview.
  • Inside a website, the website's buttons sit on the right: Import/Export, Show folder in Finder (folder icon), Edit website (pencil icon), Test in WebDonkey (only while WebDonkey is running) and Publish. While Pages is busy, it shows what it is doing in front of them, for example Building … or Checking ….
  • The badge With WebDonkey, Without WebDonkey or WebDonkey outdated shows whether Pages is connected to WebDonkey (With and without WebDonkey).
  • The book icon opens the Docs, the gear opens Settings.

Status bar

Entry Meaning
Kit with version The Pages kit Pages builds and checks with. Kit missing means Pages can't build (Requirements).
AI via Claude Code or AI via API key The AI access in use right now. Hover over it to see whether it comes from Settings or is the open website's own access (AI access).
Licence state Free, the name of your package or a state such as Subscription expired. Clicking it opens the licence dialog.
Update with version Only when a new version is ready. Clicking it opens the update notice.
Version The installed version of Pages.

How to work inside an open website is covered in the Workspace chapter.

Free and Premium

Without a licence you get one website with every feature and publish through the ZIP export. A Pages package adds more websites and uploading straight to your server. The details are under Free and licence.

Install Free

WebDonkey Pages is a Mac app. You install it once, and from then on it keeps itself current through its built-in updates. The Pages kit, which Pages uses to build and check websites, ships inside the app.

What you need

  • A Mac with macOS 11 or later, with Apple silicon or an Intel processor.
  • To work on websites you also need Node.js, a Chromium browser and an AI access. The details are under Requirements. You can install and launch Pages without them.

How to do it

  1. Download the WebDonkey Pages disk image (DMG) from the download page in the shop.
  2. Double-click the DMG file to open it.
  3. Drag WebDonkey Pages into the Applications folder.
  4. Launch WebDonkey Pages from Applications.
  5. Pages opens the Your websites overview. If something is missing, the notice Pages is not ready yet: at the top lists what.
  6. Add what is missing and restart Pages. Then create your first website with New website.

What happens in the background

  • On first launch Pages creates the folder WebDonkey Pages in your home folder. Every website gets its own subfolder there. Settings › Technology › Websites folder shows the exact location.
  • Settings, your list of websites, your own themes, the licence and encrypted keys and passwords live in the app folder ~/Library/Application Support/app.webdonkey.pages/.
  • On launch Pages looks for Node.js, a browser for the checks and Claude Code. What it finds is shown under Technology.
  • If WebDonkey is installed on the same Mac, Pages connects to it on its own at launch (With and without WebDonkey).
  • Building, previewing and checking happen on your Mac. Pages goes online for the AI, the licence, updates, the docs, the theme gallery and publishing (Data and connections).

Troubleshooting

What you see Why What to do
The Pages kit is not installed. and Kit missing in the status bar The app is incomplete, the bundled kit is missing. Reinstall Pages from a fresh DMG.
Node.js 22.12 or newer is needed. Pages can't find a suitable Node.js. Install Node.js 22.12 or later and restart Pages (Requirements).
Google Chrome is missing for the checks. Pages finds neither Google Chrome nor Chromium nor Microsoft Edge. Install one of these browsers in Applications.
WebDonkey Pages could not start. Pages couldn't read its data at launch. Quit Pages and start it again.

See also

Requirements Free

Pages builds and checks websites with tools on your Mac and writes the content with an AI. It needs four things for that: the Pages kit, Node.js, a browser for the checks and an AI access. Pages brings the kit itself, the rest you set up once.

Where to find it

  • If something is missing, the Your websites overview shows the notice Pages is not ready yet: at the top with a list of what is missing.
  • Settings › Technology lists every tool with its location, or missing (Technology).
  • The status bar shows the AI access: AI via Claude Code or AI via API key.

The Pages kit

The kit contains everything Pages uses to build, preview and check websites. It ships inside the app and is replaced with every update. The status bar shows Kit with its version. If it says Kit missing and the notice reads The Pages kit is not installed., the installation is incomplete. Reinstall Pages.

Node.js 22.12 or newer

The kit runs on Node.js, version 22.12 or later. Pages doesn't ship its own Node.js but uses one that is already installed. It looks in this order:

  1. ~/.local/bin/node
  2. /opt/homebrew/bin/node (Homebrew on Apple silicon)
  3. /usr/local/bin/node (Homebrew on Intel, the installer from nodejs.org)
  4. the versions installed with nvm under ~/.nvm/versions/node/
  5. your terminal's search path

Pages takes the first Node.js that is new enough. If it finds none, the notice reads Node.js 22.12 or newer is needed. Without Node.js and the kit, the chat input stays locked and Pages can't build. Install a current version and restart Pages.

A browser for the checks

After every change Pages checks the website, among other things for accessibility and layout on narrow screens, and before publishing also with Lighthouse. These checks run in a Chromium browser without a visible window. Pages uses Google Chrome, Chromium or Microsoft Edge from the Applications folder, and Google Chrome also from the Applications folder in your home folder.

If none is there, the notice reads Google Chrome is missing for the checks. Building and the preview still work. Pages then skips the browser checks and says so in the check result: Chrome not found, browser checks skipped (Checks).

An AI access

Claude writes texts, pages and design in the chat. You need one of these:

Route What you need Who pays
My Claude Code Claude Code installed and signed in on this Mac runs through your Claude Code sign-in
Anthropic API key a key from the Anthropic console your Anthropic account

You choose the route under AI access. Each website can also have its own access, for example a client's API key (Edit website). AI costs never run through the Pages licence.

Pages looks for Claude Code in ~/.local/bin/claude, ~/.claude/local/claude, /opt/homebrew/bin/claude, /usr/local/bin/claude and your terminal's search path. Without an AI access the chat shows The chat needs access to an AI. with the link Set up now.

Optional

  • WebDonkey on the same Mac adds local testing with PHP and the contact form, plus your saved servers (With and without WebDonkey).
  • A server with SFTP access for publishing directly, which needs a Pages package (Publish to your server). Without a package you export the website as a ZIP for any host.

Troubleshooting

What you see Why What to do
Node.js is installed but Pages still says Node.js 22.12 or newer is needed. The version found is older than 22.12, or Node lives somewhere Pages doesn't look. Check with node --version in Terminal. Install a newer version, for example through Homebrew or nodejs.org, and restart Pages.
The My Claude Code card says Claude Code is not installed on this Mac. Pages can't find Claude Code in any of the places above. Install Claude Code, sign in and restart Pages. Or use an API key.
The chat input is greyed out. The kit or Node.js is missing, or the website is archived or locked. Add what the notice in the overview names, or see Website status.

See also

Your first website Free

A name is all a new website needs. Pages sorts out the rest with you in the chat: what you offer, for whom, where, and how it should look. This page walks you through the first round, from creating the website to the first draft in the preview.

How to do it

  1. In the Your websites overview, click New website. If you have no website yet, the button also sits in the middle of the empty overview under No website yet.
  2. Under What is your business or project called?, enter a name, for example your company's.
  3. Leave AI access for this website on As in Settings to use the access from Settings. For a client's key, choose Claude API (New website).
  4. Under Website languages, choose the languages the website should appear in. German is preset. Add a language adds more, and with several you set the Default language (at “/”).
  5. Click Create. Pages creates the website's folder and opens it.
  6. The chat opens on the left with a greeting: Pages asks what you offer, for whom and where. Under For example: there are three sample texts. Clicking one puts it into the input field, it is only sent when you send it.
  7. Describe your business in a few sentences and press Return or click Send. ⇧ plus Return starts a new line.
  8. Pages gets to work. The chat shows Pages is thinking … with the steps it is taking below. Then Pages builds and checks the website.
  9. The preview shows the first draft. From now on you describe in the chat what should change, such as colours, sections or texts.

If you don't like a change, take it back with Undo below the input field, and Redo brings it back (Undo).

What comes next

  • Fill in the facts: for the legal notice, the privacy policy and publishing, Pages needs details such as your address, domain and host. Pages asks for them in the chat, and you can enter them yourself under Facts (Facts). While something is open, the website's card shows Open facts.
  • Add photos: drag photos from Finder into the window (Photos).
  • Look at the checks: Pages checks after every change on its own. What the check reports is under Checks (Checks).
  • Publish: once everything is in place, click Publish at the top right (Publish).

What happens in the background

  • Pages creates a folder for the website inside WebDonkey Pages in your home folder and sets up the basic files there.
  • Every message goes to the AI you chose. If the AI changes something, Pages rebuilds the website and checks it. If the change fails the checks, Pages tries to fix it. If that doesn't work, Pages discards the change and tells you in the chat.
  • Every change creates a version in the History (History).

Free and Premium

In Free you have one active website with every tool for building and checking. For a second website, archive the first one or get a Pages package (Free and licence).

Troubleshooting

What you see Why What to do
The chat needs access to an AI. Neither Claude Code nor an API key is set up. Click Set up now and set up an access (AI access).
The chat input is greyed out. The Pages kit or Node.js is missing. Look at what the notice Pages is not ready yet: in the overview names (Requirements).
Free includes one website. From the Personal package on you can create more. A website is already active in Free. Archive the existing website or enter a key through Enter licence.

See also

With and without WebDonkey Free

Pages runs fully on its own, licence included. If WebDonkey is installed on the same Mac, Pages connects to it at launch and uses what WebDonkey adds: a local address with PHP for testing, your saved servers, theme, language and licence key. Both states are valid, neither is an error.

Where to find it

A badge sits on the right of the title bar. Hover over it for a short explanation of what applies right now:

Badge What it means
With WebDonkey WebDonkey is installed and recent enough. “WebDonkey provides the local address with SSL, PHP for testing the contact form and your saved servers.”
Without WebDonkey Pages finds no WebDonkey on this Mac. “Pages runs fully on its own. With WebDonkey you also get a local address, form testing and saved servers.”
WebDonkey outdated WebDonkey is installed but too old for Pages. “Please update WebDonkey. Until then Pages runs on its own.”

Pages checks this once at launch. If you install or update WebDonkey while Pages is running, restart Pages afterwards.

What WebDonkey adds

Feature What you get What it needs
Test in WebDonkey WebDonkey serves the website at a local address of your choice with PHP. That way you can try the contact form too, messages arrive in WebDonkey under “Mail” (Test in WebDonkey). WebDonkey must be running, otherwise the button is missing from the title bar.
Saved servers When publishing, you pick a server you saved in WebDonkey instead of typing host and user again. With Manage you create, change, test and delete servers (Server access). WebDonkey must be running and have Premium. Publishing directly and Manage also need a Pages package.
Theme Follow WebDonkey makes Pages wear the same theme as WebDonkey. Your own themes from WebDonkey can be taken over as copies (Choose a theme). Your own themes in WebDonkey, for the copies.
Language Pages speaks the same language as WebDonkey (Language). nothing else
Licence key If WebDonkey holds a different key than Pages, Pages offers Use the key from WebDonkey (Activate a licence). a key in WebDonkey
Open in Pages On the Sites page in WebDonkey, websites from Pages lead straight back into Pages with Open in Pages (The websites in WebDonkey). a website you test in WebDonkey

What stays separate

  • Pages has its own data and its own settings. It only reads WebDonkey's data and never changes it itself. Anything new in WebDonkey, such as a website's local address or a server added through Manage, WebDonkey creates when you ask for it.
  • Pages never receives your servers' passwords or passphrases from WebDonkey. You enter them in Pages.
  • Pages checks its licence with the shop itself, never through WebDonkey. One key can still unlock both apps, and on one Mac WebDonkey and Pages share one licence seat (States).
  • Without WebDonkey you only lose local testing and the saved servers. Building, checking, the preview, the ZIP export and publishing directly work the same.

Troubleshooting

What you see Why What to do
Without WebDonkey although WebDonkey is installed WebDonkey hasn't created its data on this Mac yet, or it was installed after Pages started. Launch WebDonkey once, then restart Pages.
WebDonkey outdated The WebDonkey version is too old. Update WebDonkey and restart Pages.
The Test in WebDonkey button is missing. WebDonkey isn't running. Start WebDonkey and open the website in Pages again.
WebDonkey is not running. Start WebDonkey and try again. Pages can't reach WebDonkey. Start WebDonkey.

See also

Free and licence Free & Premium

Pages is fully usable without a licence, for one active website. Free means: chat, building, checks, preview, history and every tool for working on the website are yours without restriction, and you publish through the ZIP export. A Pages package adds more websites and uploading straight to your server.

What Free includes and what a package adds

Free With a Pages package
Active websites one as many as your package includes
Chat, building, checks, preview, history, texts, photos, facts yes yes
Multilingual websites yes yes
ZIP for your host yes, with the text link “Built with WebDonkey Pages” in the footer of every page yes, without the link
Upload to a server (SFTP) no yes
Test connection, Browse … and Prepare server no yes
Create, change, test and delete servers in WebDonkey no yes, with WebDonkey Premium
Export a backup and import a website yes yes
Test in WebDonkey yes, while WebDonkey is running yes
Choose themes, create your own, take themes from the gallery yes yes
Submit your own themes to the gallery no yes

The packages are called Personal, Business, Studio and Agency. An Add-on extends the number of websites. How many websites your package includes is shown in the Licence section in Settings (Packages and allowance). Prices and a comparison of the packages are at webdonkey.io/pricing.

How to unlock a package

  1. Buy a Pages package in the shop. See packages in the shop in the Licence section takes you there.
  2. Open Settings › Licence, or click Free in the status bar.
  3. Enter your key under Licence key and click Activate (Activate a licence).

Good to know

  • Active websites count, drafts included. Archived websites don't (Archive). The pages inside a website are not limited.
  • Exporting and backups always work, in Free too, and for archived or locked websites as well.
  • If a package ends or gets smaller, Pages deletes nothing. The oldest websites stay editable, the rest are locked: viewing and exporting still work, editing, building and publishing only once a place is free again (Website status).
  • You pay for the AI yourself. Its costs run through your Claude Code or your Anthropic account, never through the Pages licence.
  • Saved servers from WebDonkey only appear in Pages if WebDonkey has Premium. That limit belongs to WebDonkey, not to Pages.

Troubleshooting

What you see Why What to do
Free includes one website. From the Personal package on you can create more. A website is already active in Free. Archive a website or activate a package through Enter licence.
All websites of your package are in use. A larger package or an Add-on gives you more. Your package's allowance is full. Archive a website, get a larger package or an Add-on.
Publishing straight to your server is included from the Personal package on. Exporting as ZIP always works. Without a package only the ZIP export is free. Export as a ZIP or activate a package.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy