[Bug report] Improve visibility / discovery of the "Custom Container" (:::) syntax feature

[polarathene]

Description

Your docs page doesn't seem to mention the syntax for admonition/aside/alert (name varies based on docs generator):

I am referring to the Tip section at the bottom there, where inspecting the source reveals the syntax:

docs/docs/guide/markdown.md

Lines 20 to 28 in 3b0eefe

	### Header Anchors
	You might have noticed that, a `#` anchor is displayed when you hover the mouse on the headers of each section. By clicking the `#` anchor, you can jump to the section directly.
	::: tip
	This header anchors extension is supported by [markdown-it-anchor](https://github.com/valeriangalliat/markdown-it-anchor).
	Config reference: [markdown.anchor](../reference/config.md#markdown-anchor)
	:::

It's a common feature that I assume is available by default with VuePress (never used the project myself), so might be worth documenting. If it is documented somewhere I had trouble identifying where.

---

EDIT: I found it documented separately for the theme itself as "Custom Container" markdown syntax: https://ecosystem.vuejs.press/themes/default/markdown.html#custom-containers

Since your docs are showing that feature off quite a bit, might be worth referencing that more directly to the audience that is likely to be interested in the feature (searching for ::: or similar common words for the syntax/type doesn't really help).

[Mister-Hope]

Can you open a pr from a user sight of view? Only en is ok, if we think this is good, I will sync zh docs.

[polarathene]

Can you open a pr from a user sight of view?

No sorry, I'm not a VuePress user.

I reported this when I came across it while writing this reply on another project. I link to the equivalent feature in other doc generators, you could reference those.

[meteorlxy]

It used to be in the core in v1, but it would require all themes to implement styles for custom containers, which is not necessary, so we moved it into theme scope. But yes, as it's a widely used syntax, we may consider integrating it into core again, or move the docs back to core (just like the markdown code extensions)

[github-actions]

This issue is marked as stale because it has not had recent activity. Issues marked with stale will be closed if they have no activity within 7 days.

[github-actions]

This issue is marked as stale because it has not had recent activity. Issues marked with stale will be closed if they have no activity within 7 days.