# Milestone v1.0: Page Setup and Publishing Flow
We have a marketing pro named Max on the team. He needs to be able to arrange, publish, and update new pages to the website without breaking what's online today.

## Relevant Architectures
Today, we have three avenues for publishing web changes:
1. Updates to the React SPA are published by triggering a Jenkins workflow. High-security endpoint. Max does not have access to this, and shouldn't need it.
2. Much of the website is currently served by Builder.io. The React SPA has routing entries for the name of each and every dedicated Builder.io page.
  - If we add a new page, we currently must deploy from Jenkins (new URL routing via React) AND publish the page in Builder.io
  - If we update an existing page, it's easier: Just publish the updates on Builder.io
3. Shopify: We have a Shopify storefront at `store.bigscreenvr.com`. Its backend is wholly different from our main website, but Builder.io serves the public-facing pages for both parts of the website. For Shopify, Builder.io publishes updates to certain Shopify templates. We also have some other custom templates on Shopify, such as the blog.

We also have Arda, our admin portal. It doesn't do much with the website today, but it could be useful for these tasks. More info can be learned from the adjacent projects `cloud` (Arda source code + deeper web backend is here) and `bigstack`, an LLM toolkit for working with the `cloud` repo.

## Goals
- Max should be able to upload and update raw webpages (html, css, js, assets) without accessing Jenkins or Builder.io
  - Those webpages would live in one or more separate repositories. They could perhaps have some sort of `bigscreenvr.com` deployment manifest at their root.
- Max should be able to arrange and deploy new URLs for said webpages without accessing Jenkins or Builder.io
  - This goal and the previous are not necessarily mutually exclusive. If they can be wrapped up into one succinct step/LLM-lead process from Max's perspective, that would be a win.

First target: the adjacent project called `bigscreen10`. This is a finished webpage that is fully ready to be deployed to `https://www.bigscreenvr.com/10years`

A GUI for these tasks is not particularly necessary. Max also has LLMs to help him achieve his goals. So long as the foundation is laid by our work, he can collaborate with agents to achieve these goals.

## The Task at Hand
We must plan and deploy a framework which enables the goals above to be achieved on a repeating basis. The output must include the instructions (i.e. in CLAUDE.md) necessary for an LLM to perform a deployment at Max's behest.

The milestone is a success when we have:
1. Uploaded and deployed the `/10years` page without its content being present in a Jenkins deployment, and
2. Performed and deployed a test mutation to the `/10years` page without needing Builder.io or Jenkins.