docusaurus

Pre-flight checklist [X] I have read the Contributing Guidelines on pull requests. [X] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior. [X] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan. Motivation This PR address the concerns brought up in issue #6472, and enforces the use of @theme/IdealImage component instead of tags. Following feedback from @slorber in previous discussions (#8826, #11416), this rule adopts a tiered approach to minimize false positives and noise: Error Tier: Triggered for . Since the asset is explicitly required, we are certain it is a local file that would benefit from the Ideal Image optimization pipeline. Warning Tier: Triggered for static relative paths (e.g., ) or root-relative paths (). This nudges the user to optimize if the file is indeed local. Silent/Ignored:* External URLs () and protocol-relative links (). Dynamic values (e.g., or ) to avoid annoying users in generic components. SVGs: Since does not support vector formats, these are explicitly ignored to prevent useless warnings. Test Plan I have implemented a comprehensive test suite in covering the following: Valid cases: External HTTPS links, template literals with external prefixes, dynamic props/variables, and files. Invalid cases:** Standard `require()srcsetyarn jest packages/docusaurus-eslint-plugin` with all cases passing. Related issues/PRs Fixes #6472 sub-issue Credits to @Devansu-Yadav: this PR builds on the logic and feedback from #8826. Incorporates feedback from #11416 regarding noise reduction and ambiguity.

Have you read the Contributing Guidelines on issues? [x] I have read the Contributing Guidelines on issues. Description This is all the rage now. Example: https://mintlify.com/docs/quickstart Ideally we could have the same options, or a configurable set of LLMs. Considerations: 1. Need to strip comments and images from final markdown before it's exposed to people. 2. Could either load the whole thing into the built page as data on the copy button, or use the mintlify approach of building a clean .md exposed publicly. Has this been requested on Canny? _No response_ Motivation Getting popular in doc systems. API design _No response_ Have you tried building it? _No response_ Self-service [ ] I'd be willing to contribute this feature to Docusaurus myself.

Motivation Our historical syntax is invalid MDX syntax since MDX v2+ (although various MD tools support that syntax for heading ids) This implements an alternative syntax based on comments, and compatible with MDX: For CommonMark, we also support `#{#id}markdown.mdx1Compat.headingIdsdocusaurus write-heading-ids#`) Test Plan CI + unit tests Test links https://deploy-preview-11755--docusaurus-2.netlify.app/