Tag: We’re

Let’s Say You Were Going to Write a Blog Post About Dark Mode

This is not that blog post. I’m saying let’s say you were.

This is not a knock any other blog posts out there about Dark Mode. There are lots of good ones, and I’m a fan of any information-sharing blog post. This is more of a thought exercise on what I think it would take to write a really great blog post on this subject.

  • You’d explain what Dark Mode is. You wouldn’t dwell on it though, because chances are are people reading a blog post like this already essentially know what it is.
  • You’d definitely have a nice demo. Probably multiple demos. One that is very basic so the most important lines of code can be easily seen. Perhaps something that swaps out background-color and color. The other demo(s) will deal with more complex and real-world scenarios. What do you do with images and background images? SVG strokes and fills? Buttons? Borders? Shadows? These are rare things that sites have, so anyone looking at designing a Dark Mode UI will come across them.
  • You’d deal with the fact that Dark Mode is a choice that can happen at the operating system level itself. Fortunately, we can detect that in CSS, so you’ll have to cover how.
  • JavaScript might need to know about the operating system choice as well. Perhaps because some styling is happening at the JavaScript level, but also because of this next thing.
  • Dark Mode could (should?) be a choice on the website as well. That servers cases where, on this particular site, a user prefers a choice opposite of what their operating system preference is.
  • Building a theme toggle isn’t a small job. If your site has authentication, that choice should probably be remembered at the account level. If it doesn’t, the choice should be remembered in some other way. One possibility is localStorage, but that can have problems, like the fact that CSS is generally applied to a page before JavaScript executes, meaning you’re facing a “flash of incorrect theme” situation. You might be needing to deal with cookies so that you can send theme-specific CSS on each page load.
  • Your blog post would include real-world examples of people already doing this. That way, you can investigate how they’ve done it and evaluate how successful they were. Perhaps you can reach out to them for comment as well.
  • You’ll be aware of other writing on this subject. That should not dissuade you from writing about the subject yourself, but a blog post that sounds like you’re the first and only person writing about a subject when you clearly aren’t has an awkward tone to it that doesn’t come across well. Not only can you learn from others’ writing, but you can also pull from it and potentially take it further.
  • Since you’ll be covering browser technology, you’ll be covering the support of that technology across the browser landscape. Are there notable exceptions in support? Is that support coming? Have you researched what browsers themselves are saying about the technology?
  • There are accessibility implications abound. Dark Mode itself can be considered an accessibility feature, and there are tangential accessibility issues here too, like how the toggle works, how mode changes are announced, and a whole new set of color contrasts to calculate and get right. A blog post is a great opportunity to talk about all that. Have you researched it? Have you talked to any people who have special needs around these features? Any experts? Have you read what accessibility people are saying about Dark Mode?

That was all about Dark Mode, but I bet you could imagine how considering all these points could benefit any blog post covering a technical concept.

The post Let’s Say You Were Going to Write a Blog Post About Dark Mode appeared first on CSS-Tricks.

CSS-Tricks

, , , , , , , ,

What We’re Reading, 2019

There are so, so, so (so) many things to read out there on the internet. So many, in fact, that it’s difficult to keep up with everything.

But, hey, we’ve got your back! It’s our job to surface the best of the best and share it with you right here. That’s why it’s a good idea to subscribe to this site and newsletter. Why subscribe to hundreds of sites when you can follow one, right?

Where do we find the links that we share? It truly runs the gamut, but we’ve decided to list our favorite sources.

Chris Coyier

  • Labnotes – Assaf Arkin’s newsletter is great mishmash of timely, interesting, and funny tidbits with a developer twist.
  • Code with Veni is new just this year and consistently has great links from underrepresented coders
  • Codrops Collective always leaves me with like five open tabs
  • I get quite a few weekly newsletters entirely about front-end development, like Friday Frontend
  • WordPress Tavern does solid WordPress journalism.
  • Shoutout to Dave who had a strong year of bloggin’.
  • I love longtime classic blogs, like Waxy Waxy, Kottke, and Daring Fireball
  • DEV is blowing up and I end up reading many articles there each week. Meanwhile, it feels like Medium is slowing down significantly when it comes to developer-focused writing.
  • I obviously look at CodePen every day, which helps me keep an eye on what front-end developers are playing with.
  • I’d say the main value I get from Twitter is getting great links and thoughts that are a smidge beyond my regular reading. I’m in some community Slacks too, but find it far more conversational and less link-heavy.

Sarah Drasner

  • Scotch.io consistently has great stuff for pretty much every tech stack you can think of. They also do a great job of finding new authors.
  • Cassidy William’s newsletter is short and sweet, and has coding puzzles in every issue.
  • I really love PonyFoo’s quality and style. They mix it up and keep it interesting. The design is nice and unique as well!
  • I’m a Vue core team member and love to keep on top of what’s going on in the community with the Vue Newsletter. It’s curated by a team of really passionate educators and it shows — every newsletter is well curated.
  • I love Data Sketches so very much. It’s a brilliant collaboration between Shirley Wu and Nadieh Bremer, and shows exceptional mastery of technical and illustrative skillsets to convey data. Worth a read for sure.
  • Like Chris, I love Codrops Collective. You can learn so much about UX animation there.
  • Speaking of animation, Val Head has a wonderful UI Animation Newsletter. She’s kept it up for years, and it’s rich with resources from the fanciful to the practical.
  • Rachel Andrew has been the editor-in-chief of Smashing Magazine for the past year or so, and the content has been wonderful. Smashing is constantly a source of great articles and information about front-end development and design.
  • I just saw Jared Palmer’s Blog a week ago and I really enjoy the writing there. It’s informative, interesting and humorous.
  • Our own Robin Rendle has a great newsletter all about typography. I don’t know that much about type, so the poetic deep dives are lovely and informative. It’s great for die-hard fans and newbies alike!

Geoff Graham

  • W3C Cascading Style Sheets Feed – Getting news straight from the horse’s mouth!
  • CSS {In Real Life} – Michelle Barker is has a pragmatic approach to CSS and does an excellent job explaining complex concepts in a way that’s pretty easy to grok.
  • The History of the Web – This is probably the opposite of “late-breaking” news, but Jay Hoffman’s newsletter tells yesteryear’s stories of the web, which is great context for things we see evolving today.
  • CodePen Post Picks – CodePen is full of great minds sharing ideas and the team over there does an excellent job curating noteworthy posts.
  • RWD Weekly Newsletter – Justin Avery covers responsive design news (obviously) but also provides oodles of other front-end-related goodies.
  • The Work Behind the Work – This isn’t front-end stuff but I like how this site documents the creative process behind famous works that we know and love.
  • Adactio – Jeremy Keith posts regularly and thoughtfully.
  • Bruce Lawson – He usually has a weekly link dump that I find useful for uncovering things that would otherwise slip under my radar.
  • Mozilla Hacks – I could just as easily link up to other browser news, but Mozilla seems to be innovating fast and I like seeing where they’re headed.
  • Piccalilly Newsletter – Andy Bell collects awesome demos.

Robin Rendle

  • Ire Aredinokun’s blog Bits of Code is an endless treasure trove of information about front-end development best practices and each post makes me ooo and Alice with delight.
  • For type and design news I always keep an eye out for Typographica’s year in review, and this year’s edition is just as interesting as the others. They collect a ton of typeface reviews from the releases of the past 12 months and explore what makes each design tick.
  • Likewise, David Jonathan Ross’s Font of the Month Club is essential reading for designers. David gives provides a typeface that’s a work in progress in each issue and then writes diligently about the process behind it. It’s always a wonder.
  • Tim Kadlec’s blog is a great source of info about accessibility, web performance and general front-end development news.
  • I’ve been reading a bunch of great newsletters lately and Chip Scanlan’s writing advice is one that certainly stands out from the crowd.
  • Adrian Roselli’s blog never fails to impress with a ton of deep-dives into some obscure front-end problem or issue I’ve never heard about before.

Where do you look to stay updated? Share your list of favorites with us!

The post What We’re Reading, 2019 appeared first on CSS-Tricks.

CSS-Tricks

, ,
[Top]