How to publish an HTML app
A practical guide to publishing HTML with GemiGo: paste your code, publish the app, check the public link, and update it when your content changes.
What you need
Use HTML content that runs in a browser. A self-contained HTML page is a convenient starting point for an interactive lesson, game, calculator or demo. If it depends on separate local files, package the files as a ZIP instead.
1. Paste your HTML
Open Publish an app, choose HTML, and paste the HTML into the code input. Sign in when the publishing flow asks you to. Review any external scripts and API calls before publishing.
2. Publish and check the result
Start publishing and follow the deployment status. Once it succeeds, open the resulting website URL in another browser tab and check the app’s controls, images and mobile layout. A successful upload is not proof that every external dependency works.
3. Share or update the app
Share the resulting link with your audience. To publish a change, open the app in your dashboard and use its project settings to redeploy. Public discovery is a separate setting; an unlisted app can still be opened by anyone with its deployed URL.
Why does my page fail after publishing?
Check browser errors, missing assets and unavailable external APIs. Local filesystem paths do not become public URLs. Never put private API keys into HTML or client-side JavaScript. Use the project’s latest deployment result when diagnosing a failed release.
Try it: a small addition activity
This example was written by GemiGo. It runs offline, checks answers and generates another question without external APIs. Try it in your browser, then download and publish it through the matching input. It demonstrates the publishing workflow; it does not claim a learning outcome.
How do I paste this HTML?
Open addition.html in a text editor and copy everything from <!doctype html> to </html> into the HTML publishing input. Styles and scripts are already inside this file. After publishing, enter 5 and press Check: the first question should say Correct. New question should change the exercise.
Images, styles or scripts do not load?
Open the asset URL directly. A 404 usually means the archive path or filename does not match the reference. C:\, /Users/ and file:// are local filesystem paths, not published image addresses. If assets load but the page stays blank, inspect the browser console: an external API may reject cross-origin requests or require sign-in. Remove private credentials before uploading.
What about React or Vite source code?
For a ready-built site, run your project’s build command locally and zip the output files—for example, put index.html and assets/ from inside dist/ at the archive root. For source publishing, include package.json, dependency declarations, source files and required configuration so a supported build can produce static output. If only deep links fail, check application routing and the asset base path.