Image guidance for DS

[zarahzachz]

Conversation came up in Slack.

Questions:

• Shouldn’t sites have image compression
  • CI/CD actions?
  • Akamai/imgix?
• Would an image component help?
  • Built-in skeleton (loading) state
  • lazy-loading attr baked in
• Intersection Observer
  • Detail use?
  • Distribute some kind of reusable code? Might prove difficult for page layouts as DS covers more granular patterns

[zarahzachz]

Reminds me of the post GH wrote on releasing performant images

[danbivins]

Adding a "performance" section on the doc site could be useful to cover various topics.

Is there any downside to creating an image component?

[zarahzachz]

One I can see is if we introduce skeleton (or loading) states in our components, it opens the floodgates to other components also needing this loading effect. Skeleton states tend to be animation heavy based on how they are implemented, which can lead to performance issues or excessive motion on the website. All workable issues, but worth calling out here.