set up blog

Author: motdotla

_layouts/blog.html

@@ -0,0 +1,21 @@
+---
+layout: default
+---
+
+<main class="w-full max-w-2xl mx-auto px-6 mt-12 md:mt-20 flex flex-col gap-4">
+  <a href="/blog">&larr; back to blog</a>
+  <img class="mx-auto h-8 w-8 rounded-full" src="/assets/img/mot.jpg" alt="Scott Motte" />
+  <p class="text-center">Scott (Mot) Motte</p>
+  <p><time datetime="{{ page.date | date: "%Y-%m-%d"  }}">{{ page.date | date: "%B %d, %Y" }}</time></p>
+  <article>
+    <h1 class="text-2xl font-black mb-4">
+      {{ page.title }}
+    </h1>
+    <div class="prose mx-auto max-w-prose">
+      {{ content }}
+    </div>
+  </article>
+  <div class="prose mx-auto max-w-prose my-10">
+    <p class="text-center"><a href="/feed.xml">Subscribe via RSS</a> or follow us <a href="https://x.com/vestauth">@vestauth 𝕏</a></p>
+  </div>
+</main>

assets/img/blog/blog-1.png

@@ -0,0 +1,45 @@
+---
+layout: blog
+author: "Scott Motte – Mot"
+title: "introducing vestauth"
+image: "/assets/img/blog/blog-1.png"
+excerpt: "Agent authentication with verifiable identity and request signatures."
+---
+
+Today we are launching **vestauth**, authentication built for agents.
+
+`vestauth` gives agents a cryptographic identity and lets providers verify signed requests with confidence. It is designed to be simple to adopt and strong by default.
+
+## Why vestauth
+
+The shift to agents introduces a new baseline requirement: providers need to know which agent made a request and whether that request was tampered with in transit.
+
+`vestauth` addresses this with:
+
+- agent identities backed by cryptographic keys
+- signed requests agents can generate from the CLI
+- verification primitives providers can use in their servers
+
+## Quick look
+
+Initialize an agent identity:
+
+```sh
+vestauth agent init
+```
+
+Sign and send a request:
+
+```sh
+vestauth agent curl https://ping.vestauth.com/ping
+```
+
+Verify on the provider side:
+
+```js
+const agent = await vestauth.provider.verify(req.method, url, req.headers)
+```
+
+## What is next
+
+Next posts will cover the protocol, threat model, and implementation details, along with practical integration guides.

assets/img/mot.jpg

@@ -0,0 +1,24 @@
+---
+title: "Blog"
+---
+
+<section class="w-full max-w-2xl mx-auto px-6 mt-12 md:mt-20 flex flex-col gap-4">
+  <h1 class="font-extrabold text-2xl text-zinc-950 dark:text-zinc-50 text-center">Blog</h1>
+  <ul class="grid grid-cols-1 gap-4 sm:grid-cols-2">
+    {% for post in site.categories.blog %}
+      <li>
+        <a href="{{ post.url }}" class="hover:no-underline bg-transparent p-2 opacity-90 hover:opacity-100 rounded block h-full">
+          <div class="space-y-2">
+            <img alt="{{ post.title }}" loading="lazy" width="395" height="208" decoding="async" class="w-full" src="{{ post.image }}">
+            <div class="flex flex-col">
+              <time class="text-xs text-zinc-500 font-normal" datetime="{{ post.date | date: "%Y-%m-%d" }}">
+                {{ post.date | date: "%B %d, %Y" }}
+              </time>
+              <h2 class="font-bold text-zinc-950 dark:text-zinc-50">{{ post.title }}</h2>
+            </div>
+          </div>
+        </a>
+      </li>
+    {% endfor %}
+  </ul>
+</section>