<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/361/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>Jumpstart</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/361/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/361/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Managing Content on Your Drupal Website</title>
    <link>https://swsblog.stanford.edu/blog/managing-content-your-drupal-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;Our team created the &lt;a href=&quot;https://sites-jumpstart.stanford.edu/&quot;&gt;Stanford Sites Jumpstart service&lt;/a&gt; to help website owners focus their energy on what matters most: their content. To do this, Jumpstart includes a dashboard for simple content maintenance. This &quot;Manage Content&quot; feature offers an overview of all pages in the site and supports updating individual or multiple pages at one time.&lt;/p&gt;
&lt;p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 02 Nov 2015 15:00:00 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">519 at https://swsblog.stanford.edu</guid>
  </item>
  <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>Adaptive Architecture: Leave Room to Evolve</title>
    <link>https://swsblog.stanford.edu/blog/adaptive-architecture-leave-room-evolve</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;All forward-thinking technologies share one attribute: the original designers intentionally build in opportunities for future users to innovate. It requires humility and a belief in the creativity of others. This is true for buildings, computers, networks, and other tools.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 12 Dec 2014 14:55:45 +0000</pubDate>
 <dc:creator>Zach Chandler</dc:creator>
 <guid isPermaLink="false">489 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Getting Started on Sites: Remove Users Account Privileges</title>
    <link>https://swsblog.stanford.edu/blog/getting-started-sites-remove-users-account-privileges</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;Let&#039;s say your co-worker left Stanford or the grad student working on your website is no longer here. I&#039;ll walk you through the steps to either remove their editing privileges or cancel their account.&lt;/p&gt;
&lt;p&gt;After logging in the your website, navigate to the &lt;strong&gt;People&lt;/strong&gt; page.  In Stanford Sites Jumpstart products, go to the &lt;strong&gt;Site Actions&lt;/strong&gt; menu and choose &lt;strong&gt;Manage Users&lt;/strong&gt;.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 15 Sep 2014 15:47:06 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">415 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
