Build and Deployment Continuity, blocked by #8

As a site builder, I need a way to ensure continuity in build and deployment of the page when the source content changes, in so the dynamic data from the content API is turned into a static artifact, which publishes at less expenses.

The site is currently built as an Astro template feeding from a Ghost API, which was our last iteration, starting to make use of the new shiny MDX world.

We have since come to implement the #6 (closed) domain model and its #4 (closed) content within a Directus API at the very same location content.ecobytes.net. This needs to be adapted at first, before we can continue here.

• The page builds locally with contents from the Directus API. #8 (closed)

Then we are free to go to continue with implementing measures to

• continuously build the static derivative on changes in the content source
• continuously deploy the static build artifact into a suitable environment