CSS Remedy vs Normalize.css which one should I use?

CSS Remedy is a philosophical reset that overrides browser defaults with modern values, while Normalize.css focuses on normalizing inconsistencies without opinionated changes. Choose Remedy for forward-thinking projects; use Normalize for minimal interference with existing styles.

How to integrate CSS Remedy into my project?

Link the core `remedy.css` file in your HTML head, then optionally add modules like `reminders.css` based on your needs. Since it's early-stage, test thoroughly and be prepared to adjust your CSS to accommodate its overrides.

Does CSS Remedy break existing styles?

Yes, it intentionally overrides browser defaults, which can break styles that rely on those defaults. Review the remedy files and adjust your CSS accordingly, especially if migrating an existing project.

What browsers does CSS Remedy support?

It actively supports modern browsers and IE11, with non-urgent fallbacks for older browsers. However, it doesn't polyfill new features, so some modern CSS defaults may not work in legacy environments.

Is CSS Remedy stable for production?

No, the README warns it's not ready for production use due to its early development stage. Wait for stable releases or use established resets like Normalize.css if stability is critical.

How to customize CSS Remedy modules?

Use the modular approach: start with the core `remedy.css`, then selectively include optional files like `reminders.css` or edit the source CSS directly to tailor overrides to your project's requirements.

Open-Awesome

CSS Remedy

MPL-2.0CSS

A CSS reset that modernizes browser defaults by applying what CSS would look like if designed today without backwards compatibility.

GitHub

2.2k stars113 forks0 contributors

What is CSS Remedy?

CSS Remedy is a modern CSS reset stylesheet that addresses the technical debt of CSS by updating browser defaults to reflect contemporary best practices. It provides a foundation for web projects by overriding outdated user agent styles with more sensible, modern defaults, allowing developers to start from a cleaner slate.

Target Audience

Web developers and designers building new projects who want a modern, philosophical reset of browser defaults without the constraints of backwards compatibility.

Value Proposition

Developers choose CSS Remedy over alternatives because it sets CSS properties to values the CSS Working Group might choose if designing CSS from scratch today, moving beyond historical browser quirks to establish more logical defaults.

Overview

Start your project with a remedy for the technical debt of CSS.

Use Cases

Best For

Starting new web projects with a modern CSS foundation free from legacy browser inconsistencies.
Overriding outdated user agent styles with contemporary best practices in CSS.
Applying a philosophical reset that leaves behind historical reasoning like 'because that's what Mosaic did'.
Using a modular approach with core and optional files for tailored styling needs.
Supporting modern browsers while providing reasonable fallbacks for older ones without polyfills.
Building on a living project that evolves with CSS standards and community contributions.

Not Ideal For

Projects requiring a stable, production-ready CSS reset with long-term support guarantees
Teams that rely heavily on existing browser default styles or third-party CSS frameworks without modification
Legacy applications needing full backward compatibility with older browsers beyond IE11

Pros & Cons

Pros

Modern Philosophical Foundation

Sets CSS properties to values the CSS Working Group might choose if designing CSS today, explicitly moving beyond historical quirks like 'because that's what Mosaic did,' as cited in the README.

Modular and Tailorable

Provides a core `remedy.css` for broad use and optional files like `reminders.css` for situational overrides, allowing developers to pick and choose remedies based on project needs.

Browser-Agnostic with Fallbacks

Focuses on modern browsers while offering reasonable fallbacks for older ones like IE11 without polyfilling new features, as outlined in the browser support section.

Community-Driven Evolution

Encourages contributions and is described as a 'living project' in the README, ensuring it evolves with CSS standards and community input.

Cons

Early Development Stage

The README explicitly states it's 'too early to distribute' and 'have a ways to go before it's really ready to use,' making it unstable for production environments.

Opinionated Overrides

Fundamentally changes browser defaults, which may conflict with existing CSS or require additional adjustments when integrating with third-party components or frameworks.

Limited Stability Guarantees

As a new project, it lacks comprehensive testing and versioning, increasing the risk of breaking changes that could disrupt ongoing development.

Frequently Asked Questions

Related Projects

modern-css-reset

A bare-bones CSS reset for modern web development.

Stars2,962

Forks421

Last commit2 years ago

inuitcss

Extensible, scalable, Sass-based, OOCSS framework for large and long-lasting UI projects.

Stars1,845

Forks202

Last commit3 years ago

Centurion

Web-based framework for rapid prototyping and building larger web projects. Docs, Repo

Quickly build and design new UI without writing CSS. Demo, Docs, Repo | #CSS