Update README

Author: georg-schwarz

README.md

@@ -18,10 +18,10 @@ Open [localhost:4321](http://localhost:4321) in your browser.
 ## Features
 
 - **Astro.js** - Fast static site generation with partial hydration
+- **Storybook** - Component library with nice UI to browse
 - **Tailwind CSS** - Utility-first styling with custom theme
 - **TypeScript** - Strict mode for full type safety
 - **Content Collections** - Type-safe blog posts with Zod validation
-- **Resources Library** - Optional evergreen resources collection with categories and manual ordering
 - **MDX Support** - Enhanced markdown with components
 - **RSS Feed** - Automatic feed generation (`/rss.xml`)
 - **Sitemap** - SEO-friendly sitemap generation (`/sitemap-index.xml`)
@@ -35,11 +35,8 @@ src/
 │   ├── molecules/    # Compound components
 │   ├── organisms/    # Section components
 │   └── templates/    # Page-level composition (optional)
-├── content/         # Blog posts and resources (MDX)
-├── data/            # Site-specific page copy and UI content
-├── data-models/     # Shared TypeScript models for data modules
 ├── layouts/         # Page layouts
-├── pages/           # Routes (file-based)
+├── pages/           # Routes (file-based), ignores folders and files starting with underscore
 └── styles/          # Global styles
 ```
 
@@ -77,22 +74,17 @@ Story conventions (early stage):
 
 ## Customize Branding
 
-The site branding now comes from one source of truth: `src/data/brand.ts`.
+The site branding now comes from one source of truth: `src/pages/_brandConfig.ts`.
 
-1. Open `src/data/brand.ts`.
+1. Open [src/pages/_brandConfig.ts](src/pages/_brandConfig.ts).
 2. Update identity, organization, theme, links, SEO, and blog values.
 3. Keep paths aligned with your configured `base` path in `astro.config.mjs`.
 
-For the complete typed example and current defaults, use `src/data/brand.ts` directly.
+For the complete typed example and current defaults, use `src/pages/_brandConfig.ts` directly.
 
 ## Site Content Pattern
 
-Keep site-specific copy and content in `src/data/`, then import it into `.astro` pages.
-
-- Use `src/data/home.ts`, `src/data/about.ts`, `src/data/blog.ts`, and `src/data/resources.ts` for page-level strings and labels.
-- Keep shared data interfaces in `src/data-models/` (including `src/data-models/brand.ts`).
-- Keep `.astro` pages focused on layout and rendering logic; avoid hard-coded copy in templates.
-- Reuse `src/data/brand.ts` for global identity, SEO defaults, and links.
+Except the brand config, all data is initialized in the header of the `.astro` page files.
 
 ## Redirects After Renaming Pages
 
@@ -114,7 +106,7 @@ Remove the old page file, because file-based routes take precedence over configu
 
 ## Resources Collection
 
-The template includes a `resources` collection at `src/content/resources/`.
+The template includes a `resources` collection at `src/pages/resources/_articles`.
 
 - Use nested paths if helpful (for example `guides/interview-script-template.mdx`).
 - Draft entries (`draft: true`) are excluded from both resources listing and detail routes.
@@ -128,6 +120,10 @@ Supported frontmatter fields:
 
 Schema source of truth: `src/content.config.ts`.
 
+## Blog Articles Collection
+
+Same as resources, but markdown files are located under `src/pages/blog/_articles`.
+
 ## Deployment
 
 Configured for GitHub Pages. Update `astro.config.mjs` with your username: