<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/35/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:og="http://ogp.me/ns#" xmlns:article="http://ogp.me/ns/article#" xmlns:book="http://ogp.me/ns/book#" xmlns:profile="http://ogp.me/ns/profile#" xmlns:video="http://ogp.me/ns/video#" xmlns:product="http://ogp.me/ns/product#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>development</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/35/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/35/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Transparency in Product Development</title>
    <link>https://swsblog.stanford.edu/blog/transparency-product-development</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;div&gt; &lt;/div&gt;
&lt;p class=&quot;summary&quot;&gt;&lt;span&gt;While Stanford Web Services can be seen as a service provider, often involved with custom projects and closely working with clients, one of our core offerings is also our Jumpstart product. With any product offering company, as adoption and usage of the products grow, more and more customers give feedback and express interest in the future direction of the product. Lately, our group has been contemplating increasing transparency in our product development roadmap, and to what extent.&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 29 Oct 2015 21:05:07 +0000</pubDate>
 <dc:creator>Jamie C. Tsui</dc:creator>
 <guid isPermaLink="false">579 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Drush &quot;user-list&quot; Command</title>
    <link>https://swsblog.stanford.edu/blog/drush-user-list-command</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;A simple task: list all the users on a site, optionally filtering by role or by status. Difficulty: using &lt;a href=&quot;http://drush.org&quot;&gt;drush&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I had searched around a bit for this functionality and my Google-fu had failed me, so I decided to build off of &lt;a href=&quot;https://www.drupal.org/node/1199080&quot;&gt;work that already had been done&lt;/a&gt; and write a drush user-list command. (The internal monologue went something like this: &quot;Is this a thing? It doesn&#039;t look like this is a thing. This should be a thing. Why is this not a thing? Let&#039;s make this a thing.&quot;)&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 26 Jun 2015 16:05:02 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">585 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Behat Custom Step Definition: Wait for Batch API to Finish </title>
    <link>https://swsblog.stanford.edu/blog/behat-custom-step-definition-wait-batch-api-finish</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;If you&#039;re using &lt;a href=&quot;http://behat.readthedocs.org/en/v2.5/quick_intro.html&quot;&gt;Behat&lt;/a&gt; and the &lt;a href=&quot;https://www.drupal.org/project/drupalextension&quot;&gt;Drupal Extension&lt;/a&gt;, you might find the following code snippet helpful if you want to add a step to wait for batch jobs to finish.&lt;/p&gt;
&lt;p&gt;If one of your Behat scenarios kicks off a batch job (e.g., a Feeds import), and you want to wait for that batch job to finish before moving on to the next step, add this step definition in your FeatureContext.php file:&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 13 Feb 2015 22:00:00 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">507 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Hard vs soft configuration: Designing your distribution</title>
    <link>https://swsblog.stanford.edu/blog/hard-vs-soft-configuration-designing-your-distribution</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;&lt;span&gt;In this article we are going to talk about what hard and soft configuration is and how to decide between the two when creating a &lt;a href=&quot;https://www.drupal.org/documentation/build/distributions&quot; rel=&quot;nofollow&quot;&gt;distribution&lt;/a&gt;. &lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 27 Oct 2014 15:30:23 +0000</pubDate>
 <dc:creator>Shea Ross McKinney</dc:creator>
 <guid isPermaLink="false">442 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>pushd, dirs, and popd</title>
    <link>https://swsblog.stanford.edu/blog/pushd-dirs-and-popd</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;If you spend a lot of your day at the command line (as I do), you&#039;re constantly on the lookout for new tools and tricks to increase your productivity and efficiency. Today we&#039;re going to take a look at the &lt;a href=&quot;https://en.wikipedia.org/wiki/Pushd&quot;&gt;pushd&lt;/a&gt; suite of commands that exist in most shells (e.g., bash, tcsh and so forth).&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 09 Jun 2014 11:49:32 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">387 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Creating a Static Copy of a Website</title>
    <link>https://swsblog.stanford.edu/blog/creating-static-copy-website</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;The modern Web is a dynamic place. However, sometimes it&#039;s necessary (or desirable) to remove the dynamic functionality of a website, while preserving its static content.&lt;/p&gt;
&lt;p&gt;Inspired in part by Karen Stevenson&#039;s excellent blog post, &quot;&lt;a href=&quot;http://www.lullabot.com/blog/article/sending-drupal-site-retirement&quot;&gt;Sending a Drupal Site into Retirement&lt;/a&gt;,&quot; I wanted to outline a few other techniques for accomplishing this.&lt;/p&gt;
&lt;p&gt;Reasons you may want to create a static copy of a site:&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 17 Mar 2014 17:09:13 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">339 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Create a Page Title From the Views Exposed Filter Term</title>
    <link>https://swsblog.stanford.edu/blog/create-page-title-views-exposed-filter-term</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;Suppose you&#039;re using taxomomy terms in exposed filters, and you want the resulting page to display one of the the terms as a title. Taxonomy term pages will give this to you very easily, but sometimes the taxonomy term page is not the right solution.  Here&#039;s how you can display the taxonomy term as the title of your views page.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 10 Mar 2014 15:18:30 +0000</pubDate>
 <dc:creator>Caryl J Westerberg</dc:creator>
 <guid isPermaLink="false">199 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Creating a Menu Position Rule Programatically</title>
    <link>https://swsblog.stanford.edu/blog/creating-menu-position-rule-programatically</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p class=&quot;summary&quot;&gt;The &lt;a href=&quot;https://drupal.org/project/menu_position&quot;&gt;Menu Position&lt;/a&gt; module provides a powerful way for Drupal to &lt;a href=&quot;/blog/menu-tricks-3-automating-virtual-menu-position-specific-content-types&quot;&gt;create &quot;virtual&quot; menu items&lt;/a&gt;, and provides a graphical user interface to do so. However, as a developer, sometimes you want to create those rules in code. Here&#039;s how.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 11 Oct 2013 16:03:28 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">291 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Stanford Events Importer 7.x-2.x</title>
    <link>https://swsblog.stanford.edu/blog/stanford-events-importer-7x-2x</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;In November, 2012, SWS released a &lt;a href=&quot;https://drupalfeatures.stanford.edu/sites/default/files/fserver/stanford_events_importer-7.x-2.0-beta4.tgz&quot;&gt;stable beta version&lt;/a&gt; of the &lt;a href=&quot;http://drupalfeatures.stanford.edu/project/stanford-events-importer&quot;&gt;Stanford Events Importer&lt;/a&gt; for Drupal 7. The Stanford Events Importer integrates with the XML feeds from &lt;a href=&quot;http://events.stanford.edu&quot;&gt;events.stanford.edu&lt;/a&gt; and allows you to &quot;automagically&quot; import events into your Drupal site.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 09 Jan 2013 23:14:20 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">53 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>ExploreCourses and the Stanford Courses Drupal Module</title>
    <link>https://swsblog.stanford.edu/blog/explorecourses-and-stanford-courses-drupal-module</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;In December, 2011, we released the &lt;a href=&quot;http://drupalfeatures.stanford.edu/project/stanford-courses&quot;&gt;Stanford Courses&lt;/a&gt; module for Drupal 6. This is a Features-based module that polls the XML feed at &lt;a href=&quot;http://explorecourses.stanford.edu&quot;&gt;ExploreCourses&lt;/a&gt; and creates Course and Course Section nodes on a Drupal website.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 14 Dec 2012 19:42:54 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">45 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
