Path to v1.0?

[madeleineostoja]

Loving CSS remedy so far as an alternative to Normalize/my own boilerplate, but I'm hesitant to use it in prod with beta warnings everywhere. Is there an agreed upon path to a 1.0 stable release in place? What large pieces still need to be done/tested/are subject to breaking changes?

Seeing as there hasn't been much activity on the repo lately, is it worth releasing the current work as a 1.0? That's what semver is for after all, and if there are breaking changes to come we can just push out a new major version.

[pavsidhu]

If there's anything others can do, I'd love to know how I can help.

[polarathene]

There's a similar project to this one btw, though I haven't compared the two for differences.

sanitize.css is from Jonathan Neal, who co-created normalize.css with Nicolas Gallagher, but deviates from normalize.css by making adjustments to better meet the common expectations/preferences of web developers. Not unlike this project. They also split out styles for typography/forms/page as complimentary additions similar to reminders/quotes in this repo.

Might be viable alternative for you until this project is more confident to drop the warnings?