← All prototypes

Publish a prototype through GitHub

Upload your files on GitHub. This website then publishes your prototype and adds it to the homepage automatically.

You can do it in your browser. You do not need a terminal, a GitHub app or a pull request.

Open GitHub to upload →

Sign in with the GitHub account that has Kimono access. If the link shows “404” or you cannot see “Add file,” check your account or ask Titus to check your access.

Two GitHub terms, explained:
A repository is our shared project folder. Commit changes means save your upload to GitHub. Saving to main starts publishing it to this website.

Add a new prototype

  1. Prepare a folder on your computer.

    Give it a short, unique name such as new-onboarding. For a website prototype, put its index.html start page and all supporting files inside. Unzip an exported website first.

  2. Open the GitHub upload folder.

    Use the button above. It takes you straight to our shared prototypes folder.

  3. Choose “Add file” → “Upload files.”

    Drag your whole prototype folder from your computer onto the upload area. Wait for its files to finish uploading. Give each new prototype its own folder.

  4. Save with “Commit changes.”

    In the commit section, add a short description such as “Add new onboarding prototype.” Keep “Commit directly to the main branch” selected and click “Commit changes.” Confirm if GitHub asks. No review or approval is needed.

  5. Check it on this website.

    Publishing usually takes a few minutes. Return to All prototypes, refresh the page and open your prototype. Try its buttons and links, then share its link from the homepage.

Update an existing prototype

  1. Open the GitHub upload folder, then click your prototype’s existing folder.
  2. Choose Add file → Upload files. Upload the changed files and any supporting folders inside your prototype’s folder. Keep the same filenames to replace existing files. Do not put a second copy of the prototype folder inside itself.
  3. Save with Commit changes on main, just as above. Wait for publishing, then open your prototype from the homepage to check the update.

Your homepage link stays the same. Earlier published files remain available through Version history beside your prototype.

What can I publish?

Browser-ready websites and apps, multi-page HTML, images, PDFs, video, audio and downloadable files. For a single document or media file, put it in its own folder and upload that folder.

Figma, native app demos, apps with a backend and anything hosted elsewhere can appear in the list as a link.

Add a Figma or other hosted link
  1. Open the GitHub upload folder and choose Add file → Create new file.
  2. In the filename box, enter your-prototype-name/prototype.json, replacing your-prototype-name with a short, unique folder name.
  3. Paste the example below into the editor. Replace the title, description and URL with your own; keep the quotation marks and punctuation.
  4. Choose Commit changes, save directly to main, and confirm. Your link will appear on the homepage after publishing.
{
  "title": "New onboarding concept",
  "description": "A short description of what to try.",
  "url": "https://your-prototype-link"
}

The service you link to controls who can view it. Version history records changes to the link; it does not save copies of the external site.

File requirements and optional titles

Upload a ready-to-run export of your app. The publisher does not build source code or run a backend. Supporting files should use relative paths such as ./assets/image.png. Keep each file below 24 MB; use a hosted link for larger files.

More details: exports, titles, descriptions, spec links and restoring older versions →

If your update does not appear

Allow a few minutes and refresh the homepage. If it still has not appeared, open the publishing report on GitHub or ask Titus or Alek for help with your prototype’s folder name.

If an upload fails validation, its last accepted version stays live. The checks catch missing local HTML/CSS assets, but you still need to try the prototype yourself after publishing. Deleting an upload does not delete its published history.