1Name it
2Find the code
3Check the setup
4Build a preview
What are we working on?
A product is one business as your customers see it — even if it is really a website, a shop and a booking system stitched together.
Whatever you call it out loud. You can change this later.
Where does your product live?
Your website’s files sit in a project on GitHub — yours, or your developer’s. Give us the address and we will read it, work out how to run it, and build you a private copy to change.
The address of the page you land on when you open your project on GitHub.
Only projects anyone can see, for now. If yours is private, we cannot reach it
yet — connecting a private project needs a GitHub connection that is not built.
This is how we would run it
We read your project. Have a look, and correct anything that is not right — you know it better than we do.
A website
The folder holding the code for the pages people see.
The command that runs your site while you are working on it.
The number after
localhost: when you run it on your own machine.Nearly everything works on the newest. Pick an older one if something in your project refuses to install.
Run once, the first time your preview starts.
Leave empty if there is none. You can still work on the site; you just cannot publish it from here yet.
We set it to
/api, on this same address. Leave empty if your pages do not use a setting for it.An address on your service that answers when it is well. Leave empty and we will only check that it started.
One folder name, no slashes — often
dist, build, _site or public. Leave empty if this site is not one we can publish.Setting up your preview
A private copy of your site that only you can see. Every change is tried here first — your real site carries on untouched.
Your preview is ready
Ask for anything you like. You will see it here before anyone else sees it anywhere.