diff --git a/astro.config.mjs b/astro.config.mjs
index e0385fc..5eb72e9 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -28,7 +28,7 @@ export default defineConfig({
resolve: {
alias: {
- "@assets/*": "/src/assets/",
+ "~": "/src/",
},
},
diff --git a/src/content/blog/en/risk-in-platform-economy.mdx b/src/content/blog/en/risk-in-platform-economy.mdx
index 55ddb69..45ed7eb 100644
--- a/src/content/blog/en/risk-in-platform-economy.mdx
+++ b/src/content/blog/en/risk-in-platform-economy.mdx
@@ -17,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.
-![Example list of hazards](@assets/list-of-hazards.webp "Figure 1: Example list of hazards.")
+![Example list of hazards](~/assets/list-of-hazards.webp "Figure 1: Example list of hazards.")
*Figure 1: Example list of hazards*
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.
@@ -29,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.
-![Foundational risk assessment cycle](@assets/risk-assessment-cycle.webp "Figure 1: A foundational risk assessment cycle.")
+![Foundational risk assessment cycle](~/assets/risk-assessment-cycle.webp "Figure 2: A foundational risk assessment cycle.")
*Figure 2: Foundational risk assessment cycle*
### Configurational (life cycle) assessment
@@ -39,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]
-![Configurational risk assessment example for a single hazard.](@assets/configurational-risk-assessment.webp "Figure 1: Configurational risk assessment example (single hazard).")
+![Configurational risk assessment example for a single hazard.](~/assets/configurational-risk-assessment.webp "Figure 3: Configurational risk assessment example (single hazard).")
*Figure 3: Configurational risk assessment example for a single hazard.*
## Who?