Publish a website
Have a bot build a small site, a quiz, a survey, a lead capture page or a landing page, and put it online on your own Netlify account. Every publish waits for your approval.
Netlify is a trademark of its owner. Murage isn't affiliated with Netlify.
Build the site
The team library has a bot called Site Builder, under Build: "Small websites, from your idea to a link you can share." Add it from Bots, then tell it what the site is for and who will visit. It asks a few questions, recommends one template (a quiz, a survey, a lead capture page or a landing page), builds the pages in the project's site folder, and shows you a local preview. Before it offers to publish, it checks the mobile layout and goes over the form labels, the contrast and whether the page works from the keyboard.
Ask for changes in plain words. When the preview looks right, say publish.
Any bot can publish a folder of pages, not only Site Builder. Site Builder is the one that knows the templates and the checks.
Put it online
Step 1
Connect Netlify
The first time, a Connect Netlify card appears in the chat: Murage needs to be connected to your Netlify account to put your site online. Choose Sign in with Netlify, approve it in your browser, and come back.
If Netlify wants a token for publishing, the card says so. Choose Paste a Netlify access token instead. In Netlify, open User settings, then Applications, choose New access token, and paste it under Netlify access token. Press Connect.
Netlify access covers your whole Netlify account, so Murage keeps it private on this computer and never shows it in chat. The bot never sees it either.
You're done when: the card reads Netlify is connected. Murage can carry on.
Step 2
Check the card and publish
A card titled Publish this site? shows the Site name, the Public address and the Files count. Choose Show the files to read the full list. Anything held back is listed too: Kept private and not uploaded: .env, node_modules.
The card says Anyone with the link can see this. Read the list with that in mind, then press Publish, or Not now.
Murage uploads the files, then Checking it loads, then Live at my-shop.netlify.app.
You're done when: the card reads Live at your address, with an Open button.
Update a live site
Ask the bot for the change and it publishes again to the same address. The card is titled Update your live site? and the button is Update site. Your address does not change.
Take a site down
Open the bot's settings and find Sites this bot published. Each site has Open and Take down. Confirm with Yes, take it down. The address stops working for everyone, and the card reads Taken down. Your files stay here. You can also ask the bot in the chat. Either way, your files stay on your computer, and deleting them does not take the live site offline.
To let a bot update a Netlify site you already had before Murage, use Add an existing site under the same list. Paste the address, such as my-shop.netlify.app, or just the name, and press Add site.
Forms
The templates use Netlify Forms, so entries from a quiz or a lead capture page are stored in your Netlify project. After the first publish, turn on form detection in the project's Forms area in Netlify, then publish the site again so Netlify picks the forms up. Send one clearly labelled sample entry and check it appears in Netlify Forms. A thank-you page on its own does not prove the entry arrived.
Netlify Forms stores the entry and nothing more happens. It does not send a personalised result email or add someone to a mailing list on its own. For that, ask the bot to connect the form to your email tool. That is a separate job.
Another host, or your own domain
Murage's publish and take-down tools work with Netlify in this release. For another host, a bot on an engine that runs commands can use that host's own command-line tool or API with a key you give it, and you approve each command as it comes up. A custom domain is set up in your hosting account's own settings, not in Murage.
Limits
- An index.html must sit at the top of the folder. That is the page people see first.
- Size. Up to 500 files and 50 MB in all, with 20 MB for any one file.
- Never uploaded. Hidden files,
node_modules,.envfiles, keys and the bot's memory stay private, and the card names them. - Where the folder lives. The site folder must be inside the bot's own files, and cannot be hidden or protected.
Troubleshooting
You see
Netlify needs you to sign in again.Do this
Choose to reconnect on the publish card, finish the sign-in, then try again.
You see
Netlify did not accept that token. Check that you copied all of it, then try again.Do this
Tokens are long. Copy the whole thing from Netlify again and paste it in one go.
You see
That does not look like a Netlify access token. Copy it again from Netlify and paste it here.Do this
You pasted something else, such as a site address. Make a new token under User settings, Applications in Netlify.
You see
The site needs an index.html at the top of its folder.Do this
Ask the bot to move or rename the first page to index.html in the top of the site folder.
You see
These files are too big to publish.Do this
Make the largest files smaller, or remove some, then try again. The card names the five biggest.
You see
That address is already taken.Do this
Pick another site name, then try again. The name becomes the first part of the public address, such as my-shop in my-shop.netlify.app.
You see
Netlify is busy right now.Do this
Wait a minute, then try again.
You see
The page did not load when it was checked.Do this
The upload finished but the address did not answer yet. Wait a minute, then try again.
You see
This site was started but did not finish going up. Press Take down to clear it.Do this
Under Sites this bot published the site shows Needs attention. Press Take down to clear it, then publish again.
You see
Your browser held back the new tab. Allow it, then press Open again.Do this
Your browser blocked the pop-up. Allow pop-ups for Murage, then press Open.