Pick date

This is a preview. All links and Twitter names have been removed. The full version of this content can be accessed only by patrons of this digest (after signing in). Become a patron by subscribing for $6/month.

WPD 421: Designer-oriented features coming to Chrome DevTools, modernizing the W3C’s tooling

  • Posts

    • @……… announces (upcoming) designer-oriented features in Chrome DevTools, post
      • “…real-time typography and layout audits that automatically prevent common mistakes such as mixed fonts or tiny margins, and a powerful flex assistant that makes working with Flexbox as intuitive as it should be.”
  • Info

    • 82% of screen reader users use their screen readers on a mobile device, source
    • @………: The goal of WHATWG documents is to “reflect where all implementations will converge”, post
      • “It should not describe today’s implementations as that will not lead to convergence. […] And it should not describe an unreachable ideal, e.g. by requiring something that is known to be incompatible with web content.”
  • Content

    • @………: “We need an energetic rethink of the W3C’s tooling […] to stay relevant to our users”, doc
      • “A common library should be developed to provide basic functionality across all specifications. This would include simple, streamlined bug reports from within the document. […] We could expose a searchable interface that would make it possible for people to find which specification defines what, and which make use of what concept…”
  • Demos

    • An elastic sidebar effect (achieved by animating an SVG <path> with JS), @………’s demo
    • Responsive, touch-friendly carousels with Flickity, @………’s post + demo (for testing on mobile)

  • Other

    • Angular 2 will be built with TypeScript, @………’s post + new site
    • CSS transitions vs animations (what they are and when to use them), @………’s post
    • @………’s style sheet for creating animated 3D cubes, demos
    • Firefox 38 adds support for ruby annotations (ciu), incl. CSS Ruby (spec), @………’s post

Select a release using the controls above.

RSS feed

Use this feed as a reminder to visit every day

@openwebdaily

2–3 tweets/day (the best stuff from each release)

GitHub repo

Use this repo to submit issues with the site

Subscriber features

(Yeah, this part still needs to be rewritten, haha…) Become a patron of this digest for $6/month and you will (1) gain access to past releases, (2) get the option to receive dailies via email. More features coming later this year!

Payment options

  • Automatic monthly payment

  • One-time payment (½ or 1 year)

Note: PayPal only. (Other providers are not available in my country.) If you don’t want to have your credit/debit card connected to PayPal, you can just disconnect it immediately after making an one-time payment.

Notable subscribers

  • Keeping up with the ever-changing web is hard. Web Platform Daily is one of my favorite ways to do that and my absolute favorite format: simple, distilled, curated, and reliable.

    Chris Coyier’s avatarChris Coyier, designer at CodePen, writer at CSS-Tricks

  • Web Platform Daily is a fantastic way to stay on top of the latest front-end techniques, tools and resources. Very, very valuable.

    Vitaly Friedman’s avatarVitaly Friedman, editor-in-chief of Smashing Magazine

  • Web Platform Daily has quickly become not only an essential resource, but the essential resource. Nowhere else will you keep pace with the changing frontend landscape.

    Paul Irish’s avatarPaul Irish, developer advocate at Google

Open Web Platform Daily Digest

released Mon–Fri at 7 a.m. UTC
curated by Šime Vidas (Twitter, Gmail)
supported by 139 patrons (view list)