Settings
FreeSettings decide how Pages works: which AI access it uses, which licence and which colours. They also show the state of updates, the tools Pages found on your Mac and the open-source licences. Settings for a single website don't live here but under Edit website.
Where to find it
Click the gear on the right of the title bar. You get back through All websites in the title bar or WebDonkey Pages on the far left.
What you do here
- AI access: choose Claude Code or an Anthropic API key.
- Licence: enter a key, see your package and usage.
- Themes: pick the colours of Pages, create your own themes, use the gallery.
- Updates: ask for a new version and open the changelog.
- Technology: see which kit, Node.js and browser Pages uses.
- Legal: view the open-source licences.
- Language: how Pages picks its language. There is no setting of its own for it.
Page layout
The sections from top to bottom:
- AI access: the cards My Claude Code and Anthropic API key, below them the API key field.
- Licence: state, package, usage, key and the licence buttons.
- Appearance: Built in, Presets and Your themes, below them the theme editor when needed.
- Themes from WebDonkey: only if Pages is connected to WebDonkey and you have your own themes there.
- Submit to the gallery: share your own themes, plus My submissions.
- Theme gallery: load other people's themes and take them over.
- Updates: state, What's new and Check now.
- Technology: Pages kit, Node.js, Browser for checks, Claude Code and Websites folder.
- Legal and open source: View open-source licences.
Free and Premium
Every setting works without a licence. Only submitting your own themes to the gallery needs a Pages package (Submit to the gallery).
AI access Free
Pages builds websites with Claude. Under AI access you choose how Pages reaches Claude: your Claude Code on this Mac or an Anthropic API key. This applies to every website without its own access. AI costs run through this access, never through the Pages licence.
Where to find it
Settings › AI access, the first section of the page. If an access is missing, Set up now in the chat also leads here.
How to do it
Use Claude Code
- Install Claude Code on this Mac and sign in there.
- Click the My Claude Code card. A check mark shows that it applies.
Store an API key
- Create an API key in the Anthropic console and copy it.
- Paste it into API key.
- Click Check and save. Pages tests the key with Anthropic and switches the route to the API key at the same time.
- On success it says The key works and is stored encrypted. Otherwise the message gives the reason.
Fields and options
| Element | Meaning |
|---|---|
| My Claude Code card | Uses your signed-in Claude Code on this Mac. Pages only gives it its own tools, nothing else. If Claude Code is missing, the card says Claude Code is not installed on this Mac. |
| Anthropic API key card | Uses a key from the Anthropic console, costs are billed to your Anthropic account. If one is stored, the card says A key is stored. |
| API key | Field for a new key. A stored key is never shown, the field then only shows dots as a placeholder. |
| Check and save | tests the key in the field, stores it and makes the API key the active route |
| Remove | deletes the stored key at once, without asking. Only appears when a key is stored. |
Clicking a card makes it the active route, even if it still lacks something. Its text then turns yellow. If you have never chosen, Pages uses Claude Code when it is installed, and the API key otherwise.
Each website's own access
Each website can have its own access: Claude Code or Claude API with its own key, for example your client's. You set it when creating the website or under Edit website. As in Settings follows this section.
The status bar shows which access applies right now: AI via Claude Code or AI via API key. Hover over it and it says AI access from Settings or This website's own AI access.
What happens in the background
- Pages stores API keys encrypted on this Mac, in the Pages app folder. A key never goes into a website's folder, an export or a backup, and is only sent to Anthropic.
- With Claude Code, Pages works through your installed Claude Code and its own sign-in. Pages stores nothing for that.
- To test a key, Pages starts the Pages kit. Without the kit and Node.js, a key can't be checked.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| The chat needs access to an AI. in the chat | The active route has no key, or Claude Code is missing. | Store a key or install Claude Code. |
| An error message after Check and save | Anthropic rejected the key, or there is no connection. | Check the key in the Anthropic console and your internet connection. |
| The Pages kit is not installed. or Node.js is missing on this Mac (22.12 or newer). | Without the kit and Node.js, Pages can't test the key. | See Requirements. |
| Claude Code is installed, but the card still reports it missing. | Pages looks for Claude Code in fixed places and in your terminal's search path. | Restart Pages. Technology shows the location found. |
See also
Technology Free
The Technology section shows what Pages works with on this Mac: the Pages kit, Node.js, the browser for the checks, Claude Code and your websites folder. It tells you at a glance whether everything is there, and where Pages found it.
Where to find it
Settings › Technology, just before Legal and open source.
The rows
| Row | Content |
|---|---|
| Pages kit | Version of the kit and, in brackets, where it comes from. In the shipped app it says bundled. If you start Pages with the environment variable WDP_KIT_DIR, it says environment. |
| Node.js | Version and location of the Node.js Pages uses, for example v22.12.0 · /opt/homebrew/bin/node. It has to be version 22.12 or later. |
| Browser for checks | location of Google Chrome, Chromium or Microsoft Edge |
| Claude Code | location of Claude Code, if installed |
| Websites folder | where your websites live, the WebDonkey Pages folder in your home folder |
If something is missing, the row says missing. If the kit, Node.js or the browser is missing, a sentence in warning colour below says what is needed, for example Node.js 22.12 or newer is needed. The same sentences appear in the Your websites overview under Pages is not ready yet:.
What happens in the background
- Pages looks for the kit first in a folder from
WDP_KIT_DIR, then inside the app itself. - Apps started from Finder don't see your terminal's search path. That's why Pages looks for Node.js and Claude Code in the usual places and finally asks your terminal's shell. The places are listed under Requirements.
- Pages looks for the browser in the Applications folder, and for Google Chrome also in the Applications folder in your home folder.
- A missing Claude Code is not an error as long as you work with an API key. That's why it isn't in the list of missing parts.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| Node.js says missing although Node is installed. | The version is older than 22.12, or Node lives in an unusual place. | Install Node.js 22.12 or later in a usual place and restart Pages. |
| Pages kit says missing. | The app is incomplete, or WDP_KIT_DIR points to a folder without a valid kit. |
Reinstall Pages or start it without the environment variable. |
| Browser for checks says missing. | No Chromium browser in Applications | Install Google Chrome, Chromium or Microsoft Edge. |
See also
Language Free
Pages comes in 16 languages. It has no setting of its own for this: it speaks your Mac's language, and when it is connected to WebDonkey, WebDonkey's language. The languages of your websites are independent of it.
The interface languages
English, German, Danish, Dutch, Dutch (Belgium), French, French (Belgium), Italian, Spanish, Czech, Polish, Russian, Ukrainian, Japanese, Chinese and Korean.
How Pages picks the language
- Without WebDonkey, Pages goes through your Mac's list of preferred languages (in System Settings under “Language & Region”) and takes the first one it knows. If none matches exactly, the base language is enough, so Austrian German becomes German. If Pages knows none of them, it speaks English.
- With WebDonkey, Pages takes the language set in WebDonkey, as long as it is one of the 16. If you change it in WebDonkey, Pages follows at the latest on its next start.
- If a single text is missing in a language, the English one stands in. The Belgian variants use French or Dutch for everything they don't have themselves.
What follows the app language
- the interface itself, with every button, notice and error message
- the checks with their parts, summary and findings
- the working steps in the chat and the notice when Pages has discarded a change
- the messages during a takeover, while publishing and while setting up a server
- the question when you quit while Pages is writing to a server, and the titles of the file dialogs
- the default for Language of the instructions in the ZIP in the ZIP export
These texts from the Pages kit exist in 14 languages, the Belgian variants use French and Dutch. If a language is missing, Pages uses English. A check result stays in the language it was created in until Pages checks again.
What only knows German and English
- The Docs appear in German when Pages speaks German, and in English otherwise.
- The release notes in the update notice and in the Changelog come in German or English the same way.
- The texts in the dialog for agreeing to new terms before an update come from the shop in German or English (Consent to terms).
Your website's languages
You choose the languages your website appears in per website, when creating it or under Edit website. There are 26 to choose from. The AI writes the website's texts in those languages, whatever language Pages speaks and whatever language you write to it in.