<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/4/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>Tips and Tricks</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/4/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/4/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Getting started on Sites: Creating a Personal Webpage</title>
    <link>https://swsblog.stanford.edu/blog/getting-started-sites-creating-personal-webpage</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;I am sure some of you have noticed that there is a Stanford Light sample image of Jane Smith&#039;s personal website and were wondering how to recreate the same page for yourself. &lt;/p&gt;
&lt;p&gt;In this blog post, I&#039;ll show you how you can put together an About page layout similar to the Jane Smith&#039;s personal website preview image seen on the Appearance page.&lt;/p&gt;
&lt;p class=&quot;float-left&quot;&gt;&lt;img alt=&quot;&quot; src=&quot;https://swsblog.stanford.edu/sites/swsblog/themes/stanford_light/screenshot.png&quot; style=&quot;height: 219px; width: 294px;&quot; /&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 03 Dec 2019 18:30:35 +0000</pubDate>
 <dc:creator>Rebecca Hong</dc:creator>
 <guid isPermaLink="false">791 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>How to tell Google about your Stanford Sites website</title>
    <link>https://swsblog.stanford.edu/blog/how-tell-google-about-your-stanford-sites-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;You&#039;ve put time into creating your &lt;a href=&quot;http://sites.stanford.edu&quot;&gt;Stanford Sites&lt;/a&gt; website, so you&#039;ll probably want Google (and other search engines) to know about it. One of the ways to get this done is by submitting your website sitemap. This blog post will walk you through how to claim ownership of your Stanford Sites website, then submit the website to Google for indexing. &lt;/p&gt;
&lt;p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 17 Aug 2018 00:28:39 +0000</pubDate>
 <dc:creator>Alyssa Hislop</dc:creator>
 <guid isPermaLink="false">756 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Altering Custom Elements in Forms</title>
    <link>https://swsblog.stanford.edu/blog/altering-custom-elements-forms</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;&lt;a href=&quot;https://www.drupal.org/&quot; rel=&quot;nofollow&quot;&gt;Drupal&lt;/a&gt; provides a powerful framework for creating custom elements for use in forms. One example of a custom element is the &lt;/span&gt;&lt;a href=&quot;https://www.drupal.org/project/link&quot; rel=&quot;nofollow&quot;&gt;Link&lt;/a&gt;&lt;span&gt; field. Suppose you want to change the default label on a Link field to read &quot;Link text.&quot; How do you alter it?&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 23 Oct 2017 20:46:13 +0000</pubDate>
 <dc:creator>Caryl J Westerberg</dc:creator>
 <guid isPermaLink="false">729 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Grep Invert Match</title>
    <link>https://swsblog.stanford.edu/blog/grep-invert-match</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;Today I learned about the &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;bash geshifilter-bash&quot;&gt;-v&lt;/code&gt;&lt;/span&gt; flag for &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;bash geshifilter-bash&quot;&gt;grep&lt;/code&gt;&lt;/span&gt;. The &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;bash geshifilter-bash&quot;&gt;-v&lt;/code&gt;&lt;/span&gt;, or &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;bash geshifilter-bash&quot;&gt;--invert-match&lt;/code&gt;&lt;/span&gt;, flag, returns all lines that do &lt;strong&gt;not&lt;/strong&gt; match your regular expression.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 02 Oct 2017 22:11:22 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">733 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Adding Styles to Stanford WYSIWYG</title>
    <link>https://swsblog.stanford.edu/blog/adding-styles-stanford-wysiwyg</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 Stanford WYSIWYG gives the content editor multiple style options to modify the look of their site&#039;s content.  Suppose you want the ability to float an image right or left in the content region but it&#039;s not in the list of Styles. You can create a CSS Injector rule to target that specific content then make this style available to the WYSIWYG Styles drop-down list. To tackle this example, let&#039;s go step-by-step to add the ability to float images right or left in the content region within the WYSIWYG.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 13 Jul 2017 03:04:29 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">731 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Stanford Events Series module</title>
    <link>https://swsblog.stanford.edu/blog/stanford-events-series-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 class=&quot;summary&quot;&gt;Do you have a collection of ongoing related events? Try the Event Series module to collect events onto a single page and display upcoming and past events.&lt;/p&gt;
&lt;p&gt;Stanford Event Series joined Stanford Sites during the Summer 2016 Updates. Previously it was only available to our Jumpstart clients, but high demand for this functionality on Stanford Sites, combined with our commitment to contributing back to the greater community brought this module to sites created on Stanford Sites.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 31 Mar 2017 15:45:46 +0000</pubDate>
 <dc:creator>Anna Watt</dc:creator>
 <guid isPermaLink="false">726 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Creating a news item for your website</title>
    <link>https://swsblog.stanford.edu/blog/creating-news-item-your-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;Want to create a news item for your Stanford Sites? Stanford News feature provides an out of the box solution for displaying news content on your website. &lt;span&gt;This feature contains a content type, fields, a news page layout, and taxonomy. This module is a great replacement for the default Article content type.&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;Enable Stanford News module for your site&lt;/h2&gt;
&lt;ol class=&quot;clearfix&quot;&gt;&lt;li&gt;
		&lt;p&gt;Login to your Stanford Sites website&lt;/p&gt;
	&lt;/li&gt;
	&lt;li&gt;
		&lt;p&gt;From the Admin toolbar, click Modules&lt;/p&gt;
	&lt;/li&gt;
	&lt;li&gt;
		&lt;p&gt;Filter list by stanford_news&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 24 Mar 2017 17:48:46 +0000</pubDate>
 <dc:creator>Grace Kiburi</dc:creator>
 <guid isPermaLink="false">700 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Making menu links visible for all users</title>
    <link>https://swsblog.stanford.edu/blog/making-menu-links-visible-all-users</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;You have created a page that is restricted to Stanford only users logged in with their SUNet ID and placed that page in the menu. After logging out of your site, you noticed that the link is gone! Would you like to make your menu links visible to all users even though the content is restricted? Always Visible module can help you do that!&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 17 Mar 2017 18:55:34 +0000</pubDate>
 <dc:creator>Grace Kiburi</dc:creator>
 <guid isPermaLink="false">698 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Add a photo gallery to your site</title>
    <link>https://swsblog.stanford.edu/blog/add-photo-gallery-your-site</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;Want to display a group of photos on your site? Stanford Sites now offers a solution for creating your own galleries.&lt;/p&gt;
&lt;p class=&quot;summary&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 05 Dec 2016 20:06:30 +0000</pubDate>
 <dc:creator>Alyssa Hislop</dc:creator>
 <guid isPermaLink="false">676 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Choosing NoBots instead of Stanford MetaTag NoBots </title>
    <link>https://swsblog.stanford.edu/blog/choosing-nobots-instead-stanford-metatag-nobots</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;Are you creating a new site on Stanford Sites, but don&#039;t want Search Engines to see it? The &lt;a href=&quot;https://www.drupal.org/project/nobots&quot; rel=&quot;nofollow&quot;&gt;NoBots module&lt;/a&gt; is here to replace Stanford MetaTag NoBots. &lt;/p&gt;
&lt;p class=&quot;clear-both&quot;&gt;&lt;span&gt;NoBots recently joined the growing list of modules available to Stanford Sites during the &lt;/span&gt;&lt;a href=&quot;https://swsblog.stanford.edu/blog/stanford-sites-updates-summer-2016&quot; rel=&quot;nofollow&quot;&gt;Summer 2016 Updates&lt;/a&gt;&lt;span&gt;. It replaces the soon-to-be-deprecated &lt;/span&gt;&lt;a href=&quot;https://github.com/SU-SWS/stanford_metatag_nobots/blob/7.x-3.x-dev/README.md&quot; rel=&quot;nofollow&quot;&gt;Stanford Metatag NoBots module&lt;/a&gt;, which was featured as a &lt;a href=&quot;https://swsblog.stanford.edu/blog/module-day-stanford-metatag-nobots-hide-your-site-search-engines&quot; rel=&quot;nofollow&quot;&gt;Module of the Day&lt;/a&gt; here on the SWS Blog in 2014.&lt;/p&gt;
&lt;p class=&quot;summary&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 20 Oct 2016 16:00:00 +0000</pubDate>
 <dc:creator>Alyssa Hislop</dc:creator>
 <guid isPermaLink="false">682 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Git: Find the First Tag Containing a Specified Keyword</title>
    <link>https://swsblog.stanford.edu/blog/git-find-first-tag-containing-specified-keyword</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;Today&#039;s post is a quick tutorial how to use &quot;git grep&quot; and &quot;git tag&quot; to find the earliest tag that contains a particular line of code.&lt;/p&gt;
&lt;p&gt;TL;DR: use:&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;text geshifilter-text&quot;&gt;git grep &amp;lt;regexp&amp;gt; $(git rev-list --all)&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;and&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;text geshifilter-text&quot;&gt;git tag --contains=&amp;lt;commit hash&amp;gt;&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 07 Sep 2016 15:00:00 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">672 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>DrupalCon 2016: Caryl’s Highlights</title>
    <link>https://swsblog.stanford.edu/blog/drupalcon-2016-caryl%E2%80%99s-highlights</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;DrupalCon (Drupal Conference) 2016 marked the 3rd DrupalCon that I attended. With Drupal 8 released, I felt it was time to go to the conference and kick the tires.&lt;/p&gt;
&lt;p&gt;Held in historic New Orleans, I not only learned more about Drupal 8, but I learned about the beignets, cemeteries, and handgrenades. But that’s for another story.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 31 May 2016 23:54:52 +0000</pubDate>
 <dc:creator>Caryl J Westerberg</dc:creator>
 <guid isPermaLink="false">650 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Hiding the WebAuth Login Block</title>
    <link>https://swsblog.stanford.edu/blog/hiding-webauth-login-block</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;Want to hide or move the WebAuth login block on your website? On Stanford Sites the login block is in the left sidebar by default giving the administrator easy access to log in and make changes to their website. As an administrator you have the option to move this block to a different region or completely hide it.  Let&#039;s talk about both options and their ramifications.&lt;/p&gt;
&lt;p&gt;If you have multiple people collaborating on your site, you may choose to keep the WebAuth Authentication block visible somewhere on the page.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 12 May 2016 16:06:31 +0000</pubDate>
 <dc:creator>Cynthia Mijares</dc:creator>
 <guid isPermaLink="false">648 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Drupal 8 REST Requests</title>
    <link>https://swsblog.stanford.edu/blog/drupal-8-rest-requests</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;In November, 2015, the Stanford Web Services team got to dive into Drupal 8 during a weeklong sprint. I was excited to look at the RESTful web services that Drupal 8 gives out-of-the-box; what follows is my documentation of the various types of requests supported, required headers, responses, and response codes.&lt;/p&gt;
&lt;p&gt;This is not intended to be an exhaustive documentation of RESTful web services in Drupal 8. However, I have pulled information from various posts around the Web, and my own experimentation, into this post.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 02 Feb 2016 16:25:12 +0000</pubDate>
 <dc:creator>John Bickar</dc:creator>
 <guid isPermaLink="false">613 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Update status for your custom features</title>
    <link>https://swsblog.stanford.edu/blog/update-status-your-custom-features</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;Not all modules belong on Drupal.org&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 09 Dec 2015 17:14:57 +0000</pubDate>
 <dc:creator>Shea Ross McKinney</dc:creator>
 <guid isPermaLink="false">454 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
