Chances are you are living in the past or working on a project that was built in the past that is still marking up content using DIV tags instead of semantic tags like article and section.
Don’t get me wrong, there is nothing wrong with using DIV tags and there will always be a use for them, some pieces of content should be marked up using tags with semantic meaning. They’re not only cleaner, but also help bolster your chances of ranking better on the likes of Google.
This is the one aspect of jQuery and well, Javascript, in general, I see newcomers to Javascript and jQuery get caught upon. Heck, I’ve seen veterans get caught up on how to properly cancel and allow events as well as event bubbling.
Nothing. There is no opposite method of “event.preventDefault()” to understand why you first have to look into what event.preventDefault() does when you call it.
Underneath the hood, the functionality for preventDefault is essentially calling a return false which halts any further execution. If you’re familiar with the old ways of Javascript, it was once in fashion to use return false for cancelling events on things like form submits and buttons using return true (before jQuery was even around).
Everyone wants to build the next Facebook, the next Google, the next Instagram and the next big thing. The harsh reality is that only a handful of people every so often actually make it. For every Mark Zuckerberg there are probably tens of thousands of entrepreneurs toiling away in cafes, the early hours of the morning and weekends who end up not “making it” presumably because only a very small percentage of entrepreneurs actually do.
If you’re like a lot of developers out there, you start your projects off with the best of intentions. No developer ever says, “I am going to make this project a fucking mess, a cluster-fuck of spaghetti code that even I’ll struggle to read in 2 weeks, let alone any other developer”
We’re living in the golden-age of front-end development. We have tools, we have awesome methodologies like BEM and CSS pre-processors like Sass. And for all that automation without a proper structure, our CSS always ends up being unorganised and messy.
For some time now there has been a slowly growing movement amongst particular designers and developers against WordPress. We’ve seen light CMS’s, decoupled PHP frameworks, open source alternatives and the big one: static site generators, but no matter the alternative, it seems it’s for the wrong intentions.
What WordPress Is Firstly, WordPress is a content management system that started out as a blogging platform. I’d actually argue WordPress is a framework of sorts in that it provides you with; user authentication, plugins sytem, themes system, helper classes and a loose structure which it expects you to follow (but isn’t overly strict on).
For some weird reason, this very blog has started getting a lot of traffic the last few days, from Google. I wonder if Google have recently tweaked their search algorithm again?
I have been trying to update the blog on a more regular basis, I’ve been posting two, sometimes three posts a day and I have been focusing on making the quality of them as decent as I can.
Perhaps I am experiencing the effects of a previous search engine algorithm change, and my recent updates have put me into the upper-echelon of Google’s almighty preference circle.
Firefox has supported CSS variables since version 29 and at present, no other browser supports them. In version 31 of Firefox, Mozilla are once again first to implement the latest working draft from the W3C for CSS variables. You can read the post about the addition to Firefox here.
All I have to say is, who the hell over at W3C came up with the syntax? I am very disappointed that the syntax doesn’t follow that of another language like, I don’t know, Javascript or perhaps you know, implemented similar syntax to that of Sass or Less.
First things first, I am not a Ruby on Rails veteran. I am fairly new to the framework, but have dabbled with Ruby before and understand it. Take this post with a grain of salt, this isn’t a debate or article putting down X language or X framework.
I see Ruby on Rails and Node.js compared so much and this question being repeatedly asked in every crevice of the Internet I thought I would take a stab at clearing up any confusion about making a choice.
All responsible/good front-ender developers use some kind of package management these days, whether it be in the form of Composer, Node Package Manager, Component or Bower. If you’re not using package management for your code, it’s not too late to start.
The power of Bower (ha, that rhymes) The true value of a front-end package manager like Bower is shown when you implement it into your WordPress themes. Have you ever had to update jQuery on a clients WordPress site you built 3 years ago or even on your own sites? I have and it’s not pretty.
To the disdain of some, NoSQL databases are well and truly here to stay and everyday proving their worth. The number one question I see being asked is: can I replace MySQL and use MongoDB instead?
A couple of years ago I would have told you no. In-fact, I would have probably argued with you about using a NoSQL database for more simple tasks that don’t require table joins and advanced queries instead of using it as a fully-blown RDBMS replacement. It’s 2014 and times change, especially as existing solutions die or mature.