Overview

Why does this exist?

  • Listing of data (rosters) should be dynamic for current and future use

  • Users should have ability to define their own content via forms

  • Data should not be hard-coded. Data should not be hard-coded. Repeat.

Goals

  • Build and design the Astro front-end framework

  • Learn dynamic web templating concepts via Astro

    • components and sub components

    • nested and inherited layouts

    • props and dynamic data

  • Load internal and external data -- dynamically

  • Use both public and private API data sources

  • Programmatically create a listing (roster) of information

  • Practice process of creating an MVP (minimal viable project) or proof of concept before investing in version 1.0

PreviousClass Roster APINextIn Class Example

Last updated