Build the Site Here,Put It on a Real Address

Preview builds the site and serves it exactly as a static host does, which is not what a dev server does. A dev server sends every unknown address to your home page and papers over a wrong base path. A real host does neither. So the preview will 404 on a link that the dev server renders happily, and that is the point: it is the same 404 your visitors would have got.

• A folder of HTML needs no build and no Node
• Astro, Vite, Next, Nuxt, SvelteKit, Remix and Gatsby are built for you
• Deep links behave the way they will once published
• The build output appears inline when a build fails

One button puts the running preview on a public address. No account, no token, nothing to sign up for. Send it to a client, watch them click it, change something and they see it. The link is honest about itself: it stops working when you close Plexon, and the address is different next time.

• Works with no account of any kind
• The caveat is on screen, not buried in a help page
• Add an ngrok domain in Settings to keep one address
• Closing the preview closes the link with it

Plexon creates the repository, writes the deploy file, pushes, turns on GitHub Pages, and follows the build. You are asked the two questions that actually decide whether it works, before anything is built: which repository, and whether the files are private. A private repository needs GitHub Pro or Team, and it does not make a private website: only the source stays private.

• The deploy file is shown before it is pushed
• Edit it and Plexon leaves your version alone from then on
• The progress line names the job and step in flight
• Publishing twice does not publish twice

A green build is not proof a site works. When the deploy finishes, Plexon fetches the published address and requires a real response before it tells you the site is live. If the build fails instead, the message names the job and the step, so you get "the deploy failed at build, npm run build" rather than "the workflow failed".

• Success is measured at the address, not in the build log
• A deploy waiting on a person says so, instead of spinning
• Failures name the step, not the workflow
• The run log is never copied into your chat

Three ways a static site breaks while every status stays green. An asset folder starting with an underscore that the host skips, so the page loads with no styles at all. A site built for the wrong base path, so the HTML arrives and every asset 404s. A browser-routed app with no fallback page, so every link except the home page is dead. Plexon checks for all three before it pushes.

• The underscore-folder trap that leaves a page unstyled
• A base path that does not match where the site will live
• Deep links that would 404 once published
• A credential file about to become public

Add a domain and Plexon shows the exact records to create, with the right shape for the kind of name: one record for a subdomain, eight for a bare domain, because a shortcut that works for one is invalid for the other. Then it checks, and it names the two failures that look like nothing is wrong.

• A subdomain points at your account, never at the repository
• A bare domain needs all eight address records
• A proxy in front of the domain blocks the certificate
• A certificate still being issued is not a broken one