Merge pull request #106 from jbolns/dev

GH Action Deploy #12

.gitignore

@@ -5,6 +5,7 @@
 
 # build output
 dist/
+docs/
 
 # generated types
 .astro/

src/content/blog/en/digital-transformation-currents.mdx

@@ -17,7 +17,7 @@ Other lower-level drivers exist.[^1] However, these three needs seem to be influ
 
 They are always present. Like oceanic currents.
 
-<Image src={currents} alt="Top-level needs driving the digital transformation." />
+![Top-level needs driving the digital transformation.](/digital-transformation-currents.webp)
 <span className="text-2sm">*Figure 1: Top-level needs driving the digital transformation.*</span>
 
 ### Integration[^2]

src/content/blog/en/risk-in-platform-economy.mdx

@@ -7,12 +7,6 @@ heroImage: "@assets/banner-risk.webp"
 tags: ["policy", "coding"]
 ---
 
-import { Image } from 'astro:assets';
-import list from '@assets/list-of-hazards.webp';
-import cycle from '@assets/risk-assessment-cycle.webp'
-import configurational from '@assets/configurational-risk-assessment.webp'
-
-
 Risk assessment in the platform economy seems feasible. 
 
 Furthermore, while the initial steps are are more or less what you would expect from a traditional risk assessment process, the analysis can, in theory, go beyond the fundamentals.
@@ -23,7 +17,7 @@ Conceptually, the process of assessing risk in the platform economy can be divid
 ### Identification
 All risk assessment shares a need for identifying threats/hazards---thing that can go wrong. The platform economy is no different: online activities can go wrong in various manners.
 
-<Image src={list} alt="Example list of hazards." />
+![Example list of hazards](/list-of-hazards.webp)
 <span className="text-2sm">*Figure 1: Example list of hazards*</span>
 
 A first step in assessing risk in the platform economy is therefore to list things that are difficult to manage in digital platforms (one or many). Comprehensiveness is unlikely at first, but an initial set of concerns can act as a preliminary list of hazards to improve over time.
@@ -35,7 +29,7 @@ The second step is also fairly standard. Once there is an initial list of hazard
 
 Initial estimates will likely be inaccurate, but these can be improved cyclically, as visualised in figure 2.
 
-<Image src={cycle} alt="A foundational risk assessment cycle." />
+![Foundational risk assessment cycle](/risk-assessment-cycle.webp)
 <span className="text-2sm">*Figure 2: Foundational risk assessment cycle*</span>
 
 ### Configurational (life cycle) assessment
@@ -45,7 +39,7 @@ The data-driven nature of the platform economy should in theory permit us to mov
 
 Conceptually, any risk can be mapped in a “tree”-like manner. For all applicable hazards, on can layout all possible states/scenarios and follow things as a product/service makes its way through the different levels of the platform economy, as visualised in figure 3.[^2]
 
-<Image src={configurational} alt="Configurational risk assessment example for a single hazard." />
+![Configurational risk assessment example for a single hazard](/configurational-risk-assessment.webp)
 <span className="text-2sm">*Figure 3: Configurational risk assessment example for a single hazard.*</span>
 
 ## Who?