Awjin

I addressed most comments; printing a nicely formatted report and specs are in flight.

@stof I think read-only module members is an interesting idea, though I'm not sure that guten-type is the most illustrative use-case, since it's a toy project and small in scope....

@jina thoughts on this? I recently looked into migrating this repo onto Github Actions, but I felt like I was just adding more machinery and complexity. The brunt of migrating...

Right. The key advantage of Jekyll is that we don't have to create/maintain any extra build steps, and can just let Github do it for us with minimal configuration. I...

> I'm ok using Jekyll as long as we can use the Dart Sass implementation with it! :) Ah, good point. Since Jekyll uses sassc, we'd have to manually configure...

Thanks for the context. My personal opinion is that regression tests should be added to the *feature*, so that over time the feature specs become more robust. Regardless, the bulk...

Here's a first pass at a new structure for `spec/`, excluding libsass directories. # Current Top-Level Directories ``` basic/ colors/ core_functions/ css/ directives/ errors/ extend-tests/ misc/ mixin/ nesting/ operations/ parser/...

I'm struggling most with the somewhat generic `syntax` folder—could this be made more explicit, or split up even further?

> Something to consider is how we track tests that we think conform well to the style guide versus those that do not. [...] One option would be to design...

This is valid Sass and should compile. What version of Sass are you using? What else are you using to compile your Sass?