It has been around a month and a half since we jumped into 2013. And this is my first post of the year. I released a side project called Hint.css some days back on Hacker News and this post is primarily about what it is, how it works and what all I learned while creating it.
First I would like to mention how nicely it was received and appreciated by the community. Here are some stats for the same:
I released it on Hacker News on 4th Feb 2013 where it attained #1 ranking just after half an hour or so. Cool eh? BTW, this was the first time my submission got to #1 :) It got 224 upvotes. Thank you!
As a result of the above, the project page around 20K+ unique views. Heres an image showing some realtime stats after ~3 hours of release (Note: The realtime count did went above 300, but come on…I was not in a state to take a screenshot then :P):
The github repo has been starred and forked 1.4K+ and 100+ times respectively.
Also the repo is still in the list of most trending repos on github.
So all in all, the launch was beyond expectations and really good.
####1. Pseudo elements
Pseudo elements are a gift for web developers which open numerous possibilities for creating amazing stuff. Hint.css makes use of these pseudo elements (
::after elements) to create the actual tooltip.
This has the advantage that you do not have to add any extra markup on your page. But it has a downside too. As the tooltip is created using pseudo elements, its not possible to use them for any other purpose on the element you put tooltip on.
####2. data-* attributes
The tooltips need to be told what text to show. How do we provide this text?
data-* attributes to the rescue. They let you put custom data on any element using attributes. So hint.css expects you to define an attribute called
data-hint on the element which needs a tooltip:
1 Out of the many, <span data-hint="Tooltip text">this</span> word needs a tooltip.
####3. attr function for content
Now the most important part on which hint.css is based on. You may have heard about the
content property of pseudo elements. As is clear from the name, it lets you specify content of the pseudo element.
What was really great for me was the attr function which gives you the power of grabbing the value of any attribute on the element and set it as the pseudo element’s content. Isn’t that really neat? So the meat of the library is this one line:
1 content: attr(data-hint);
And you are DONE!
####4. CSS3 transitions Finally to add some eye candy, the tooltips are loaded with subtle fade & translate effect using CSS3 Transitions.
One thing to note here is that Transitions on pseudo elements work only in Firefox presently. But do not worry guyz…thanks to Elliott Sprehn, the feature has arrived in Google Chrome 26 dev version and it’s not too far when we’ll all have it in the stable one too :)
###What I learned
If you are passionate about creating cool new stuff, you surely understand the importance of developing small side projects, something you can own completely. It teaches you a hell lot of things…not only about the tech side but about managing stuff from planning to releasing to maintaining a small product. You should probably read this awesome post on creating side projects by Sacha Grief.
While making hint.css I too learned many things which I would like to share here.
This was the first time I tried SASS. SASS is basically a CSS preprocessor…meaning it provides you some great features (like variables, mixins etc) to write your CSS in a more efficient way.
I had never felt the need of using a preprocessor ever. And same was with hint also. If you happen to see the original demo of hint.css I released, it was written in CSS. Even when I started writing the actual library I was using plain CSS but then things started getting very repetitive and unmanageable.
Adding any new type of tooltip required to change certain properties on all four tooltip positions (top, bottom, left and right) which I had to write again and again. Also at times, inconsistencies occurred with respect to color values and other static numbers used at different places. And hence I was forced to look into a preprocessor that could make me write smarter code.
Basically its the mixins (check out src/color-types.scss for example) and variables that made the whole library very easy to extend and consistent everywhere.
It has worked quite well till now. I had to install some extra tasks for SASS compilation and CSS minification as they don’t come bundled by default with Grunt and now I simply run
grunt watch and all building happens silently in the background as I develop.
This one is a tough and I would say a phase which needs more consideration and effort than the actual development itself. Coding the library hardly took a day or two but rest of the work took around 300% of the already spent time and that includes: - Writing README for the repo - Creating a project page with demo, usage explanation etc - Writing a blog post about the project - Making sure I did not miss anything - Finally releasing!
During this I became better at writing (I only love writing code though) and managing multiple tasks.
####More CSS knowledge Last but not the least, as I was working on a CSS library I came to know more about it as mentioned earlier. CSS is really beautiful :)
###In the end
Finally Hint.css was released as an Open Source project on Github. But it didn’t stop there. People have been liking it and started using and contributing to it which marks the beginning of the final phase of a software: Maintenance. To keep a library fresh you need to constantly keep it up to date with latest technology, keep adding new features your users want, fix bugs that get reported regularly. And all this in very organized and planned manner so that the user’s know exactly what changed when, whats coming up etc. In short, everyone should be able to track the project without difficulties.
Doing all this is fun. I am getting to know GIT better and better now that I have started using branches, merging etc a lot. I only hope I don’t face the Cute Puppy Syndrome (a term coined by @fat) in future :P
Talking about issues, one thing that I have been hearing a lot from people is that BEM naming convention is kind of an overkill, specifically in Hint. For example people prefer
hint-top class over
hint--top. I am still thinking over this if BEM was at all necessary or is really an overkill in my library. Though I would really appreciate if BEM masters could really comment on this.
Would love to hear your comments, suggestion or anything you feel like saying about my work, this post…anything.
P.S. Discussion on Hacker News.