<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/blog/johan-baath" 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>Johan Baath&#039;s Blog Posts</title>
    <link>https://swsblog.stanford.edu/blog/johan-baath</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/blog-posts.xml/johan-baath" rel="self" type="application/rss+xml" />
      <item>
    <title>My Time at Stanford Web Services</title>
    <link>https://swsblog.stanford.edu/blog/my-time-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;Even though it feels like I have known the SWS team for years, the truth is that I have only been here for two months. The reason it feels that way might be because of the amount of things I’ve learned from my colleagues over the past 8 weeks could be compared to an intense 4-year combined degree in Computer Science/Customer Relations/&lt;span&gt;Project Management&lt;/span&gt;&lt;span&gt;. Another reason could be that the amazing people that comprise this team make you feel at home right away.&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 30 Nov 2015 16:15:47 +0000</pubDate>
 <dc:creator>Johan Baath</dc:creator>
 <guid isPermaLink="false">623 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>
  </channel>
</rss>
