Move all inline styles to dedicated CSS/SCSS files to improve maintainability, consistency, and separation of concerns. Inline styles make components harder to maintain, reduce reusability, and violate the principle of separating presentation from logic.
Move all inline styles to dedicated CSS/SCSS files to improve maintainability, consistency, and separation of concerns. Inline styles make components harder to maintain, reduce reusability, and violate the principle of separating presentation from logic.
Instead of using inline styles:
// ❌ Avoid
<div style=>
<span style=>
Status
</span>
</div>
// ❌ Avoid
<Typography.Paragraph
style=
>
Create proper CSS classes:
// ✅ Preferred
.status-container {
display: flex;
align-items: center;
gap: 8px;
.status-text {
color: white;
font-size: 14px;
}
}
.login-prompt {
color: var(--text-vanilla-300);
font-style: italic;
}
// ✅ Preferred
<div className="status-container">
<span className="status-text">Status</span>
</div>
<Typography.Paragraph className="login-prompt">
This approach enables better theming, easier maintenance, improved performance through CSS caching, and cleaner component code that focuses on logic rather than presentation details.
Enter the URL of a public GitHub repository