Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/airgead-investment-calculator/llms.txt

Use this file to discover all available pages before exploring further.

Airgead is a fully static site with no build step. Any host that serves static files works, but GitHub Pages is the primary target because the project uses relative paths throughout and deploys cleanly from the repository root without any additional configuration.

​
Deploy to GitHub Pages

1

Push the project to GitHub

Push the complete project directory to the default branch of your GitHub repository. Make sure the root index.html file and all subdirectories (css/, js/, pages/, assets/) are committed and present.
2

Open repository Settings

Navigate to your repository on GitHub and click the Settings tab near the top of the page.
3

Open the Pages section

In the left sidebar, select Pages under the Code and automation group.
4

Choose a deployment source

Under Build and deployment, set the source to Deploy from a branch.
5

Select branch and folder

Choose the default branch (typically main) and set the folder to / (root).
6

Save the configuration

Click Save. GitHub will queue a deployment immediately.
7

Visit the live site

After the deployment completes (usually within a minute), open your published URL. For this project the expected address is:
https://apursley2012.github.io/airgead-investment-calculator/
If you forked the repository under a different account or renamed it, substitute your GitHub username and repository name in the URL.

​
Why No Build Step

Airgead uses only vanilla HTML, CSS, and native ES module scripts. GitHub Pages serves these files directly from the repository without requiring Jekyll, npm, a CI runner, or any preprocessing step. The <script type="module"> tags the pages use are handled entirely by the browser.

​
Relative Paths

All asset references in Airgead — stylesheets, scripts, images, and inter-page links — use relative paths. Pages inside pages/ reference the shared stylesheet as ../css/styles.css and the shell component as ../js/components/shell.js. This means the site works correctly when deployed to any GitHub Pages subpath, including /airgead-investment-calculator/, without modifications.

​
Deploy to Other Static Hosts

GitHub Pages is the primary target, but the same static files can be served from any host that supports plain HTML. Netlify Drag the project folder into the Netlify drop zone at app.netlify.com, or connect your GitHub repository through the Netlify UI. Leave the build command empty and set the publish directory to / (root). Netlify will detect the index.html file and serve the site immediately. Vercel Import the GitHub repository in the Vercel dashboard. Set the framework preset to Other, leave the build command field empty, and set the output directory to . (the repository root). Vercel will deploy the files as-is. Local HTTP server (for development and testing) Because Airgead uses ES modules, it must be served over HTTP rather than opened directly as a file:// URL. From the repository root, run: 
python -m http.server 8000
Then open http://localhost:8000/ in your browser. The VS Code Live Server extension is another convenient option — open index.html and select Open with Live Server.

​
After Deployment Checklist

Once the site is live, run through these checks to confirm the deployment is complete and functional:
  • All navigation links in the header and footer resolve without 404 errors
  • Logo images load from assets/logo/ on every page
  • Calculator inputs update the live balance preview in real time
  • View Details navigates to the Results page with a populated chart and table
  • CSV export downloads a correctly formatted file
  • Saved Plans created on the Results page appear on the Saved Plans page
  • The site renders correctly at mobile viewport widths

Build docs developers (and LLMs) love

Get started for freeTalk to us