add thesis page and sample projects

[PominovaMS]

What does this PR change?

Checklist

• npm run format:check passes (or run npm run format to auto-fix)
• npm run lint passes
• npm run build succeeds locally
• Profile photo added to public/profile-images/ (if applicable)
• BibTeX entry added to src/data/publications.bib (if applicable)

Summary by CodeRabbit

• New Features
  • Added a dedicated Thesis page with project topics, application guidance, deadlines, and contact options.
  • Added support for rendering static Markdown pages through dynamic routes.
• Style
  • Improved Markdown page headings with spacing, borders, and visual separation.
• Documentation
  • Updated project documentation to reflect the new static pages structure and content.

[coderabbitai]

Warning

Review limit reached

@manuelkuss, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf9d2a6b-fffd-4265-bbda-dd244ebafa10

📥 Commits

Reviewing files that changed from the base of the PR and between 411dd40 and 7d735cb.

📒 Files selected for processing (4)

• CLAUDE.md
• README.md
• src/content.config.ts
• src/styles/global.scss

📝 Walkthrough

Walkthrough

The thesis content is moved into a generic pages collection, served through a new dynamic [slug].astro route. The former thesis-specific route is removed, documentation is updated, and markdown headings receive additional styling.

Changes

Static Markdown Pages

Layer / File(s)	Summary
Pages collection and thesis content src/content.config.ts, src/content/pages/thesis.md	Defines and exports a title-based pages collection containing the new thesis markdown page.
Dynamic page route and rendering src/pages/[slug].astro, src/styles/global.scss	Generates static routes from the pages collection, renders markdown through BaseLayout, and styles markdown h1 and h2 headings.
Documentation and legacy route cleanup CLAUDE.md, README.md, src/pages/thesis.astro	Documents the pages collection and removes the former thesis-specific route.
Estimated code review effort: 2 (Simple)	~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Build as Astro build
  participant Collection as pages collection
  participant Route as [slug].astro
  participant Layout as BaseLayout
  Build->>Collection: Load pages entries
  Collection->>Route: Map entry IDs to slug routes
  Route->>Route: Render page content
  Route->>Layout: Pass rendered content and title

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is only the template placeholder and does not describe the actual changes or fill the checklist.	Add a brief summary of the thesis page/content changes and complete the checklist items that were verified.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: adding a thesis page and related sample-project content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch thesis-info-section

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

src/pages/[slug].astro (1)

13-14: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider typing Astro.props for better TypeScript support.

Since the repository uses TypeScript strict mode, you can explicitly type Astro.props by inferring it from getStaticPaths. This ensures that the page prop and its data are correctly typed within the component. As per coding guidelines, TypeScript strict mode should be utilized for .astro files.

💡 Proposed refactor

-const { page } = Astro.props;
+import type { InferGetStaticPropsType } from 'astro';
+
+type Props = InferGetStaticPropsType<typeof getStaticPaths>;
+
+const { page } = Astro.props as Props;

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/`[slug].astro around lines 13 - 14, Type the Astro.props
destructuring in the page component using the prop type inferred from
getStaticPaths, so page and its data are checked under strict TypeScript rules
while preserving the existing render(page) flow.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/pages/`[slug].astro:
- Around line 13-14: Type the Astro.props destructuring in the page component
using the prop type inferred from getStaticPaths, so page and its data are
checked under strict TypeScript rules while preserving the existing render(page)
flow.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 632bf13a-44bd-4cb8-ba4c-f1962eb44d64

📥 Commits

Reviewing files that changed from the base of the PR and between 39ebb18 and 411dd40.

📒 Files selected for processing (7)

• CLAUDE.md
• README.md
• src/content.config.ts
• src/content/pages/thesis.md
• src/pages/[slug].astro
• src/pages/thesis.astro
• src/styles/global.scss

💤 Files with no reviewable changes (1)

• src/pages/thesis.astro