Buy

Publish

Free & Premium

Publish at the top right of the title bar of an open website opens the Publish website dialog. There you choose how the website goes online: as a ZIP you upload to your host yourself, or straight to a server via SFTP. At the very bottom you can also back up the whole website as a file.

What you do here

Access, web folder, saved servers, fingerprint and setting up a server of your own are covered in the Server chapter.

Layout of the dialog

  1. How to publish? with the two routes ZIP for your host and Upload to a server. With a Pages package and an active website, the server is preselected, otherwise the ZIP. Every time you open the dialog, this preselection applies again.
  2. Before publishing, still missing: with everything that is still missing, if anything is. If the last check is red, its summary follows below (What must be ready first).
  3. The chosen route: the settings for the ZIP or the form for the server.
  4. Or export as a backup with the Export backup button. It saves the whole website with data, design, all photos and history to your Downloads folder. Use Import website to bring it back, also on another Mac (Export a backup). The password for your server is not included.

While you choose the web folder on the server or manage the servers in WebDonkey, the dialog shows only that view, without the choice at the top and without the backup.

Principles

  • Only a version that passed the full check with Lighthouse and has nothing missing goes onto a server.
  • Pages doesn't delete files on the server that it didn't create itself. It only moves existing files into a hidden backup folder with your consent.
  • Archived and locked websites can't be uploaded to a server. The ZIP and the backup always work.

Free and Premium

Free from the Personal package on
ZIP for your host yes, with the "Built with WebDonkey Pages" link in the footer yes, without the link
Upload to a server no yes
Export backup yes yes

Packages and prices are at webdonkey.io/pricing.

What must be ready first Free

Before a website goes online, it needs complete details for the legal notice and privacy policy and a version that passed all checks. The Publish website dialog shows at the top what is still missing. When uploading to a server, Pages runs a full check itself beforehand.

Where to find it

Click Publish in the title bar. If something is missing, a yellow box Before publishing, still missing: sits at the top of the dialog.

What the list can contain

  • every open question from the facts, word for word, for example about a missing address,
  • The domain,
  • The host for the privacy policy,
  • Your confirmation that the legal pages are correct.

Below it: Everything can be added in the chat or under "Facts". If the last check is red, its summary follows below the list in a red box.

The list doesn't name everything: missing required details of your business, missing translations or a missing browser for the checks show on the Checks tab (Reading the result).

How to do it

  1. Read the list in the dialog and close it.
  2. Open the Menu on the right, Facts tab. Under For publishing, enter the Domain and the Host (for the privacy policy) (Domain and host). Open questions sit right at their field; you answer the rest in the chat.
  3. Under Legal notice and privacy, read both pages and tick I have read the legal notice and privacy policy and the details are correct. (Confirm the legal pages).
  4. Switch to the Checks tab and click Check now. If anything stays red or yellow, fix it in the chat or under Facts.
  5. Open Publish again. Once the yellow box is gone, you are good to go.

The full check before uploading

The Upload to a server route has a fixed rule: Pages only uploads a version whose last check was a full check with Lighthouse, after which nothing changed, and which has no red and no yellow part.

When you click Check and publish, Pages first connects briefly to the server, so a wrong password doesn't only show up after the check. If the version isn't cleared yet, Pages then runs the full check ("Full check before publishing", usually one to two minutes). If anything is still open afterwards, it uploads nothing and reports Not ready to publish yet: … with the reason, for example the summary of the check.

The ZIP for your host route needs no full check, and yellow parts don't hold up the export. Still check the list and the Checks tab before uploading: if details are missing, the legal notice of the exported website shows visible placeholders (Export as ZIP).

Troubleshooting

What you see Why What to do
Not ready to publish yet: Technically fine. Still missing before publishing: … Yellow parts, for example Open facts, Legal notice and privacy policy or Languages. Add what the Checks tab names and start again.
Not ready to publish yet: with findings The full check found red parts, for example in Lighthouse. Have the findings fixed in the chat (Full check with Lighthouse).
The yellow box is gone, but the check is still yellow. The list doesn't name every required detail. Look on the Checks tab under Legal notice and privacy policy.

See also

Export as ZIP Free & Premium

The ZIP export always works: in Free and with every package, for archived and locked websites too. You get the finished website with instructions as a ZIP file and upload it to your host's web folder yourself, for example through its file manager or an FTP client.

Where to find it

Click Publish in the title bar and choose the ZIP for your host route under How to publish?. In Free and for archived or locked websites, it is already preselected.

How to do it

  1. Open the website and click Publish.
  2. Choose ZIP for your host.
  3. Under Language of the instructions in the ZIP, choose the language of the instructions.
  4. Click Export ZIP.
  5. Pages saves the file to your Downloads folder, reveals it in Finder and names the location in the dialog under Saved:.
  6. Unpack the ZIP and upload everything from the website folder into your host's web folder. The steps are in the instructions inside the ZIP.

Fields and buttons

Element Meaning
Language of the instructions in the ZIP Language of the ANLEITUNG.txt file. You can choose every language Pages has instructions for, each under its own name, such as Deutsch, English or Français. Preselected is the interface language, or English if it isn't available. The language of the website doesn't change.
Export ZIP Active as soon as there is a built version and Pages isn't working on the website.
Full check with Lighthouse Sits next to it as long as the last check wasn't a full check. The export doesn't need it (Full check with Lighthouse).

The file is named after the website's folder, for example bakery-miller.zip. If a ZIP with that name is already in your Downloads folder, Pages replaces it.

What's in the ZIP

  • website folder: everything that belongs in your host's web folder (document root), hidden files such as .htaccess included. The .htaccess redirects visitors to HTTPS.
  • .kontaktformular.php in the website folder, if the website has a contact form and domain and email address are set under Facts. It holds recipient and sender, so the form sends right after uploading without further setup.
  • ANLEITUNG.txt with the steps: upload all files, including the hidden ones (in Finder, ⇧⌘. shows them), switch on SSL or HTTPS at your host, and PHP at your host for the contact form. It also contains a template for a .env file one level above the web folder, in case you want to set the form's addresses by hand. Such a .env takes precedence.

Which version goes into the ZIP

The export contains the version the preview shows: the latest one that passed the check without red findings. If something has changed since the last check, for example under Facts, Pages builds and checks again before exporting. Photos that no page shows are left out.

Yellow check parts don't hold up the export. If details for the legal notice or privacy policy are missing, the exported website shows visible placeholders there. So check What must be ready first beforehand.

The contact form

The form needs PHP at your host. Enquiries go to Recipient of enquiries under Facts, Contact form; without an entry, to the email address under Business. The sender is the Website sender if it belongs to the domain, otherwise noreply@ with your domain. If domain or email address are missing, the instructions say so: enter them under Facts and export again, or create the .env from the template.

Free: the footer link

In Free, the footer of every page of the exported website carries the link "Built with WebDonkey Pages" to webdonkey.io, in the language of that page, on German pages for example "Gebaut mit WebDonkey Pages". The dialog says In Free the exported website carries the link "Built with WebDonkey Pages" in its footer. From the Personal package on it is left out.

It is a plain text link without any script and doesn't affect loading time. The preview and the local test in WebDonkey don't show it.

Troubleshooting

What you see Why What to do
Export ZIP is greyed out. There is no built version yet, or Pages is working. Wait until the build or the check is finished.
Pages or images are missing online, or the website looks different from the preview. Not all files arrived in the web folder. Upload the content of website completely, including the hidden files .htaccess and .kontaktformular.php.
The contact form shows an error when sending. PHP is missing at the host, or recipient and sender are missing. Turn on PHP at your host, enter domain and email address under Facts and export again.
The website is only reachable over http. SSL isn't switched on at the host yet. Switch on SSL in your host's control panel.

See also

Upload to a server Premium

From the Personal package on, Pages uploads the website via SFTP into the web folder at your host or on your own server. SFTP is the encrypted file transfer almost every host offers. Pages fully checks the website first; only a cleared version goes online. From the second time on, Pages only transfers what has changed.

Where to find it

Click Publish in the title bar and choose the Upload to a server route under How to publish?. With a Pages package it is preselected. Without a package, it says Publishing straight to your server is included from the Personal package on. Exporting as ZIP always works. with the Enter licence button.

How to do it

  1. Open the website and click Publish.
  2. Choose Upload to a server.
  3. Enter the access: Server, Port, User, the Sign-in with Password or SSH key (Server access). If Pages is connected to WebDonkey, you can pick a server saved there instead (Saved servers from WebDonkey).
  4. Enter the Web folder on the server or pick it with Browse … (Choose the web folder).
  5. If you like, check access and web folder with Test connection without uploading anything (Test connection). If Pages doesn't know the server yet, you first confirm its fingerprint.
  6. Click Check and publish. The button is active as soon as server, user, password or key and web folder are filled in.
  7. Pages connects to the server, runs the full check if needed (usually one to two minutes) and uploads the website. A bar shows the progress; the title bar shows Publishing ….
  8. At the end it says Published: … files are online. with a link to your domain. In the overview, the website shows the status Published (Website status).

You can close the dialog meanwhile; the upload keeps running. If you want to quit Pages, it asks first (Question when quitting).

Fields and options

All access fields are explained in Server access. On this page, these matter most:

Element Meaning
Remember password encrypted on this Mac On by default. With key sign-in it reads Remember passphrase encrypted on this Mac. Once one is saved, the field is called Password (saved, leave empty).
Checkbox The web folder contains … other files. Pages moves them into a hidden backup folder before uploading. Only appears when other files already sit in the web folder, with the list of files. See below.
Check and publish Starts connection, full check and upload. Below it: The full check with Lighthouse takes one to two minutes.

What happens during the upload

  • Only what changed: Pages creates the hidden file .wdp-manifest.json in the web folder. It lists every file Pages put there, with a checksum. Next time Pages only uploads new and changed files and reports, for example, 12 files uploaded as new or changed, 230 were already up to date.
  • Replacing without gaps: every file first goes onto the server under a temporary name and then replaces the old one. Visitors never see a half-written file. If a run is cut off, the next one cleans up the leftovers.
  • Cleaning up: Pages only deletes files it created itself and that are missing from the new version, for example the page you removed. Photos that no page shows any more go too.
  • Other files: if other files already sit in the web folder the first time, for example an old website, Pages stops and reports The web folder already contains … other files, for example an old website. Pages can move them into a hidden backup folder: agree below or choose an empty folder. If you tick the box and click Check and publish again, Pages moves them into a .wdp-alt- folder with date and time inside the web folder. Hidden entries such as .well-known stay, unless Pages brings a file of the same name, such as .htaccess.
  • Another website from Pages: if the web folder already holds another website published with Pages, Pages asks the same way and doesn't overwrite it without asking.
  • Your consent only applies to this case: to this server, this folder and exactly the list shown. If you change something about the access or files are added, Pages asks again.
  • Root and login folder: Pages only publishes into the server's root or your login folder if nothing foreign sits there apart from hidden entries. Otherwise create a subfolder with Browse ….
  • Recognising your website: Pages recognises its own website on the server and updates it without asking, even if you imported it, it comes from another Mac or you uploaded it as a ZIP before.
  • Contact form: if the website has a contact form and domain and recipient are set, Pages creates the .env file one level above the web folder with recipient, sender and the website's address. If Pages created it for this website before, it brings it up to date with the current facts. A .env you created yourself stays unchanged. If it belongs to another website from Pages, Pages leaves it alone as well and suggests a folder of its own for this website, for example html/ with your domain and /public after it.
  • A look at the domain: finally, Pages calls https:// with your domain. If the new site isn't visible there yet, it says The new site is not visible under the domain yet. Check that the domain points to this folder.

Archived or locked

If the website is archived or exceeds the allowance of your package, the form is replaced by This website is archived or exceeds the allowance of your package. Publishing works again once it is active. Exporting as ZIP always works.

Free and Premium

Uploading to a server is included from the Personal package on. In Free you export the website as a ZIP. Packages are at webdonkey.io/pricing.

Troubleshooting

What you see What to do
Not ready to publish yet: … Fix what follows (What must be ready first).
The folder … is the root of the server or your login folder, … Under Browse …, create a subfolder for the website and choose it.
The settings for the contact form (.env) could not be created. The form only sends once they exist. Check whether your user may write to the folder above the web folder, and publish again.
The note that the new site isn't visible under the domain yet Check in your host's control panel which folder the domain points to.
Access, web folder, server All messages are listed under Common messages.

See also

Question when quitting Premium

If Pages is uploading a website to your server or setting up a server, quitting would cut the run off halfway. That is why Pages asks first, whichever way you try to close the app. You decide whether Pages keeps working or quits anyway.

When Pages asks

Pages only asks while one of these two runs is active:

The question comes up on every way out: closing the window, ⌘Q, Quit in the Dock and logging out of your Mac. Pages doesn't ask during a chat, a check or a build. The restart after an update doesn't ask either.

The question

Pages brings its window to the front and shows the question Pages is still working on your server. The text depends on the run:

  • While uploading: Pages is publishing a website right now. If you quit, the upload stops halfway and the website stays partly updated until you publish it again.
  • While setting up: Pages is setting up a server right now. If you quit, the setup stops halfway. You can start it again later.
Button What happens
Keep running The question closes and Pages keeps working. Afterwards you can quit in peace.
Quit anyway Pages quits immediately and cuts the run off.

If you press ⌘Q again while the question is open, no second one appears.

After "Quit anyway"

  • Interrupted upload: some files on the server are already in the new version, the rest in the old one. Publish the website again after the next start. Pages cleans up the leftovers of the interrupted run and uploads whatever is still missing.
  • Interrupted setup: start it again: click Test connection and start the setup once more under Prepare server. The setup can be repeated; a second run doesn't break anything.

Free and Premium

Both runs are included from the Personal package on, so you only meet the question with a Pages 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