Link markdown, robots and contact vars

.markdownlint.json

@@ -0,0 +1,5 @@
+{
+    "MD013":false,
+    "MD033": false,
+    "MD036": false
+}

src/components/cards/contactCard.astro

@@ -35,6 +35,7 @@ const loadedLogoImage = plsLoadImage(images_logos, imagePath)
 <style>
   a {
     text-decoration: none;
+    --s-image: 80px;
   }
 
   article {
@@ -53,7 +54,7 @@ const loadedLogoImage = plsLoadImage(images_logos, imagePath)
 
   article img {
     border-radius: 1.25rem;
-    width: 80px;
+    width: var(--s-image);
     height: auto;
   }
 
@@ -74,8 +75,8 @@ const loadedLogoImage = plsLoadImage(images_logos, imagePath)
     text-align: center;
     background-color: var(--c-primary-background);
     border-radius: 1.25rem;
-    width: 80px;
-    height: 80px;
+    width: var(--s-image);
+    height: var(--s-image);
     opacity: 90%;
     z-index: 100;
   }

src/content/blog/astro-usage.md

@@ -75,7 +75,7 @@ allPosts.sort(
 The `frontmatter` interface is a kind of header for the markdown files which provides astro with metadata like title, author and such.
 It is structured like this:
 
-```
+```yaml
 ---
 layout: ../../layouts/blogPost.astro
 title: 'How Astro powers this site'

src/content/blog/deploying-this-round-2.md

@@ -74,7 +74,7 @@ As you can see, I am using a custom container for the runtime stage, which will
 
 ### Custom serve docker - My new goto for static site serving
 
-When starting out with the `Dockerfile`, I first used the standard `node:lts` image for the runtime. This meant I also had to install the `serve` package by `@warren-bank` each time I built the container. Since this takes extra time and resources each run, I decided to create a pre-configured docker container that can be used for this instead. 
+When starting out with the `Dockerfile`, I first used the standard `node:lts` image for the runtime. This meant I also had to install the `serve` package by `@warren-bank` each time I built the container. Since this takes extra time and resources each run, I decided to create a pre-configured docker container that can be used for this instead.
 
 The `Dockerfile` for that one is laughable simple:
 

src/content/blog/deploying-this.md

@@ -81,7 +81,7 @@ screen -S website-firq-npx -dm npx serve public/ -p 9000 -c serve.json"
 
 With the following directory structure on the remote host, this can easily be explained:
 
-```
+```plain
 /
 ├─ public/
 │  ├─ site content

static/robots.txt

@@ -1,7 +1,8 @@
-user-agent:*
+User-agent: *
 Disallow: /assets/data/
 
 User-agent: GPTBot
+User-agent: Bytespider
 Disallow: /
 
 Sitemap: https://firq.dev/sitemap-index.xml