docs: Stylelint declaration-block-no-redundant-longhand-properties

[nschonni]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make?

Enable the rule, and manually combine the 2 properties into the shorthand https://developer.mozilla.org/en-US/docs/Web/CSS/flex-flow

Is there anything you'd like reviewers to focus on?

[netlify]

✅ Deploy Preview for docs-eslint ready!

Name	Link
🔨 Latest commit	498e20c
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/6366d92a9d720200089f3922
😎 Deploy Preview	https://deploy-preview-16499--docs-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[snitin315]

Not sure if we should restrict this behavior. I would like to hear more opinions from @eslint/website-team

[kecrily]

I prefer not to use shorthand because longhand properties are more explicit for people who don't particularly know css or suddenly forget the order in which shorthand properties correspond.

---

But this will obviously also increase the size of the css file, but for now it's just a little bit for us. Or could we use postcss to merge them?

[snitin315]

I prefer not to use shorthand because longhand properties are more explicit for people who don't particularly know css or suddenly forget the order in which shorthand properties correspond.

Yeah, I feel the same here. Let's close this one.

But this will obviously also increase the size of the css file, but for now it's just a little bit for us. Or could we use postcss to merge them?

@kecrily There is a PR for PostCSS, you may want to review #16502