<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Geoffrey Byers</title><description>Dallas, TX. Building in public. Notes, projects, and case studies from a designer-founder.</description><link>https://geoffreybyers.com/</link><language>en-us</language><item><title>Hello, World</title><link>https://geoffreybyers.com/posts/hello-world/</link><guid isPermaLink="true">https://geoffreybyers.com/posts/hello-world/</guid><description>Kicking off geoffreybyers.com — what I&apos;ll write about and why.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><content:encoded>This is the first post on the new site. Short and sweet.

## Why another blog?

Because dictation is easier than Twitter threads, and I want my notes
to outlive any platform. I&apos;ll write about what I&apos;m building, what I
shipped, and what broke.</content:encoded></item><item><title>Why Astro for this Blog</title><link>https://geoffreybyers.com/posts/why-astro/</link><guid isPermaLink="true">https://geoffreybyers.com/posts/why-astro/</guid><description>Static files, zero JS by default, MDX. The short version.</description><pubDate>Tue, 14 Apr 2026 00:00:00 GMT</pubDate><content:encoded>Astro ships zero JS by default. That&apos;s rare and worth celebrating.

```javascript
// This code block will be syntax-highlighted by Shiki
export default function hello() {
  return &quot;world&quot;;
}
```

Content collections, typed frontmatter, view transitions, Pagefind
search — all wired without a framework runtime on the page.</content:encoded></item><item><title>Building in Public Notes</title><link>https://geoffreybyers.com/posts/building-in-public/</link><guid isPermaLink="true">https://geoffreybyers.com/posts/building-in-public/</guid><description>Why I&apos;m threading project updates into the feed.</description><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate><content:encoded>Every project gets a case study page. Posts link up to the project
they belong to, and the project page threads them back together.

This post isn&apos;t linked to a project — it&apos;s a meta note about the
mechanism itself.</content:encoded></item><item><title>Restaurant Cold Email — Week 1</title><link>https://geoffreybyers.com/posts/restaurant-cold-email-w1/</link><guid isPermaLink="true">https://geoffreybyers.com/posts/restaurant-cold-email-w1/</guid><description>Early sequences, list sourcing, and the first booked meeting.</description><pubDate>Sun, 12 Apr 2026 00:00:00 GMT</pubDate><content:encoded>First week of live outbound. 240 contacts across two buying centers.
Two replies, one booked tasting.

Lessons:

1. Subject lines referencing the buyer&apos;s specific venue beat generic ones 4x.
2. Thursday 7:00 AM local beat every other send time we tested.
3. Two follow-ups is the sweet spot before a restaurant goes silent.</content:encoded></item></channel></rss>