This is notable/different because it uses descriptive HTML rather than semantic CSS classes: <grid columns=8> <c></c> <c span=3>3</c> <c></c> <c span=7-8>7-8</c> <c span=2+2>2+2</c> <c span=5-8>5-8</c> <c span=1-4>1-4</c> <c span=6..>6..</c> <c span=2..>2..</c> <c span=4..>4..</c> <c span=1-2>1-2</c> <c span=4-5>4-5</c> </grid>

read more

I’ve been using Semantic UI for years. Still do to this day. Unfortunately, the project hasn’t been sustainable with a BDFL despite Jack Lukic’s efforts (you can read a lot more on that history right here). These things happen. And when they do, it’s awesome to see the community rally around the project and keep it alive and thriving. That’s exactly the case with Fomantic UI. Let’s be clear: this is no hostile takeover. From the README: NOTE: Fomantic was created to continue active development of Semantic-UI and has the intent to be merged back into the master repository once active development can restart. Let’s hope the two can become one flesh at some point in the future. In the meantime, Fomantic is where the action’s at.

read more

Eric Bailey writing for CSS-Tricks: Good design isn’t about forcing someone to walk a tightrope across your carefully manicured lawn. Nor is it a puzzle box casually tossed to the user, hoping they’ll unlock it to reveal a hidden treasure. Good design is about doing the hard work to accommodate the different ways people access a solution to an identified problem. For reading articles, the core problem is turning my ignorance about an issue into understanding (the funding model for this is a whole other complicated concern). The more obstructions you throw in my way to achieve this goal, the more I am inclined to leave and get my understanding elsewhere—all I’ll remember is how poor a time I had while trying to access your content. What is the value of an ad impression if it ultimately leads to that user never returning? Fantastic article full of amazing resources. As web developers, we want people to experience our site the way it was intended. But that means we have to put in the work to make that experience easy, accessible, and clutter-free.

read more

Robin Rendle writing on CSS-Tricks: We should see front-end development as a unique skillset that is critical to the success of any project. I believe that’s why frameworks and tools like Bootstrap are so popular; not necessarily because they’re a collection of helpful components, but a global solution that corrects an inherent issue. … Bootstrap isn’t a skill though — front-end development is. It’s supremely ironic that front-end development is incredibly undervalued by many, yet those same people use frameworks because moving a box around in CSS is “hard.”

read more

Tomasz Jakut takes us through a proof-of-concept where he rebuilds Vue’s single file components from the ground up with nothing but browser-native technologies. It takes a few ‘dirty’ hacks to get the job done, but the journey is quite enjoyable and you learn a lot along the way. A great read! 💯

read more

Copy/paste the code in this repo’s README into your browser’s address bar and you end up with a super minimal CodePen-style editor. Pretty cool, and a bit crazy that you can get so much functionality with just 400 bytes of code…

read more

It allows complex layouts to be defined with CSS and JavaScript, while writing the content in a friendly, minimal syntax close to Markdown or LaTeX. Lots of nice output examples in the README.

read more

This is a spectacular project by Diana Smith: Rules I have for myself: All elements must be typed out by hand Only Atom text editor and Chrome Developer Tools allowed. SVG use is limited, and all shapes can only use hand-plotted coordinates and bezier curves - without the aid of any graphics editor. The results are stunning, to say the least. I won’t embed the image here, because it won’t do it justice. You have to click through and see it for yourself.

read more

Keith J. Grant: For the next few blog posts, I’m going to explore some aspects of HTML5 that maybe haven’t received as much attention as they deserve. As a warm up, I’ll look at some elements from HTML5 that most web developers probably are somewhat familiar with: <main>,<nav>, <article>, <section>, <aside>, and other structural, semantic elements. Even if you already use these elements, you might just learn a few new things along the way (I know I did as I researched this). I really enjoyed this article. I try to be as semantic as possible in my markup, but Keith’s post shed light on things I didn’t know—especially the impact certain elements can have on accessibility.

read more

This library has a tiny (4 KB) footprint, no dependencies, and most (all?) of the features you’d need in a file dropping library.

read more

What are Flame Graphs good for? According to Netflix, they’re using them for: quick analysis of performance issues such as perturbations, variance, single-threaded execution, and more.

read more