From 53d3d070226a96be297923cd70fdfec8660f9834 Mon Sep 17 00:00:00 2001
From: Fernando Ayats <ayatsfer@gmail.com>
Date: Thu, 29 Aug 2024 16:39:59 +0200
Subject: [PATCH] update astro-1

---
 src/content/blog/astro-1/index.md | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/src/content/blog/astro-1/index.md b/src/content/blog/astro-1/index.md
index cfdf91a..a32d6ae 100644
--- a/src/content/blog/astro-1/index.md
+++ b/src/content/blog/astro-1/index.md
@@ -115,5 +115,21 @@ The [Astro webpage](https://astro.build) describes it as a "web framework for
 content-driven websites". You can find many explanations on the internet about
 how Astro works, but here is my take as a list of the key features:
 
-- Much like [Pandoc](https://pandoc.org), Astro can take input Markdown files
-and transform them into HTML.
+- Much like [Pandoc](https://pandoc.org), Astro takes Markdown files as input,
+and outputs some HTML.
+- You start from you plain HTML+CSS, statically served.
+- Astro code fences let you generate the HTML programmatically, for example:
+    ```astro
+    ---
+    // This is JavaScript
+    const text = "foo" + "bar";
+    ---
+
+    <!-- This a Component template (HTML+{JS}) -->
+    <p>{text}<p>
+    ```
+- A standard library that can handle content collections for you.
+
+Apart from these insights, this framework feels to me just like "HTML + JS
+components", which is exactly what I needed.
+