docs: clean up inline styles in documentation

[codewithzubair07]

What changed

• Removed inline styles from multiple MDX documentation pages
• Replaced them with class-based styling to avoid mixed styling approaches

Why

• Improves consistency and maintainability of docs styling

Closes #744

[DeveloperAlly]

Apologies, I should have been clearer.

Details

-b docs-v2 houses styles in /snippets (multiple custom components), inline on pages themselves (under v2/pages) and in styles.css(root).

The old documentation is being fully replaced by the docs-v2 branches (most up to date currently being docs-v2-preview branch).

I'm not a style expert, but I understand you can use either tailwind (I haven't as I hadn't used it before and had enough learning curbs here :P) or otherwise you are limited to using the styles.css file in root (cannot create multiple of these ie. per page/grouping), or by styling inline on pages (.mdx) or in components (.jsx).

My thought is that:

• 1. Firstly this information should be verified Mintlify Docs

Thoughts on homogenous style framework

If true

• 1. Global styles and overrides should be housed in styles.css
• 2. Components must have styles defined within the component themselves
• 3. No page should have inline styles: either the style is converted to a component or it uses a global style className.

Sorry for the misunderstanding here.

[codewithzubair07]

Apologies, I should have been clearer.

Details

-b docs-v2 houses styles in /snippets (multiple custom components), inline on pages themselves (under v2/pages) and in styles.css(root).

The old documentation is being fully replaced by the docs-v2 branches (most up to date currently being docs-v2-preview branch).

I'm not a style expert, but I understand you can use either tailwind (I haven't as I hadn't used it before and had enough learning curbs here :P) or otherwise you are limited to using the styles.css file in root (cannot create multiple of these ie. per page/grouping), or by styling inline on pages (.mdx) or in components (.jsx).

My thought is that:

• 1. Firstly this information should be verified Mintlify Docs

Thoughts on homogenous style framework

If true

• 1. Global styles and overrides should be housed in styles.css
• 2. Components must have styles defined within the component themselves
• 3. No page should have inline styles: either the style is converted to a component or it uses a global style className.

Sorry for the misunderstanding here.

Thanks for clearing that up — that makes sense now
I’ll switch over to the docs-v2-preview branch and focus on tidying up styles in the v2 pages. I’ll try to reduce inline styles and move things into shared styles or components where it feels right, keeping Mintlify’s quirks in mind.
I’ll open a new PR once I’ve got a decent clean pass. Let me know if there’s anything specific you’d like me to look at first!