Building This Website Together with an LLM

I want to create my own web page.
Please help me think through the requirements.
I do not need implementation yet. Please create a requirements document that I can give to Codex.

## Routing idea
- Structure
    - /
        - Self-introduction and routing overview
        - /links
            - External URLs
        - /articls
            - Articles, papers, and similar items
        - /blogs
            - Articles rendered from Markdown

## Implementation requirements
- Use TypeScript and Next.js for a modern React-based UI/UX.
- Use GitHub Pages for a static site to reduce operating cost.
- I do not want to touch code every time I update the blog, so writing Markdown should be enough to build automatically.
- Pages other than Markdown-generated blog pages, such as the home page, should support both Japanese and English.
- The route name "articles" may not be ideal because it will include papers and external technical posts.

# Overview

A requirements definition for a personal website. It uses TypeScript + Next.js for a modern UI/UX, deploys statically on GitHub Pages, and minimizes update cost by rebuilding from Markdown content.

## 1. Purpose / Deliverables

* Purpose: consolidate self-introduction, external links, publication/article references, and blog operations into a static site with minimal maintenance.
* Deliverables: repository, design/components, CI/CD, content templates, and documentation.

## 2. Information Architecture / Routing

* `/`: self-introduction, JP/EN switching, links to major sections
* `/links`: external URLs such as SNS, GitHub, and slides
* `/publications`: papers, external technical posts, and other published work
* `/blogs`: Markdown-based blog index and detail pages

The typo `/articls` should be fixed. For the section name, `/publications` is recommended because it can include papers, contributed posts, and external articles.

## 3. Non-functional Requirements

* Fast rendering with Core Web Vitals in mind
* Accessibility with WCAG 2.1 AA as a target
* SEO with OGP, Twitter Card, structured data, sitemap, and robots
* Responsive design
* Easy operation through Markdown updates

## 4. Stack / Implementation Policy

* TypeScript and Next.js App Router
* Static export for GitHub Pages
* Tailwind CSS and custom UI components
* Markdown parsing with gray-matter, remark/rehype, and zod
* Client-side search and filters where needed

## 5. i18n

* Static UI such as the home page should support Japanese and English.
* Use a URL prefix or similar mechanism to preserve language.
* Japanese is the default language.

## 6. Content Design

Blog frontmatter should include `title`, `date`, `updated`, `tags`, `summary`, `thumbnail`, and `draft`.

Publication frontmatter should include `title`, `type`, `publishedAt`, `venue`, `publisher`, `authors`, `links`, `tags`, and `abstract`.

## 7. Build / Deploy

Use GitHub Actions to build on push to the main branch and deploy the `out/` directory to GitHub Pages.

## 8. Acceptance Criteria

* Adding a Markdown article and merging to `main` automatically builds and deploys the site.
* `/` supports ja/en switching, and `/blogs` can publish articles from Markdown only.
* `/publications` filtering and search work on the client.
* LCP/CLS/INP goals are checked in lab tests.
* Basic accessibility checks pass.