polaris VS stylelint

We are delighted to announce that the interface of Ryviu account has been updated according to Shopify Polaris. Aligned with Shopify's top-tier standards for safety, performance, and functionality, these changes aim to simplify the process of importing and managing product reviews for your store.

Shopify Polaris: Shopify's Polaris Design System features a color module with primary, secondary, and functional colors, plus an extended palette for shades and tints. Similar to others, it underscores the role of color in conveying meaning, maintaining visual hierarchy, and ensuring accessibility.

shopify design system: https://polaris.shopify.com/

I love the idea because community contributions in OS projects are always super focused on the code aspect while the design work is performed by the core team. Sometimes the results are shared publicly (Cals Design System or Shopify's Polaris)

Currently Im using templates, so my options are kind of limited by that. I cannot do fancy React or Vue apps (would love to tho). My main point of reference is the Polaris design system by Shopify (https://polaris.shopify.com). Simple but efficient.

Learn UX. There are a couple of publicly available design systems out there that give some guidelines about UX: Material Design, Polaris, Human Interface Guidelines.

https://polaris.shopify.com/ - Shopify

Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:

Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase.

The “cost of loading modules” diagram shows non-linear behaviour (though you should largely ignore the curve visible in the diagram because the x axis is way off linear):

• 0.15s ÷ 500 = 0.3ms

• 0.31s ÷ 1000 = 0.31ms

• 3.12s ÷ 10000 = 0.312ms

• 16.81s ÷ 25000 = 0.6724ms

• 48.44s ÷ 50000 = 0.9688ms

My own observation on a Surface Book six years ago was that in Node.js under Windows, each module had about 1ms of overhead when there was warm file system cache—that is, simply bundling with Rollup saved 1ms per file. If this sort of thing interests you, quite a lot of useful stuff came out of https://github.com/stylelint/stylelint/issues/2454 which I filed because I was unhappy with stylelint taking over a second to import. And that must have been only in the order of one or two thousand modules, when the behaviour is still close enough to linear.

As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards.

Document your build process in a blog, use eslint, stylelint and jsx-a11y lint. Run a lighthouse performance test, follow the optimisation reccomendations.

Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities

Stylelint

I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint

The complete code for this project is in the Rodney Lab GitHub repo. I do hope the post has either helped you with an existing project or provided some inspiration for a new one. As an extension, you can add all your favourite future CSS rules to the PostCSS config. Beyond PostCSS for linting your input CSS, consider trying stylelint.