Black Hole
BLACK HOLE
 Back to Black Hole

Guide

Publishing and GitHub

A build is private until you publish it. Publishing gives the site a public address anyone can open, and connecting GitHub gives you the source code as an ordinary repository you can take anywhere. Neither step locks you in.

Publishing

  1. Open the project you want to put online.
  2. Press Publish at the top of the workspace.
  3. Confirm the project name — it becomes part of the public address.
  4. The site goes live and the link is shown to you immediately.

Republishing after further edits is the same button. The public address stays the same; only the content behind it changes. Visitors always see the last version you published, never a half-finished edit you are still working through in the chat.

Before you publish

  • Read every line of visible text. Generated copy is plausible but not always true.
  • Check phone numbers, email addresses, opening hours, and prices against reality.
  • Open the preview at phone width and confirm nothing overflows sideways.
  • Click every link and button, including the ones in the footer.
  • Confirm the page title and description read well — they are what search results show.

Invented details

If you did not give the agent a phone number, an address, or opening hours, anything that appears in those places was generated as a placeholder. Replace it before you publish.

Connecting GitHub

Connecting GitHub takes one click and an authorisation on GitHub's own screen. Black Hole never sees your GitHub password; it receives a token you can revoke at any time from your GitHub settings. Once connected, four actions are available in the workspace:

ActionWhat it does
ConnectLinks a repository to this project, creating a new one if you prefer.
PushSends the current build to the repository as a commit.
PullBrings changes made outside Black Hole back into the project.
Auto-syncPushes automatically after every successful build.

Why bother with GitHub

  • Full version history, so any change can be inspected or reverted.
  • Edit in your own editor and pull the result back into Black Hole.
  • Deploy through any host that reads a Git repository.
  • A guarantee that the code is yours and portable, whatever happens to your Black Hole account.

Deploying to your own hosting

With the repository connected, point your hosting provider at it and let their build run. Most modern hosts detect the project type automatically. Set the same environment variables your build expects, and configure your custom domain in that host's dashboard — DNS for a domain you own is managed at your registrar, not inside Black Hole.

After launch

  1. Submit the address to Google Search Console so pages start getting indexed.
  2. Check how the link previews when shared — the page title, description, and image are what appear.
  3. Keep publishing changes as you make them; there is no cost or limit on republishing.