3 ms·
Lol how do people get this good at css. Whenever I get a css ticket at work I inevitably find myself in the chrome inspector twiddling levers and switches until
by komali2 10y ago
Lol how do people get this good at css. Whenever I get a css ticket at work I inevitably find myself in the chrome inspector twiddling levers and switches until it looks juuuuust right... And then doing it all over again in a day after QA kicks it back with a "misaligned on Firefox" comment
- Raphmedia 10y agoI have a Diploma of College Studies (Canada) in Multimedia Integration. We learned how to create animations, how to render 3D models, how to do videos editing, how to do web front-end (advanced css + js), how to do backend web programming and how to create native apps. It's a lot easier to be good at css when you actually learn it from teachers.
- johnhenry 10y agoIn the past, the hardest thing about learning CSS had little to do with the language itself, but in dealing with inconsistencies for specific browsers (like "Firefox", as mentioned). Recent efforts by browser manufacturers to render CSS in accordance with standards, along with the advent of pre/post-processing tools, have made it easier for developers to focus on the language.
- komali2 10y agoFair, I've only been doing this a year, my older colleagues laugh strangely whenever I complain about browser inconsistencies. I'm of the understanding I live in a quite different world :P
- markdown 10y agoDesigning for email today (Outlook renders emails with Microsoft Word!!) is only a tiny bit more painful than what designing for the web used to be.
- devrelm 10y agoThis one isn't actually /too/ complicated. It certainly uses some advanced techniques -- transitions, clip-paths, nth-child -- and I'm not sure (haven't checked) if or how it works in browsers other than Chrome, but the fact that you _know_ you'll have 30 shards greatly simplifies everything. If you can have a designer draw up the basic design, then you can one-by-one take the shards & put them into place with CSS. From there you can set up some animations on specific shards to make it seem like everything's moving together. From there, you basically have one animal. It'd be time-consuming, but would work. The css selector for a particular animal's shards start with a `.<animal>` class selector, so that you change the animal class in a parent and all the shards move into place. It looks like they're still using some javascript to set "states", which seem to trigger animations. I'm honestly not sure why they decided to do that rather than just using keyframes with animations, though I imagine that it may have been that animations were firing before the transition between animals finished, which would have caused a little bit of weirdness.