In this fantastic video from the Webstock ’13 conference, Mike Monteiro shows that designers need to take responsibility for their actions. There are many things I touched on with my article Be Proud to be a Web Developer from almost a year ago, and it’s worth watching. From the description:
You are directly responsible for what you put into the world. Yet every day designers all over the world work on projects without giving any thought or consideration to the impact that work has on the world around them. This needs to change.
[… M]ethodologies [like OOCSS and BEM] attempt to apply the principles of Object-Oriented Programming to CSS. Notwithstanding the conceptual incompatibilities between a declarative style language and object-oriented software design principles, these methodologies introduce subtle problems which may not be immediately obvious to less-experienced developers. Most disconcertingly, these methodologies have seen widespread adoption thanks to prominent bloggers evangelising their usage as ‘best practice’.
While OOCSS classes may be understood by programmers and HTML novices, they put the design into HTML, it is the <font>-Element all over again. Little gain for complex HTML. True object oriented CSS has the objects in the CSS through SASS, rather than in HTML.
I don’t say “Don’t use classes!” but try to describe the content. A table with the class products can easily be made striped and narrow in SCSS:
Don’t want the product tables striped: Change one line in your SCSS. With OOCSS you’d have to go through every HTML template and remove the class “table-striped”. If narrow tables aren’t in the style guide after a redesign, remove one line (inside %table-narrow) and boom, all your tables aren’t narrow anymore. Same if the narrow style changes. It’s one change in one file (probably an included _table-styles.scss) and not searching through many template and HTML snippet files to change it.
Christian Heilmann shows an inspiring speaker from Spain, Luz Rello, who talks about the often overlooked topic of accessibility: Dyslexia. In the TEDx talk she really is very passionate about the topic and it shows, and I agree with Chris that we need more Speakers who can actually show their passion for a topic.
I’ve been sitting through a lot of bad accessibility presentations, some with weird and confusing slides. But I personally think that accessibility and passion go together hand in hand, I don’t think that those people were unemotional about the topic. Actually I think they are so involved in their topic that they want to put everything into the presentation and thus fail to articulate themselves better and articulate their passion better.
After successfully testing Webmentions (a new form of the old Trackback or Pingback mechanisms), Jeremy Keith shows how to parse the content of the sites linking back to display excerpts of their comments:
The next step is to do something with the responses. After all, I’ve already got the source of each response from those cURL requests [to verify that the URL contains a back link as it claims].
[…] I’m using [a microformats parser in PHP] to check the cURLed source for any responses that have been marked up using h-entry. That’s one of the microformats 2 vocabularies—a much simpler way of writing structured content with microformats.
This is a spec to watch as is everything from the Indie Web movement, because they make the web a better and more distributed place.
It seems like swiping is considered to be extremely cool. Scrolling, on the other hand, not so much. I understand that new stuff is exciting, and I also understand that new stuff has to be investigated. But I believe that as of today we can safely assume that swiping is not native to the web. […] More and more browsers start using swipe gestures to navigate to the previous and next pages in the user’s history.