I love Open-Source and try to release most -if not all- of my projects under the GPL so that everyone can benefit from my work.
For the past decade I've been building websites for small and large companies. I specialize in responsive front-end design, HTML/CSS and web interfaces. Some of my most popular projects include the Elusive Icons Webfont and the Shoestrap WordPress theme.
Currently I work at WPMU-DEV as support staff and my startup wpmu.io, striving to evolve and improve my personal projects.
Recent blog posts:
As humans we grow. We change perspectives and see things differently.
We keep learning new things and strive to improve ourselves.
This also applies to the code we write: We keep improving the code we write on a daily basis and improve the things we have already built. The ugliest code I've seen is the code I wrote last year. I always say that and some people may disagree, but it's true. And each year, each month that goes by we keep learning things and change the way we function. As a result, I sometimes look at the code I wrote a while back and say to my self "what on earth have you done here Ari? Why??"
Sometimes when you build a WordPress multisite installation that will be accessible by many people, you want to restrict access to certain areas of your site. The reasons behind such a decision may vary: Some want to simply make it easier for their clients to navigate the dashboard by removing all the clutter and others want to protect sensitive areas of their sites.
The WordPress Customizer was first introduced in WordPress 3.7 and provides an easy way for themers and plugins developers to allow users to change their settings while at the same time they can see the effects of these changes in real-time on a preview screen.
A lot of themes use the WordPress customizer to generate additional CSS.
That CSS is then usually simply echoed to the
<head> of the page.
With this article I'll be sharing some more info about myself and launch this blog.