Howdy,
How do y'all consider which styles are public and private?
Because the ".footer--dark" class uses a hard-coded color and the class will have high specificity, developers cannot easily align the footer component with their product's brand. Developers directly integrating infima, those manually constructing infima components, have an easier time applying their styles with the correct specificity. Docusaurus users swizzle the classic theme Footer/Layout component to apply styles with higher specificity.
Ideally, the footer classes inherit their colors from the default or developer-supplied color theme.
Thank you for the consideration.
|
--ifm-footer-background-color: #303846; |
Example developer workaround:
/* footer.module.css */
.footer {
--ifm-footer-background-color: var(--ifm-color-emphasis-100);
}
[data-theme="dark"] .footer {
--ifm-footer-background-color: var(--ifm-color-emphasis-100);
}
// footer.tsx
import classNames from "./footer.module.css";
const element = (<footer className={clsx("footer", classNames["footer"])}>);
Howdy,
How do y'all consider which styles are public and private?
Because the ".footer--dark" class uses a hard-coded color and the class will have high specificity, developers cannot easily align the footer component with their product's brand. Developers directly integrating infima, those manually constructing infima components, have an easier time applying their styles with the correct specificity. Docusaurus users swizzle the classic theme Footer/Layout component to apply styles with higher specificity.
Ideally, the footer classes inherit their colors from the default or developer-supplied color theme.
Thank you for the consideration.
infima/packages/core/styles/components/footer.pcss
Line 31 in e947edc
Example developer workaround: