luxlogica

OS UI guidelines are comprehensive, ever-changing, and extremely opinionated - eg., they usually specify typography for all text elements, but these settings might change (a little or a lot) with...

There are indeed a number of solutions available - including [sanitize.css](https://csstools.github.io/sanitize.css/), and the highly opinionated [Bootstrap Reboot](https://getbootstrap.com/docs/4.0/content/reboot/) - all of which build upon normalize.css, by adding further normalisations (which, apparently,...

Yes, indeed I do - as do lots of other people. Saying that providing a standard styling for form elements is ‘opinionated’, but that providing a standardised typography for every...

I agree - unfortunately, as there has been no official update since 2018, and the project feels very stale, and somewhat outdated. The appearance and proliferation of so many other...

Latest discussion: https://github.com/necolas/normalize.css/issues/729 The main discussion seems to have taken place almost 4 years ago: https://github.com/necolas/normalize.css/issues/646 In the old discussion, one of the normalize authors dismisses the whole idea of...

@sindresorhus there are currently 2 ways to setup a 'starting point' in a CSS project: 1. you start with NO SETTINGS for anything - no styles, no default, and the...

@sindresorhus not for inline text elements - and even for block elements, we also have margins, paddings, and other settings. For the designer/developer, the only difference is that the settings...

@mkllnk would truly love to contribute, but my shell scripting skills are not up to the task... :(

This is particularly relevant now when comparing with Yarn 2 (issue #31). Yarn 2 compresses the installed packages by a lot, but we still get duplication - in order to...

We often do article page layouts, where the body content is broken down into sections (blocks) that vary in the **number of columns**, and their content type. For example: At...