<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/24/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>Uncategorized</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/24/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/24/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>What we have designed + engineered: the story of our navigation model for Stanford Sites  </title>
    <link>https://swsblog.stanford.edu/blog/what-we-have-designed-engineered-story-our-navigation-model-stanford-sites</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;lead&quot;&gt;Navigation is one of the most important functions of your website. Meant to organize your content into discernible sections, good navigation afords users intuitive pathways to discover or find content. Without good navigation, the effort you spend creating meaningful and compelling content is diminished if a user cannot find it.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 05 Aug 2020 19:41:53 +0000</pubDate>
 <dc:creator>Kerri Augenstein</dc:creator>
 <guid isPermaLink="false">796 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>My Summer at Stanford Web Services</title>
    <link>https://swsblog.stanford.edu/blog/my-summer-stanford-web-services</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;This summer, I had the opportunity to intern with the fantastic Stanford Web Services team. In doing so, I gained an understanding of the methodologies involved in the development of modern websites.&lt;/p&gt;
&lt;p class=&quot;summary&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 15 Sep 2017 23:11:35 +0000</pubDate>
 <dc:creator>Caleb Jones</dc:creator>
 <guid isPermaLink="false">735 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>CSS Injector: How to keep custom styles out of your edit pages</title>
    <link>https://swsblog.stanford.edu/blog/css-injector-how-keep-custom-styles-out-your-edit-pages</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 writing &lt;a href=&quot;https://swsblog.stanford.edu/blog/styling-sites-introduction-css-injector&quot; rel=&quot;nofollow&quot;&gt;CSS Injector&lt;/a&gt; styles to adjust the look of your Drupal site, it&#039;s easy to accidentally get what I call &quot;CSS bleed&quot; into the administrative experience, which can make things look pretty funky on edit screens. In this tutorial, I&#039;ll quickly explain how to avoid overriding the styles of your administration theme.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 16 Oct 2015 18:54:49 +0000</pubDate>
 <dc:creator>Johan Baath</dc:creator>
 <guid isPermaLink="false">607 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Improving Date and Time with our new Time Picker</title>
    <link>https://swsblog.stanford.edu/blog/improving-date-and-time-our-new-time-picker</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;Sometimes it is about the small things. &lt;span&gt;Something missing i&lt;/span&gt;&lt;span&gt;n Drupal&#039;s date popup field was a time popup. The calendar popup is very useful and very user friendly but it&#039;s sister field, the time field, is not. &lt;/span&gt;&lt;/p&gt;
&lt;h4&gt;&lt;strong&gt;Just give me the goods: &lt;a href=&quot;https://drupal.org/project/stanford_date_timepicker&quot; rel=&quot;nofollow&quot;&gt;Drupal Module Project Page&lt;/a&gt;&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt;&lt;img alt=&quot;Time Picker&quot; src=&quot;https://drupal.org/files/project-images/Screen%20Shot%202014-02-17%20at%202.09.05%20PM.png&quot; /&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 02 Jun 2014 16:00:00 +0000</pubDate>
 <dc:creator>Shea Ross McKinney</dc:creator>
 <guid isPermaLink="false">383 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
