In my last blog post, I talked about the difference between Wordpress and Drupal in terms for everyday users. In this post, I would like to highlight some of the differences when you're a developer and possibly some advantages you might see in Drupal when compared to Wordpress.
In part one of this series, I talked about the importance of properly transferring the value you have built in your existing website. The first step of this process is to conduct a content and SEO audit of your existing site. In this post, I will talk about what to do with that data.
In this blog post, I am going to extend upon my last module overview of Masonry, which is a Views plugin that utilizes the jQuery Masonry plugin. (Short recap, Masonry sets your elements into a responsive grid that aligns the elements in a brick fashion based on height, compared to the standard float technique.)
In response to a previous post about Converting Views List Into Responsive Stacked Columns, we've teamed up to create a module for just this sort of thing. Views Responsive Grid is a views display format plugin designed to give you the proper HTML structure for creating CSS grids.
In April 2012, I submitted a module called twitter_signin_callback to the project application queue. The concept was simple, my module was meant to add functionality to the twitter_signin module that allowed a developer to specify a path for where to send the user after logging in via Twitter OAuth. My thought was to get approval on a simple module to meet my goals for my job, and get commit access to be able to contribute some bigger ideas later.