8000 What are some inherent constraints of CSS for designers? · Issue #12 · sebdeckers/pfnp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

What are some inherent constraints of CSS for designers? #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sebdeckers opened this issue Sep 3, 2015 · 0 comments
Open

What are some inherent constraints of CSS for designers? #12

sebdeckers opened this issue Sep 3, 2015 · 0 comments

Comments

@sebdeckers
Copy link
Owner

While CSS offers immense flexibility, it is valuable for designers to understand CSS' natural strengths and weaknesses as a medium.

  • Following non-rectangular shapes. Unlike SVG, there is no support for arbitrary paths in CSS, let alone running text along them. At best there are the upcoming CSS Shapes and CSS Exclusions specifications, though they are seldom used. Read more: http://alistapart.com/article/css-shapes-101
  • Blending modes like Photoshop layers. There is mostly basic opacity stacking. Fortunately the Compositing and Blending specification has increasingly broad browser support.
  • The key to a good frontend design is consistency. Think about the many types of design elements across all pages of the app. Reduce them to a reusable set of rules that can be composed together. Avoid many one-off design variations. Less complexity = less problems = better design.
  • Performance budget: Carefully consider the performance envelope of low-end clients like last gen mobile devices or older computers/browsers. Or even users who are running multiple apps/tabs. Keep track of the framerates of animations and transitions and make sure they don't drop below 60 fps in the Performance section of DevTools. Be frugal with computationally expensive effects like box-shadow, border-image, or background-position: fixed. Watch the GPU memory consumption when using hardware accelerated animations and transitions with the transform or opacity properties.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0