Daniel D. Beck

@wbamberg two questions about fixing CSS page errors, hopefully uncomplicated: 1. Should I remove fixed pages from the spreadsheet? I fixed one (and removed it) but then I thought better...

@wbamberg I finished up the fixable `data.formal_definition` and `data.formal_syntax` pages today. Some conclusions after rerunning the linter against all the CSS pages: * There are six pages which still produce...

I wanted to briefly chime in here: I think the analysis is really good. I like the principles you've selected to selection. I itch a bit a wholly traffic-driven approaches...

> I wonder if things like https://wiki.developer.mozilla.org/en-US/docs/Web/CSS/justify-content#Browser_compatibility are getting caught by the linter because they have a subheading? Yeah, that's exactly what's happening. I brought this up in discussions while...

I can get you an exact number if you like, but there's an upper bound of 78 properties' data files that contain one or more instances of `'"prefix": "-moz-"'` (90...

One little suggestion I wanted to make: a page type identifier proposal ought to speak to versioning (spitballing here, but `javascript-class:1`, etc.). Then when a page spec inevitably changes, the...

Thanks for reporting this, @skcodes. This is closely related to https://github.com/mdn/content/discussions/5549. We don't have a consistent terminology to communicate status (experimental, deprecated, standards-track) and we don't consistently use symbols to...

> Pick a name and stick to it: “Scarf CLI”, “Scarf Environment Manager”, etc. @shlevy, @havi maybe you've got a sense of what the canonical name is already? Or how...

@shlevy Thanks for the naming clarification. That helps a bunch! I was thinking of approaching it by the major headings in the to-do list. I'll open a PR to fix...

OK, first PR is in. Reworking the install and usage instructions with https://github.com/scarf-sh/scarf/pull/23