diff --git a/src/content/til/2024-12-30-astrowind-foundation.md b/src/content/til/2024-12-30-astrowind-foundation.md
new file mode 100644
index 00000000..d0c2d92e
--- /dev/null
+++ b/src/content/til/2024-12-30-astrowind-foundation.md
@@ -0,0 +1,36 @@
+---
+title: 'Starting with AstroWind: The Foundation of Resonant Projects'
+date: 2024-12-30
+tags: ['astro', 'astrowind', 'tailwind', 'web-development']
+description: 'Today I learned how starting with a well-structured template like AstroWind can accelerate custom website development while still allowing complete customization.'
+draft: false
+---
+
+# Starting with AstroWind: The Foundation of Resonant Projects
+
+Building a custom website from scratch is rewarding, but starting with a solid foundation can save weeks of work. Today I began customizing the AstroWind template for Resonant Projects.
+
+## Why Start with a Template?
+
+AstroWind provides:
+
+- **Pre-built Astro components** with proper TypeScript types
+- **Tailwind CSS integration** with dark mode support out of the box
+- **SEO optimization** built into the layout components
+- **Performance optimizations** like image optimization and lazy loading
+
+## Initial Customization Steps
+
+The first changes I made were to themes and colors, establishing the visual identity:
+
+```typescript
+// Customizing the color scheme
+:root {
+ --aw-color-primary: /* your brand color */;
+ --aw-color-secondary: /* accent color */;
+}
+```
+
+## Key Takeaway
+
+Don't reinvent the wheel—but also don't be afraid to modify every aspect of a template. The goal is to use it as scaffolding, not a constraint. Within a few commits, the site was already distinctly "Resonant Projects" rather than generic AstroWind.
diff --git a/src/content/til/2025-03-23-vercel-speed-insights.md b/src/content/til/2025-03-23-vercel-speed-insights.md
new file mode 100644
index 00000000..2fdb85ea
--- /dev/null
+++ b/src/content/til/2025-03-23-vercel-speed-insights.md
@@ -0,0 +1,43 @@
+---
+title: 'Integrating Vercel Speed Insights for Real User Metrics'
+date: 2025-03-23
+tags: ['vercel', 'performance', 'monitoring', 'web-vitals']
+description: 'Today I learned how to integrate Vercel Speed Insights to get real-world performance metrics from actual users, not just Lighthouse synthetic tests.'
+draft: false
+---
+
+# Integrating Vercel Speed Insights for Real User Metrics
+
+Lighthouse scores are great, but they're synthetic. Today I integrated Vercel Speed Insights to get real user metrics (RUM).
+
+## Why Real User Metrics Matter
+
+Lighthouse runs in a controlled environment. Real users have:
+
+- Varying network conditions
+- Different device capabilities
+- Various geographic locations
+- Actual interaction patterns
+
+## Quick Integration
+
+```astro
+---
+import { SpeedInsights } from '@vercel/speed-insights/astro';
+---
+
+
+```
+
+That's it! Vercel automatically starts collecting:
+
+- **LCP** (Largest Contentful Paint)
+- **FID** (First Input Delay)
+- **CLS** (Cumulative Layout Shift)
+- **TTFB** (Time to First Byte)
+
+## Insights from Real Data
+
+After a week of data, I discovered that mobile users in certain regions were experiencing significantly slower TTFB than my Lighthouse tests suggested. This led to investigating edge caching strategies.
+
+The lesson: synthetic tests are a starting point, but real user metrics tell the true story.
diff --git a/src/content/til/2025-05-18-pagefind-search.md b/src/content/til/2025-05-18-pagefind-search.md
new file mode 100644
index 00000000..8da23e0f
--- /dev/null
+++ b/src/content/til/2025-05-18-pagefind-search.md
@@ -0,0 +1,53 @@
+---
+title: 'Adding Lightning-Fast Search with Pagefind'
+date: 2025-05-18
+tags: ['astro', 'search', 'pagefind', 'static-site']
+description: 'Today I learned how Pagefind provides instant client-side search for static sites without any backend infrastructure.'
+draft: false
+---
+
+# Adding Lightning-Fast Search with Pagefind
+
+Static sites traditionally struggle with search—you either need a backend service or rely on external providers. Today I integrated Pagefind, and it's a game-changer.
+
+## What Makes Pagefind Special
+
+Pagefind builds a search index at build time and includes a tiny client-side search that:
+
+- Works entirely client-side (no server needed)
+- Has a compressed index averaging ~100kB for most sites
+- Provides instant results with typo tolerance
+- Supports multiple languages
+
+## Integration in Astro
+
+```bash
+pnpm add pagefind
+```
+
+Then in your build script:
+
+```json
+{
+ "scripts": {
+ "postbuild": "pagefind --site dist"
+ }
+}
+```
+
+And in your search component:
+
+```astro
+
+
+```
+
+## Key Insight
+
+The search index is built at deploy time, so it's always in sync with your content. No more worrying about stale search results or webhook failures. When your site builds, your search is automatically updated.
+
+Perfect for content-heavy static sites where you want great search UX without operational complexity.
diff --git a/src/content/til/2025-05-27-notion-contact-form.md b/src/content/til/2025-05-27-notion-contact-form.md
new file mode 100644
index 00000000..d4f6ab68
--- /dev/null
+++ b/src/content/til/2025-05-27-notion-contact-form.md
@@ -0,0 +1,56 @@
+---
+title: 'Building a Notion-Powered Contact Form'
+date: 2025-05-27
+tags: ['notion', 'api', 'forms', 'astro']
+description: 'Today I learned how to submit form data directly to a Notion database, creating a serverless CRM-like system.'
+draft: false
+---
+
+# Building a Notion-Powered Contact Form
+
+Why pay for a form backend when Notion can be your database? Today I implemented a contact form that submits directly to Notion.
+
+## The Architecture
+
+```
+User submits form → Astro API route → Notion API → Database entry
+```
+
+## Setting Up the Notion Integration
+
+1. Create a Notion integration at notion.so/my-integrations
+2. Share your database with the integration
+3. Store the token securely in environment variables
+
+## The API Route
+
+```typescript
+// src/pages/api/submit-to-notion.ts
+import { Client } from '@notionhq/client';
+
+const notion = new Client({ auth: process.env.NOTION_TOKEN });
+
+export async function POST({ request }) {
+ const data = await request.formData();
+
+ await notion.pages.create({
+ parent: { database_id: process.env.NOTION_DATABASE_ID },
+ properties: {
+ Name: { title: [{ text: { content: data.get('name') } }] },
+ Email: { email: data.get('email') },
+ Message: { rich_text: [{ text: { content: data.get('message') } }] },
+ },
+ });
+
+ return redirect('/thank-you');
+}
+```
+
+## Benefits Over Traditional Forms
+
+- **No additional service costs** - Notion's API is free
+- **Built-in collaboration** - Team can see and respond to inquiries
+- **Flexible schema** - Add fields to your database anytime
+- **Views and filters** - Sort by date, filter by status, etc.
+
+The key insight: Notion databases are surprisingly powerful backends for simple data collection needs.
diff --git a/src/content/til/2025-05-27-react-email-welcome.md b/src/content/til/2025-05-27-react-email-welcome.md
new file mode 100644
index 00000000..ae4ea6e8
--- /dev/null
+++ b/src/content/til/2025-05-27-react-email-welcome.md
@@ -0,0 +1,52 @@
+---
+title: 'Sending Beautiful Welcome Emails with React Email'
+date: 2025-05-27
+tags: ['react-email', 'email', 'automation', 'typescript']
+description: 'Today I learned how React Email makes building and previewing HTML emails as easy as building React components.'
+draft: false
+---
+
+# Sending Beautiful Welcome Emails with React Email
+
+HTML emails are notoriously painful to build. Tables, inline styles, client quirks... Today I discovered React Email, and it changes everything.
+
+## Why React Email?
+
+- Write emails using React components
+- Live preview during development
+- Built-in components for common patterns
+- TypeScript support out of the box
+
+## Creating a Welcome Email
+
+```tsx
+// emails/WelcomeEmail.tsx
+import { Html, Head, Body, Container, Text, Button } from '@react-email/components';
+
+export const WelcomeEmail = ({ name }: { name: string }) => (
+
+
+