A partially functional version of new Oengus, targeting the major static pages such as the landing page and marathon public schedule pages. There are three major checkpoints along the way to milestone 1.

Checkpoint 1
Provides a barebones site that demonstrates the chosen technology stack and provides stubs for pages forming a complete example map of the site. At this point, it'll be relatively easy to make updates to the technology stack if anything is found to be lacking or unruly at this point. Additionally, the page stubs will allow a review to be sure that all the intended pages are included and we can catch any gaps early on and the stubs will serve as a guide for later.

Checkpoint 2
Basic layout, style, and content for the main landing page and the marathon pages. At this point, stub data will be generated rather than connecting to the API to demonstrate the style. This will include the basic mobile ideas as well as it's important to begin that early rather than adding it in later.

Checkpoint 3
Connect to the API and ensure pages are being properly cached, populating the data in the fields and tables mentioned in M1C2. The main landing page and marathon schedule pages should be mostly functionally complete at this point, potentially to the point that it could serve in a production environment pending team discussion and implementation. This may not include proper mobile support depending on the state of that.