This may be a rather short blog post, but it is mainly because this is such a simple solution. Recently my computer barked at me for having having practically no disk space left. Probably like most, I was in the middle of something and promptly ignored it.
Have you ever been in a situation where you needed to collect a certain type of data on a node form and display it in a certain way that wasn't supported by the core Drupal field types? Rather than using a text field to display something like a phone number or email address, you may consider using the phone or email modules instead, both of which are perfect examples of why you may need to define your own custom field types.
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.