feat: initialize project structure, Nuxt v4, metadata & project workspace

[toddeTV]

This PR configures the Nuxt v4 environment, streamlines project metadata, and establishes the project and workspace structure. It also introduces sponsoring information and cleans up the initial starter boilerplate.

Summary by CodeRabbit

Release Notes

• New Features

  • GitHub Sponsors funding configuration now available

• Documentation

  • Added sponsorship information and links to README
  • Simplified homepage welcome experience
  • Updated project metadata including description and author information

• Chores

  • Removed demo components
  • Updated project name and enhanced configuration for improved build and development experience

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates project configuration files, adds GitHub sponsorship information, removes demo Vue components (Alert and Counter), and simplifies content files. Package.json is restructured with reorganized dependencies and new development tooling, while nuxt.config.ts expands with enhanced meta tags and TypeScript settings.

Changes

Cohort / File(s)	Summary
Configuration & Build Setup .coderabbit.yml, .npmrc, nuxt.config.ts, package.json, pnpm-workspace.yaml	Package.json restructured with reorganized dependencies, new scripts, and expanded metadata (author, license, repository). Nuxt.config expanded with meta tags, runtimeConfig, and TypeScript settings. .npmrc and .coderabbit.yml updated with new options. pnpm-workspace.yaml adds built dependencies list.
Repository Infrastructure .github/FUNDING.yml, .gitignore, README.md	GitHub Sponsors funding configuration added. .gitignore expanded with AI-related artifact patterns. README.md includes new Sponsoring section.
Component Removals app/components/Alert.vue, app/components/Counter.vue	Two demo components removed: Alert (color-customizable alert box) and Counter (state-based counter with increment/decrement buttons).
Content & Documentation content.config.ts, content/index.md, content/about.md	content/index.md replaced with minimal "Welcome" message under "todde.tv" header. content/about.md deleted entirely. content.config.ts adds file header comment.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content.config.ts (1)

8-15: 🧹 Nitpick | 🔵 Trivial

Consider adding Zod schemas for content validation.

The coding guidelines specify that content collections should use Zod schemas (content.config.ts using Zod), but the current configuration only defines a basic content collection without schema validation. Per the Content Model guidelines, you'll need schemas for: talks, projects, clients, and publications.

This may be intentional for the initial project setup, but consider adding schemas as the content structure is established.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content.config.ts` around lines 8 - 15, Add Zod schema validation to the
content configuration: update the export from
defineContentConfig/defineCollection in content.config.ts to define collections
for "talks", "projects", "clients", and "publications" each with a Zod schema
instead of the catch-all page/source; create Zod schemas (e.g., talkSchema,
projectSchema, clientSchema, publicationSchema) describing the expected
frontmatter fields and types, import them into content.config.ts and pass them
as the schema property to defineCollection for each collection, and keep or
remove the existing "content" collection as appropriate.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@nuxt.config.ts`:
- Around line 7-8: The comment notes `@nuxtjs/seo` is referenced but not added;
update nuxt.config.ts by adding "@nuxtjs/seo" to the modules array (the existing
modules block), install the package (add it to package.json / run package
manager install), and add a top-level site configuration object in
nuxt.config.ts (populate domain, titleTemplate, description, og:site_name,
htmlAttrs.lang and any default metadata/OG settings) so `@nuxtjs/seo` can manage
sitemap, OG images, robots and JSON-LD; ensure the site object names match what
`@nuxtjs/seo` expects and that the module name matches the installed package.

---

Outside diff comments:
In `@content.config.ts`:
- Around line 8-15: Add Zod schema validation to the content configuration:
update the export from defineContentConfig/defineCollection in content.config.ts
to define collections for "talks", "projects", "clients", and "publications"
each with a Zod schema instead of the catch-all page/source; create Zod schemas
(e.g., talkSchema, projectSchema, clientSchema, publicationSchema) describing
the expected frontmatter fields and types, import them into content.config.ts
and pass them as the schema property to defineCollection for each collection,
and keep or remove the existing "content" collection as appropriate.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Lite

Run ID: d7ffd039-db02-4671-a892-1c86eac44611

📥 Commits

Reviewing files that changed from the base of the PR and between 52bb5f1 and c65cd42.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml, !pnpm-lock.yaml

📒 Files selected for processing (13)

• .coderabbit.yml
• .github/FUNDING.yml
• .gitignore
• .npmrc
• README.md
• app/components/Alert.vue
• app/components/Counter.vue
• content.config.ts
• content/about.md
• content/index.md
• nuxt.config.ts
• package.json
• pnpm-workspace.yaml

💤 Files with no reviewable changes (3)

• app/components/Alert.vue
• app/components/Counter.vue
• content/about.md