Here’s some CSS humor for you – Ninjas of Web Development: 30+ CSS Puns That’ll Crack You Up. Some of these are very obvious, some are very subtle.
“Lesser known CSS quirks & advanced tips” is a collection of some really weird CSS features and behaviors. These are good to know, as sometimes they can shed some light on strange results or help with implementation of a particular design feature, where no other options are applicable.
It won’t change your life, but it will help with adding a little human touch to your web application.
What can we do with this method?
We can gather some basic information about the user, like the screen resolution (when the browser is maximized) and which browser (or engine) is used. Further we can detect if a user opens a link or hovers with the mouse over an element. This can be used to track which (external) links a user visits and using the hover method. It should be even possible to track how the user moved their mouse (using an invisible table of fields in the page background). However, using my method it’s only possible to track when a user visits a link the first time or hovers over a field the first time. Maybe it’s possible to modify the method so that it is possible to track every click.
Furthermore it is possible to detect if a user has installed a specific font. Based on this information it should be possible to detect, which OS a users uses (because different operating systems ship different fonts, e.g. “Calibri” on Windows).
css-purge is a tool that does the following:
A CSS tool written in Node JS as a command line app or library for the purging, burning, reducing, shortening, compressing, cleaning, trimming and formatting of duplicate, extra, excess or bloated CSS.
“A Look Back at the History of CSS” is a nice trip down the history lane as to where and how CSS came about. It’s hard to imagine these days that CSS wasn’t always around and the web looked like whatever your browser decided to make it look like.
This Front-End Checklist is pretty awesome and quite extensive:
The Front-End Checklist is an exhaustive list of all elements you need to have / to test before launching your site / page HTML to production.
It is based on Front-End developers’ years of experience, with the addition from some other open-source checklists.
The best part is that large parts of this list are pretty easy to automate and integrate with your deployment / continuous delivery tool chain.
Grabient is a quick and easy to use online tool for generating CSS gradients. You can pick any two colors, adjust the gradient angle and shift, and generate a CSS snippets to add to your web project.
- This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team.
- For each problem domain and each technology, I try my best to pick only one or a few links that are most important, typical, common or popular and not outdated, base on the clear trends, public data and empirical observation.
- Prefer fine-grained classifications and deep hierarchies over featureless descriptions and distractive comments.
- Ideally, each line is a unique category. The ” / “ symbol between the links means they are replaceable. The “, “symbol between the links means they are complementary.
- I wish this document could be closer to a kind of knowledge graph or skill tree than a list or a collection.
- It currently contains 2000+ links (projects, tools, plugins, services, articles, books, sites, etc.)
On one hand, this is one of the best single resources on the topic of web development that I’ve seen in a very long time. On the other hand, it re-confirms my belief in “there is no such thing as a full-stack web developer”. There’s just too many levels, and there’s too much depth to each level for a single individual to be an expert at. But you get bonus points for trying.