Richard Hallows

> But if so, we must discuss how to decide and operate the policy If we have a guiding principle, we can use our judgement case-by-case rather than have a...

Thanks for pointing out the usage relative view on caniuse. I wasn't aware of it until now. It's definitely a good tool to help us judge!

> It is easy for users if you can say : "we use Baseline as a guide when adding new rules" because over time there will be shared understanding of...

Thanks for the request and for using the template. The rule intentionally only supports numerics font weights because they play well with variable fonts and we can do a naive...

That'd be fantastic. You're welcome to open an early work-in-progress pull request as I can help you. The rule will still expect an array of numbers, but 400 and 700...

If you weren't already aware of it, I think the [`declaration-block-properties-order`](http://stylelint.io/user-guide/rules/declaration-block-properties-order/) rule is what you're after: ``` js { "rules": { "declaration-block-properties-order": "alphabetical" } } ```

Yes, I believe so. It's okay to have overlapping rules. If possible, those rules should have secondary options so that they can be used together, where appropriate.

I'm catching up on discussions I missed over the summer... Shall we go with small and separate rules, as each rule may check different areas? For example, the `custom-property-pattern` rule...

Closing as sub-issues are complete, thanks to everyone's contributions.

Looks like it was fixed upstream: