My Scholar 2.2.6 is ready

My Scholar 2.2.6 is a reusable Astro theme for academic profiles, projects, publications, teaching pages, and research blogs. It keeps the source in portable Markdown and the output static by default, while still giving long technical posts a place for equations, code, citations, and notes.1 Markdown remains searchable, reviewable in Git, and reusable in other publishing systems.

What 2.2.6 includes

The release brings the main surfaces of an academic site into one consistent system:

The site uses native HTML and CSS for most interactions. Content collections validate frontmatter before a page is built, so an invalid date or missing required field produces a useful error near the source file.

The release also includes the small details that are easy to miss in a theme:

• Light and dark color modes with an explicit theme toggle
• Responsive navigation and mobile menus
• Shared table-of-contents behavior for blog posts and project pages
• Accessible focus states and reduced-motion fallbacks
• Formatting, linting, Markdown tests, type checks, and production builds
• Replace the demonstration profile and content with your own work

Configure the site

The main configuration lives in src/site.config.ts. A small excerpt looks like this:

1
export const SITE = {
2
  title: "My Scholar",
3
  tocMaxDepth: 3,
4
  home: {
5
    careerHighlightCount: 4,
6
    updateCount: 3,
7
    publicationCount: 3,
8
  },
9
}
10

11
export const NAV_LINKS = [
12
  { href: "/projects", label: "Projects" },
13
  { href: "/publications", label: "Publications" },
14
  { href: "/teaching", label: "Teaching" },
15
  { href: "/blog", label: "Blog" },
16
]

Use src/content/ for the parts that belong to the site owner. Keep reusable layout and component changes in src/ outside the content collections. The repository’s installation guide and customization guide describe the available configuration surfaces.

Write posts in Markdown

The writing pipeline keeps ordinary Markdown at the center. You can combine short prose with emphasis, inline code, descriptive links, and an idea that changed during revision without switching to a custom authoring format.

Add code examples

Fenced code blocks use the language identifier that readers expect from a technical document:

1
type Study = {
2
  title: string
3
  methods: string[]
4
  reproducible: boolean
5
}
6

7
const study: Study = {
8
  title: "Documenting a small research corpus",
9
  methods: ["sampling", "annotation", "review"],
10
  reproducible: true,
11
}

Inline code works in the same paragraph, so names such as tocMaxDepth, pnpm astro check, and src/site.config.ts remain distinct from prose.

Render equations

Inline math keeps a claim compact: the posterior is $p(\theta |D)\propto p(D|\theta )p(\theta )$.

Display math gives a longer expression room to breathe:

The Sätteri pipeline passes both forms to Temml and renders semantic MathML. That keeps equations readable in the browser and available to assistive technology.

Use callouts for context

Directive callouts create expandable notices with a label:

You can also use the Obsidian callout form when you want to move an existing note into the theme:

The {closed} directive attribute starts a callout in its collapsed state:

Link related pages

Wikilinks connect a post to the site’s other collections: project pages, publications, teaching notes, and other research posts. Regular Markdown links remain available for external documentation and sources.

Keep evidence close to the claim

Footnotes become sidenotes on wide screens and compact disclosures on narrow screens.2 Sidenotes keep citations and qualifications near the claim they support while preserving an accessible reading order. This keeps a qualification near the sentence it supports without making the reading order depend on a visual layout.

A useful research note makes its evidence easy to inspect. The page structure should help the reader move from a question to a method, a result, and a limitation.

Model a small research note

Blog frontmatter describes the post, and the body stays in Markdown:

1
---
2
title: A field note about annotation quality
3
createdAt: 2026-08-23T12:00:00
4
tags:
5
  - methods
6
  - reproducibility
7
stage: seedling
8
---

The collections also support project records, people, experience, updates, and BibTeX publications. Use the matching source file for each kind of record:

This separation keeps a publication’s citation data independent from the prose that explains it. It also lets the same project or author appear in several views without duplicating the record.

Upgrade to 2.2.6

If you have an earlier My Scholar site, follow this sequence:

1. Copy your local content and configuration changes before updating the theme.

2. Update the template and dependencies from the v2.2.6 release.

3. Review src/site.config.ts, src/schemas.ts, and the Markdown pipeline for configuration changes.

4. Run the project checks:

   pnpm format
   pnpm lint
   pnpm lint:styles
   pnpm test:markdown
   pnpm astro check
   pnpm build

5. Inspect the home, projects, publications, teaching, and blog routes in both color modes before publishing.

Version 2.2.6 gives you a clear starting point for a personal research site: keep the sample content as a reference, replace it with your own records, and write the parts of the project that deserve a durable explanation.