chore: Reflect OpenAI role

Author: andrewginns

CONTENT.md

@@ -0,0 +1,102 @@
+Based on this Astro framework website integration what possible options are there to allow the site owner to edit and preview the content without having to directly edit html inside a code editor. Specifically content that is included inline like the experience and intro pages.
+
+I would like to avoid a third party CMS or anything that would significantly bloat the codebase. External packages or Astro native tools/approaches are acceptable.
+
+<response>
+This is a common challenge when managing content within a Static Site Generator (SSG) like Astro. The goal is to enable easier content editing and previewing without resorting to editing HTML directly in Astro components, while adhering to the constraints of avoiding heavy third-party CMS solutions and minimizing bloat.
+
+The solutions below leverage Astro's capabilities and the existing Git-based workflow.
+
+### Foundational Step: Migrate to Astro Content Collections
+
+Before implementing an enhanced editing interface, the content must be decoupled from the presentation logic. The Astro-native solution for this is **Content Collections**.
+
+1.  **Astro Content Collections:** The cornerstone of managing content in Astro. It separates content from presentation logic by storing it in `src/content/` using Markdown, MDX, YAML, or JSON. It provides type safety via Zod schemas.
+
+    - _Why it's essential:_ It's Astro-native, adds zero runtime bloat, and is the prerequisite for most lightweight CMS solutions. It immediately improves the editing experience by moving from editing HTML/Astro components to editing cleaner Markdown or structured data files.
+
+2.  **MDX for Flexibility:** For pages like "Experience" that might mix prose with specific UI components (like timelines or skill cards), MDX (`.mdx`) allows the use of Astro components within Markdown, offering great flexibility.
+
+By migrating the "Experience" and "Intro" pages to Content Collections, you enable the following enhanced editing and previewing options.
+
+---
+
+### Option 1: Enhanced File-Based Editing (Zero Bloat)
+
+If the primary goal is to avoid editing _HTML_ inside the code editor, Content Collections alone might suffice. The experience of editing Markdown or YAML is significantly cleaner.
+
+#### 1a. Local Editing with Live Preview
+
+The standard Astro development workflow provides the best preview experience.
+
+- **Workflow:** The owner runs `npm run dev`. They edit the Markdown/YAML files in their preferred editor.
+- **Preview:** Astro's Hot Module Replacement (HMR) provides instant, accurate previews in the browser as files are saved.
+- **Enhancement: Dedicated Markdown Editors:** To move away from the "code editor" feel, the owner can use dedicated writing apps like Obsidian, Typora, or iA Writer. These offer a focused, often near-WYSIWYG environment for editing the files in `src/content/`.
+
+#### 1b. Remote Editing with GitHub.dev
+
+To edit content without setting up the local development environment or using a local code editor.
+
+- **Workflow:** The owner navigates to the repository on GitHub.com and presses the `.` (period) key. This launches GitHub.dev, a web-based version of VS Code.
+- **Editing:** The owner can edit the content files directly in the browser and commit the changes.
+- **Preview:** GitHub.dev offers Markdown previews, but not a preview of the actual site design. The changes are visible live only after the GitHub Action rebuilds and deploys the site.
+
+---
+
+### Option 2: Git-Based CMS (Web UI Editing)
+
+If the goal is to provide a friendly, form-based web interface (an "admin panel") for editing content, a Git-based CMS is the ideal solution for SSG architectures.
+
+**Concept:** These tools provide a web UI for editing content. They do not store data in an external database; instead, they commit changes directly back to the Markdown/YAML files in the Git repository, maintaining Git as the source of truth and triggering automatic rebuilds.
+
+#### 2a. Keystatic (Highly Recommended for Astro)
+
+Keystatic is a modern, open-source Git-based CMS designed with excellent support for Astro and TypeScript.
+
+- **How it works:** Keystatic integrates closely with Astro. You define your content schema using Keystatic's API (which aligns well with Content Collections principles), and it automatically generates a type-safe admin UI.
+- **Pros:**
+  - **Astro & TypeScript Native:** Excellent integration and developer experience.
+  - **Type-Safe UI:** The admin forms are generated from your configuration, ensuring data integrity.
+  - **Minimal Bloat:** The CMS interface runs locally during development or via a dedicated `/admin` route, with minimal impact on the production site's performance.
+  - **Local and Hosted:** Supports local file editing and connecting to GitHub for production editing.
+- **Cons:**
+  - Requires initial setup and configuration.
+
+#### 2b. Decap CMS (The Established Alternative)
+
+Formerly Netlify CMS, Decap CMS is a robust, framework-agnostic option.
+
+- **How it works:** You add a static HTML file and a YAML configuration file to the `public/` directory.
+- **Pros:**
+  - **Maturity:** Well-established and widely used.
+  - **Zero Production Bloat:** The CMS JavaScript is only loaded when accessing the `/admin` route.
+- **Cons:**
+  - **Schema Duplication:** You must manually define the content structure in YAML, duplicating the effort made in Astro Content Collections (unlike Keystatic).
+  - **Older UI:** The interface is functional but less modern than Keystatic.
+
+---
+
+### Option 3: Creative GitHub API Usage (Unconventional)
+
+The project already utilizes the GitHub API to fetch repository data (`systemPatterns.md`). This pattern can be extended to fetch content.
+
+- **Concept:** Use a specific GitHub Discussion or Issue as the content source for a page (e.g., "CONTENT: Introduction Bio"). During the Astro build process, fetch the content of that specific post via the GitHub API.
+- **Pros:**
+  - **Web UI Included:** The owner edits content using the standard GitHub comment box (Markdown supported).
+  - **Zero CMS Bloat:** Only requires build-time API fetching logic.
+  - **Accessible:** Editing can be done via the GitHub website or mobile app.
+- **Cons:**
+  - **Unconventional:** Blurs the line between issue tracking and content management.
+  - **Fragility:** Relies on specific Issue/Discussion IDs remaining constant.
+  - **No Live Preview:** Changes require a rebuild.
+
+---
+
+### Recommendation
+
+Given the project's emphasis on technical excellence, TypeScript integration, and minimal bloat, the recommended path is:
+
+1.  **Migrate to Astro Content Collections.** This is the essential first step. It improves the project architecture and immediately makes content updates cleaner.
+2.  **Evaluate the Editing Experience.** See if editing Markdown/YAML files (perhaps using GitHub.dev or a dedicated Markdown editor) is sufficient.
+3.  **Integrate Keystatic (Option 2a).** If a form-based admin UI is desired, Keystatic offers the best integration with Astro, the most modern experience, and respects the project's type-safety goals while keeping content in the Git repository.
+    </response>

src/lib/github.ts

@@ -284,7 +284,7 @@ export async function getGitHubProfile(username: string) {
     const roleMatch = bio.match(
       /(?:I'm\s+(?:a\s+)?|I\s+am\s+(?:a\s+)?|Currently\s+(?:a\s+)?|Working\s+as\s+(?:a\s+)?)([^.]+(?:Engineer|Scientist|Developer|Manager|Architect|Lead|Director|Consultant))/i
     );
-    const role = roleMatch ? roleMatch[1].trim() : 'AI Solutions Architect';
+    const role = roleMatch ? roleMatch[1].trim() : 'Solutions Architect';
 
     return {
       company: profile.company || 'Motorway',
@@ -319,8 +319,8 @@ export async function getGitHubProfile(username: string) {
     };
 
     return {
-      company: 'Google',
-      role: 'AI Solutions Architect',
+      company: 'OpenAI',
+      role: 'Solutions Architect',
       bio: '',
       profile: defaultProfile,
     };

src/pages/experience.astro

@@ -8,10 +8,24 @@ import LastUpdated from '../components/LastUpdated.astro';
     <h1>Professional Experience</h1>
 
     <section class="current-role">
+      <div class="role">
+        <h2>Solutions Architect</h2>
+        <div class="company">OpenAI</div>
+        <div class="period">November 2025 - Present</div>
+        <ul class="responsibilities">
+          <li>
+            Partnering with customers to safely deploy generative AI and build real-world
+            applications that support OpenAI's mission to ensure AGI benefits all of humanity.
+          </li>
+        </ul>
+      </div>
+    </section>
+
+    <section class="previous-roles">
       <div class="role">
         <h2>AI Solutions Architect</h2>
         <div class="company">Google</div>
-        <div class="period">August 2025 - Present</div>
+        <div class="period">August 2025 - November 2025</div>
         <ul class="responsibilities">
           <li>
             Designing and rapidly prototyping Generative AI solutions for enterprise customers
@@ -35,9 +49,6 @@ import LastUpdated from '../components/LastUpdated.astro';
           </li>
         </ul>
       </div>
-    </section>
-
-    <section class="previous-roles">
       <div class="role">
         <h2>Lead Machine Learning Engineer</h2>
         <div class="company">Motorway</div>