4 Commits (faaa4a124ed7a5b2f1cfc8f9b7686a3785d2012b)

Author	SHA1	Message	Date
Divyansh Singh	faaa4a124e	feat(markdown): support per-locale markdown strings ... Strings baked into pages by the markdown renderer can now be overridden per locale via `locales.<index>.markdown` in the site config: container titles (including GitHub-flavored alerts and custom containers) and the code copy button title. Values resolve against `env.localeIndex` at render time and fall back to the root markdown options, so the single shared renderer keeps working unchanged. close #4431 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	962f00e7a3	feat(markdown): support registering custom containers ... New containers can be registered via `markdown.container.customContainers`, mapping a container name to its default title. Registered names work as `::: name` blocks and as GitHub-style alerts (`> [!NAME]`), with custom titles, attributes, and no-title behaving like the built-in types. Styling is left to the theme via `.custom-block.name`. close #3591 close #3603 close #4228 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	4c7a030bc1	feat(markdown): support title-less containers ... A no-title attribute (`::: tip {no-title}`) renders a container without its title element, and the theme reduces the top padding for containers without one. It has no effect on `details`, which always needs its summary. The docs previously hand-rolled this with a raw div and an inline style - those are now switched to the new syntax. close #4928 close #4932 close #4929 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago
Divyansh Singh	420565236b	refactor(markdown): migrate containers to @mdit/plugin-container ... Replaces markdown-it-container and merges the GitHub alerts plugin into the containers module so both share one title map. Rendered output is byte-compatible with the previous implementation. This also restores fence-line attributes on containers ({open}, {.class}, etc.), which broke when markdown-it-attrs was replaced with @mdit/plugin-attrs - its fence rule handled containers too, but had to be disabled to keep code block meta intact. The container plugin now parses the trailing braces itself, so the old markdown-it-attrs patch is not needed in any form. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 weeks ago