<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text" xml:lang="en">Kevin Quillen - Still coding. Still rocking. Still ranting.</title>
    <link type="application/atom+xml" href="http://kevinquillen.com/feed/planet.xml" rel="self"/>
    <link type="text/html" href="http://kevinquillen.com/" rel="alternate"/>
    <updated>2016-02-21T20:04:00+00:00</updated>
    <id>http://kevinquillen.com/</id>
    <author>
        <name>Kevin Quillen</name>
    </author>
    <rights>Copyright (c) 2000-2014, Kevin Quillen; all rights reserved.</rights>

    
        
    
        
    
        
    
        
    
        
    
        
    
        
            <entry>
                <title>Using Drush Automatically with Grunt</title>
                <link href="http://kevinquillen.com/grunt/2015/02/04/using-drush-with-grunt"/>
                <updated>2015-02-04T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/grunt/2015/02/04/using-drush-with-grunt</id>
                <content type="html">Ever find yourself working on a Drupal theme and unable to figure out why templates aren&#39;t recognized, CSS isn&#39;t changing, or JS is still acting funky only to realize you haven&#39;t done something as simple as clear cache? We all have. Fortunately, we can do this automatically via Grunt.</content>
            </entry>
        
    
        
    
        
            <entry>
                <title>Using the Migrate Framework with a remote database on Pantheon</title>
                <link href="http://kevinquillen.com/migration/2014/08/02/drupal-pantheon-migrations"/>
                <updated>2014-08-02T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/migration/2014/08/02/drupal-pantheon-migrations</id>
                <content type="html">If you host your Drupal site on the Pantheon platform, you may already know that you do not need to include a settings.php file because they provide the connection information for you automatically. However, you _can_ provide one if you are setting up database connections. What was unclear, at least to me, is that you can only define connections for local development. Fortunately, there is a way around this.</content>
            </entry>
        
    
        
            <entry>
                <title>Media Migration Tip in Drupal</title>
                <link href="http://kevinquillen.com/drupal/2014/07/08/media-migrate-trick"/>
                <updated>2014-07-08T18:00:00+00:00</updated>
                <id>http://kevinquillen.com/drupal/2014/07/08/media-migrate-trick</id>
                <content type="html">&lt;p&gt;If you’re doing a migration of media files, you most likely will be working with a list of URLs. Other times, you will have a local file system from which to pull in media. When working with just a list of
URLs though, you’re somewhat working with a ‘blind’ import.&lt;/p&gt;

</content>
            </entry>
        
    
        
    
        
            <entry>
                <title>Add 301 Redirects to a Drupal Migration</title>
                <link href="http://kevinquillen.com/drupal/2014/07/02/add-redirect-during-migration"/>
                <updated>2014-07-02T08:02:00+00:00</updated>
                <id>http://kevinquillen.com/drupal/2014/07/02/add-redirect-during-migration</id>
                <content type="html">&lt;p&gt;Migrating content from one platform to another saves lots of time from doing grunt work and gets data moved fast. However, simply moving the content doesn’t mean the job is done. There are other considerations too, such as 301
redirects for example. Since we are moving content, our aliases are likely changing too. We can create 301s while migrating content in all at once.&lt;/p&gt;

</content>
            </entry>
        
    
        
            <entry>
                <title>Using Live Templates in PHPStorm</title>
                <link href="http://kevinquillen.com/tools/2014/07/01/live-templates-in-php-storm"/>
                <updated>2014-07-01T10:10:00+00:00</updated>
                <id>http://kevinquillen.com/tools/2014/07/01/live-templates-in-php-storm</id>
                <content type="html">PHPStorm and the JetBrains suite of products are without a doubt, the best IDEs on the market for their respective applications. If you do a lot of custom development, you owe it to yourself to learn and use every tool this IDE can afford you.</content>
            </entry>
        
    
        
    
        
            <entry>
                <title>Web scraping magic with Ruby and Nokogiri</title>
                <link href="http://kevinquillen.com/programming/2014/06/23/ruby-gets-shit-done"/>
                <updated>2014-06-23T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/programming/2014/06/23/ruby-gets-shit-done</id>
                <content type="html">Every now and then you&#39;re going to have one of those projects that will need to be migrated from one platform to another. Occasionally you will have to migrate a static site into a dynamic site. Don&#39;t panic. Don&#39;t hire a dozen interns to do the grunt work. With Ruby, we can quickly create intelligent scripts to scrape the static files and generate a CSV datasource for us to use.</content>
            </entry>
        
    
        
    
        
            <entry>
                <title>Basic behavior testing with Behat in Drupal</title>
                <link href="http://kevinquillen.com/bdd/2014/06/08/your-first-behat-test"/>
                <updated>2014-06-08T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/bdd/2014/06/08/your-first-behat-test</id>
                <content type="html">We have all at some point or another faced projects where wasted minutes and/or hours on regressions or redo work not only eat into the current project budget, but hurt long term numbers too on the books. Fortunately, we can crush this leveraging Behat and covering our bases with tests, and everyone goes home happy.</content>
            </entry>
        
    
        
            <entry>
                <title>Up and Running with Behat, Drupal, &amp; Vagrant</title>
                <link href="http://kevinquillen.com/bdd/2014/06/06/behat-drupal"/>
                <updated>2014-06-06T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/bdd/2014/06/06/behat-drupal</id>
                <content type="html">Behat is a PHP implementation of the Gherkin language, which powered Cucumber for Ruby. It provides a way to tell the system in plain English how to go about testing your feature points as if it were the user doing it. Not only is this a great way to automate tests, it cuts down hours of tedious clicking by a human to say that something is working or not.</content>
            </entry>
        
    
        
            <entry>
                <title>Spiff up your Drupal AJAX interactions.</title>
                <link href="http://kevinquillen.com/javascript/2014/06/04/kill-the-ajax-throbber"/>
                <updated>2014-06-04T14:00:00+00:00</updated>
                <id>http://kevinquillen.com/javascript/2014/06/04/kill-the-ajax-throbber</id>
                <content type="html">There are things I love about Drupal. There are also things I flat out hate about Drupal, too. One of them is the throbber.gif activity indicator. Guys, we can do better. Let&#39;s add some shine.</content>
            </entry>
        
    
        
    
</feed>