You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to convert component docs content to MDX to be able to load it in docusaurus easily.
This meta issue covers components text documentation only, excluding component previews and examples, prop tables, and playgrounds. These code-related elements must be converted to storybook stories first (#6674), then embedded into the MDX files created as deliverables of this meta issue.
Acceptance Criteria
All existing component documentation pages available on the current docs site should be converted to MDX and saved to /website/docs/components/<SNAKE CASE COMPONENT NAME>/overview.mdx
All text content should be converted to MDX, including but not limited to:
headings
paragraphs and text formatting (e.g., emphasis)
links
callouts
inline code
MDX files should be formatted using built-in Markdown features only. Please don't use EUI components, HTML tags, or CSS to achieve custom text formatting
All MDX component docs should have frontmatter defined on top of the file following the format:
Summary
We need to convert component docs content to MDX to be able to load it in docusaurus easily.
This meta issue covers components text documentation only, excluding component previews and examples, prop tables, and playgrounds. These code-related elements must be converted to storybook stories first (#6674), then embedded into the MDX files created as deliverables of this meta issue.
Acceptance Criteria
/website/docs/components/<SNAKE CASE COMPONENT NAME>/overview.mdx
_category_.yml
file created and including these properties:Example directory structure
Content conversion script 👈🏻
You may use a script like this to automatically convert EUI page contents to Markdown.
Converted components
The text was updated successfully, but these errors were encountered: