Skip to content

Run 4: Go Live

Where You Left Off

In Run 3, your project context file changed everything. AI knew your project from the first word of every conversation, and you used that speed to build ambitious features — snowpack data, condition-specific recommendations, and whatever your team chose to push toward. Your Field Guide went from displaying real data to being genuinely useful.

Then in Lift 4, you zoomed out. You learned what deployment means — moving your Field Guide from your private workspace to a live URL that anyone can visit. You saw that your save-and-sync habit has been building toward this moment all along, that the deployment pipeline is already set up, and that going live is one prompt away. You ran the pre-flight check and made a game plan for this final sprint.

You also learned some important truths about AI-built software: the two-week cliff (things break when they interact), the validation gap (AI says it's done before you've verified it works), and why authoritative data sources matter more than AI-generated explanations. Those aren't reasons to hold back — they're reasons to ship thoughtfully.

This is it. Your final sprint. Time to ship.

The Challenge

Deploy your Avalanche Field Guide to a live URL. Then polish, fix, and add that final touch. By the end of this run, your Field Guide should be live — a real application, accessible to anyone with a browser, built by a team that had never written code before today.

This is the run where your workshop project becomes a real product. Deploy first, then iterate.

Baseline Capabilities

  • Your Field Guide is deployed to a live URL — tell your AI coding assistant to deploy the project and get back a working URL that anyone can visit from any device
  • Fix any issues from the pre-flight check — if something was broken or outdated when you checked in Lift 4, fix it now
  • At least one final improvement — polish an existing feature, add something new, or improve the experience based on what you wish the Field Guide had
  • Your live version reflects your latest work — save, sync, and redeploy so the live URL shows everything you've built, not an earlier version

Stretch Goals

  • Mobile-friendly — test your live URL on a phone and make sure it looks good on a small screen (tell your AI coding assistant to make the layout responsive if it isn't already)
  • About page — add a section that explains what the Field Guide is, who built it, and where the data comes from — give your creation a proper introduction
  • "Last updated" timestamp — show when the data was last refreshed so users know they're looking at current conditions, not stale information
  • Share it — text the live URL to a friend or family member who skis and ask what they think — that's the ultimate test of whether what you built is useful

Tips

  • Deploy first, improve second. Don't try to perfect everything before you deploy. Get the URL, confirm it works, then use the remaining time to polish. You can redeploy as many times as you want — every save-and-sync followed by a deploy updates the live version.
  • Use the game plan you made in Lift 4. Your team already discussed what to tackle first. Stick to the plan — or adjust it now that you're in the sprint.
  • Test the live URL, not just the workspace preview. Your workspace preview and the deployed version should look the same, but always check the real URL. Open it in a new browser window or on a teammate's phone. Check the things that matter most: Does the danger rating show today's real data? Do the pages and navigation work? Does the condition-specific advice match the current danger level? These are your acceptance criteria from earlier runs — they should still pass on the live version.
  • If something goes wrong, don't panic. If deployment fails, ask your AI assistant: "The deployment failed. What went wrong and how do we fix it?" If the live URL looks different from your workspace preview, try redeploying — sometimes changes need a fresh deploy to show up. If a feature that worked in your workspace is broken on the live URL, save and sync first to make sure your latest code is pushed, then redeploy.
  • Save, sync, and redeploy after each change. This is the same habit you've been building — just with one extra step. Make a change, verify it in the workspace, save and sync, then redeploy.