Workspace /The field guideA little help along the way
FROM YOUR IDEA TO OUT THERE
A website, on your terms.
You don’t need to learn a new design tool. Start with what you want to say, and take it one step at a time.
01 / TELL YOUR STORY
Your AI chooses the direction.
Start with just your project name. In Simple mode, your AI chooses the site structure, pages, template, fonts, and colour palette from your project context. Download your AI brief, import the finished JSON and a required brand logo, then review your site. Download and publish the website, paste its public URL back into Makeway, then prepare and launch your token. The left column remembers your progress. Manual mode gives you direct editing controls for the same project.
01
Give your AI a little context.
Choose Download AI brief and give it to an AI chat that already knows your project. The file includes the content format, all the available designs and fonts, and instructions for choosing the right pages and writing useful, detailed content. Extra notes are optional.
02
Ask for content that’s actually yours.
Use the AI you already like. Tell it your story, the real features of your product, and the links you want people to visit. Leave out milestones or claims you can’t support.
03
Bring one file back.
Upload the makeway-site.json file your AI gives you. Review the preview, then apply it. The design and content update together. Add your AI’s images to the matching slots. If the JSON needs fixing, copy the repair instructions and give them to your AI.
You can make small corrections directly in the editor. Re-imports preserve artwork in matching image slots, and the top-bar undo button restores the content before your most recent import.
02 / MAKE IT YOURS
Add the part only you can bring.
In Simple mode, upload your required brand logo after importing the AI file. A separate hero image is optional. Drag and zoom in the image editor to adjust its framing before saving. Manual mode keeps these controls in Artwork. Upload your logo, hero artwork, or screenshots. Use PNG, JPG, or WebP files under 5 MB, or outlined SVG files under 1 MB. Keep your transparent logo separate from hero artwork and product screenshots. Add a short description to each image for people using screen readers.
The first assigned image after the logo fills the hero, and the rest become a gallery. In Manual mode, use the arrows on each slot to change which is which. Without an image, the page uses a simple decorative illustration.
Your AI can use a preset palette or create a custom theme with hex colours for backgrounds, text, accents, borders, panels, and button text. Makeway checks those colours for readable contrast and applies them throughout the preview and exported pages. You do not need to choose a style in Simple mode. For direct control, open Manual mode and use Appearance to adjust colours, fonts, or templates. Try each template with your real content. Every template accepts the same content and arranges it differently, so switching is free — your words and artwork carry over. Keep the recommended-style checkbox checked to try each template’s font and colour pairing, or uncheck it to retain your current styling. Apply recommended style restores the selected template’s font and colour defaults.
Use the desktop and mobile preview buttons. Check long headlines, image cropping, button links, and optional sections before exporting.
03 / PUT IT OUT THERE
Download it. Give it a home.
Choose Export website, then Download website ZIP. Your download is a standalone site with your assigned images, selected fonts and licences, a content file, and a short README. The ordinary static export needs no Makeway login or backend. If you enable live admin, follow the separate Netlify admin instructions below. The static deployment steps in this section do not apply to that export.
The fast way — no Git, about a minute
Netlify hosts the ZIP exactly as it is. You do not unzip it, and there is nothing to configure.
01
Open Netlify Drop.
Sign up or sign in to Netlify first. Then open Netlify Drop.
Use the file you just downloaded. It is live within seconds at an address like your-name.netlify.app.
03
Make it public and copy the link.
When deployment finishes, click Make public if needed. Open the published website and copy its URL from the address bar. Back in Makeway, paste it into the live website URL field. Check the link in a private browser window without a Netlify login.
The lasting way — with Git
Choose this when you would rather push a change than drag a folder, and you want updates to deploy themselves.
01
Extract and review.
Open the ZIP and find index.html. Check the site locally and keep a copy of the files.
02
Put the files in your own repository.
Create a GitHub repository and upload the extracted contents. Keep index.html at the root, alongside assets and fonts — not inside an extra folder.
Choose Other as the framework, leave the build command empty, and use the root directory (.) for output. The export already contains a configuration file with those settings. No environment variables are needed.
Open the production link and check the site on desktop and mobile, including your real links and any contract address.
Cloudflare Pages and GitHub Pages will host this export just as happily — nothing in your download is tied to one provider. Opening a provider or entering a website URL in Makeway doesn’t deploy or verify your site. Choose a plan that suits your project and check the provider’s current terms.
OPTIONAL / LIVE CONTRACT ADDRESS
Add your CA after launch.
In Token settings, enable Include live admin in my export, enter and confirm a password, then save it. The next ZIP contains /admin and a small Netlify backend. Only a salted password verifier goes into the server files; your plaintext password is not saved or exported.
01
Unzip your download
Open the extracted folder to see your website files.
Show instructions
Download the Netlify admin ZIP from Makeway, then extract it on your computer. Open the extracted folder to see the website files.
02
Create a new GitHub repository
Sign in. Name it, select Private, then Create repository.
Show instructions
Sign in to GitHub, give your website its own repository name, select Private, and choose Create repository.
Choose uploading an existing file. Drag everything INSIDE the extracted folder into GitHub together. Click Commit changes.
Show instructions
In your new repository, open uploading an existing file (or Add file → Upload files). On your computer, open the extracted folder and press Command+A on Mac or Ctrl+A on Windows to select everything INSIDE it. Drag those selected files and folders together into GitHub’s upload area. Use drag and drop for this step so the folders are included too; skip the choose your files button. Do not drag the ZIP or its outer folder. Wait for every file to upload, then choose Commit changes.
04
Sign up to Netlify and import from GitHub
Add new project → Import an existing project → GitHub. Select your new repository and deploy.
Show instructions
Sign up or sign in to Netlify. Once the files are saved on GitHub, open your Netlify dashboard. Choose Add new project → Import an existing project → GitHub. Allow access to your new private repository, select it, and deploy with the included settings below.
Before opening Netlify, check the top level of your GitHub repository: public/, server/, netlify/, package.json, and netlify.toml should be visible together. If you must open another folder to find them, the upload is one level too deep. Move the contents to the repository’s top level first.
Build command: npm run build. Publish directory: public. Functions directory: netlify/functions. Leave the base directory empty. Publish only public, so server files stay private.
After deployment, open /admin/ on your live website and use the password you saved in Makeway. Use this GitHub-to-Netlify route for the admin export.
Once your token launches, open /admin/ on the published site, enter your builder password, paste the confirmed CA and save. New page loads use the saved address; open pages refresh it within 30 seconds.
This version needs a Netlify Git or CLI deployment, not Netlify Drop or the static Vercel route. CLI instructions are included in the downloaded README. Your Netlify account’s current storage and function limits apply.
To replace a forgotten password, set another in Makeway and redeploy a new export to the same Netlify site. Your saved CA remains in site-wide storage. Website copy and design changes still require an export and deployment.
04 / YOUR OWN ADDRESS
A name people can come back to.
Buy the domain in your own registrar account, so it stays yours whatever happens to your host. Compare the renewal price as well as the first-year price — the first year is often a discount that does not last.
Then add it in whichever host you chose. Netlify and Vercel both have a Domains page that shows the exact DNS records for your project. Enter those at your registrar, keep unrelated records such as email settings, and check HTTPS on both the root domain and www once it is confirmed.
Edit your project, download a fresh export, and replace the files in the same repository. Your production branch can redeploy through Vercel. Check the resulting website yourself.
Saving in Makeway doesn’t change your already hosted page. With live admin enabled and deployed, CA updates through the live /admin page are saved directly without redeploying. If you’ve edited the exported source yourself, back up those edits and merge new files manually. Makeway won’t overwrite or merge your external source for you.
Projects currently save in this browser, on this device. Keep exports and original artwork as backups. GitHub sign-in and cloud sync are planned for the account-connected release.
Your website first. Your token next.
Prepare your token, publish your website, then use Launch your token for a Pons launch on Robinhood Chain. Already have a token is a secondary option. Your AI supplies five ranked ticker ideas, with the top choice selected and a dropdown or manual override. ETH is the default pair; approved stock-token pairs are available. When launching is enabled, connect your wallet, approve publishing the logo you already uploaded, review the fees and 80/20 creator earnings split, then sign the fee-contract deployment and token launch separately. Approve the free listing signature before the token transaction. Confirmed launches appear automatically in Explore and My launches, even if you close this browser. Website drafts and artwork still stay in this browser. Save the recovery JSON. A timeout is not a failed launch: check its receipt before retrying. Confirmed launches add the CA to your local draft; publish a new ZIP or update your live admin to show it online. Website creation, exporting, and updates never create a token by themselves.
