style(theme): refine alert callouts and tighten code blocks

- Alert title: tighter spacing, uppercase label, filled circular icon badge
  as a stronger per-type visual indicator.
- Highlighted (.highlight) code blocks: trim the inherited .prose pre
  padding/margins so server-side Chroma blocks no longer read as a wall of
  whitespace; line numbers retained.
- Update contributor guide article and Front Matter CMS config.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: HeyItsGilbert

content/articles/2026-06-23-how-to-write-for-powershell-org.md

@@ -1,16 +1,17 @@
 ---
-title: "How to Write for PowerShell.org"
-description: "Two ways to submit an article to PowerShell.org, best practices that get you published faster, and why claiming an author page is worth five minutes of your time."
+title: How to Write for PowerShell.org
+description: Two ways to submit an article to PowerShell.org, best practices that get you published faster, and why claiming an author page is worth five minutes of your time.
 author: Gilbert Sanchez
 authors:
   - Gilbert Sanchez
-date: "2026-06-23T00:00:00+00:00"
+date: 2026-06-23T00:00:00+00:00
 categories:
   - Tutorials
 tags:
   - contributing
   - community
   - writing
+fmContentType: article
 ---
 
 There's a thought that stops a lot of good articles: *who am I to write for
@@ -98,15 +99,14 @@ flow through the same review.
 
 4. Open a pull request with a short description, and we'll review it there.
 
-> [!TIP]
-> Let VS Code do the boring part. Install the [Front Matter
-> CMS](https://frontmatter.codes/) extension, open the repo, and run **"Create
-> content"** in the `content/articles` folder. It scaffolds the
-> `YYYY-MM-DD-slug.md` filename and every front-matter field for you, and it
-> gives you a form for the title, description, category, and tags instead of a
-> wall of YAML you can typo. It turns the single most error-prone step into a
-> fill-in-the-blanks. If you only adopt one tool from this article, make it this
-> one.
+> [!TIP] Let VS Code do the boring part!
+> Install the [Front Matter CMS](https://frontmatter.codes/) extension, open the
+> repo, and run **"Create content"** in the `content/articles` folder. It
+> scaffolds the `YYYY-MM-DD-slug.md` filename and every front-matter field for
+> you, and it gives you a form for the title, description, category, and tags
+> instead of a wall of YAML you can typo. It turns the single most error-prone
+> step into a fill-in-the-blanks. If you only adopt one tool from this article,
+> make it this one.
 
 ## Best practices that get you published faster
 
@@ -162,9 +162,9 @@ rule that trips people up: the `<slug>` has to match your byline exactly
 
 So let the helper script handle it:
 
-```powershell
+{{< terminal lang="powershell" >}}
 ./tools/new-author.ps1 "Jane Doe"
-```
+{{< /terminal >}}
 
 That scaffolds `content/authors/jane-doe/_index.md` with every field commented.
 Fill in what you want, delete the rest:
@@ -188,14 +188,14 @@ putting your email address in a public repo. Store the MD5 hash of your
 lowercased email as `gravatar_hash`, and Gravatar serves your picture while your
 email stays private:
 
-```powershell
+{{< terminal lang="powershell" >}}
 $email = "jane@example.com"
 [System.BitConverter]::ToString(
   [System.Security.Cryptography.MD5]::Create().ComputeHash(
     [System.Text.Encoding]::UTF8.GetBytes($email.Trim().ToLowerInvariant())
   )
 ).Replace("-", "").ToLowerInvariant()
-```
+{{< /terminal >}}
 
 And if your name ever changes, `./tools/new-author.ps1 "Old Name" -To "New Name"`
 rewrites your byline across every article and adds a redirect so your old

frontmatter.json

@@ -260,29 +260,72 @@
     {
       "title": "Articles",
       "path": "[[workspace]]/content/articles",
-      "contentTypes": ["article"],
+      "contentTypes": [
+        "article"
+      ],
       "filePrefix": "{{year}}-{{month}}-{{day}}"
     },
     {
       "title": "Podcast",
       "path": "[[workspace]]/content/podcast",
-      "contentTypes": ["podcast"],
+      "contentTypes": [
+        "podcast"
+      ],
       "filePrefix": "{{year}}-{{month}}-{{day}}"
     },
     {
       "title": "Events",
       "path": "[[workspace]]/content/calendar",
-      "contentTypes": ["event"]
+      "contentTypes": [
+        "event"
+      ]
     },
     {
       "title": "Authors",
       "path": "[[workspace]]/content/authors",
-      "contentTypes": ["author"]
+      "contentTypes": [
+        "author"
+      ]
     },
     {
       "title": "Pages",
       "path": "[[workspace]]/content",
-      "contentTypes": ["page"]
+      "contentTypes": [
+        "page"
+      ]
+    }
+  ],
+  "frontMatter.content.snippets": {
+    "Terminal": {
+      "description": "Show your terminal commands in a nice terminal window.",
+      "body": [
+        "{{< terminal title=\"[[filename]]\" lang=\"[[language]]\" >}}",
+        "[[selection]]",
+        "{{< /terminal >}}"
+      ],
+      "fields": [
+        {
+          "name": "filename",
+          "title": "filename",
+          "type": "string",
+          "single": true,
+          "default": ""
+        },
+        {
+          "name": "language",
+          "title": "language",
+          "type": "string",
+          "single": true,
+          "default": ""
+        },
+        {
+          "name": "selection",
+          "title": "selection",
+          "type": "string",
+          "single": true,
+          "default": ""
+        }
+      ]
     }
-  ]
-}
+  }
+}

themes/powershell-community/layouts/_default/baseof.html

@@ -88,6 +88,12 @@
            terminal chrome renders flush; Prism handles token colors. */
         .ps-terminal pre { background: transparent; color: #ccc; margin: 0; border-radius: 0; padding: 1.25rem; overflow-x: auto; }
 
+        /* Hugo/Chroma highlighted blocks (.highlight) carry their own light
+           background; trim the heavier .prose pre padding/margins so they don't
+           read as a wall of whitespace. */
+        .prose .highlight { margin: 1.25rem 0; border-radius: 0.5rem; overflow: hidden; }
+        .prose .highlight pre { margin: 0; padding: 0.85rem 1rem; border-radius: 0; line-height: 1.5; }
+
         .hero-pattern {
             background: linear-gradient(135deg, #0078D4 0%, #00BCF2 100%);
             position: relative;

themes/powershell-community/static/css/alerts.css

@@ -19,15 +19,25 @@
     display: flex;
     align-items: center;
     gap: 0.5rem;
-    margin: 0 0 0.25rem;
-    font-weight: 600;
+    margin: 0 0 0.1rem;
+    font-size: 0.78rem;
+    font-weight: 700;
+    letter-spacing: 0.04em;
+    text-transform: uppercase;
     font-style: normal;
     color: var(--ps-alert-color);
 }
 
 .ps-alert-title i {
-    width: 1em;
-    text-align: center;
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    width: 1.5rem;
+    height: 1.5rem;
+    border-radius: 9999px;
+    background: var(--ps-alert-color);
+    color: #fff;
+    font-size: 0.8rem;
 }
 
 /* Keep inner Markdown (.prose adds top/bottom margins to p/ul/etc.) flush