Skip to content

This guide provides instructions and information about Stanford Web Services Jumpstart platform, based on Drupal 7.

We've released our new Stanford Sites on Drupal 8 (D8) platform — the new framework for Stanford Sites in 2020 and beyond. Check out our new User Guide to help you set up your website on the D8 platform. 

Read more about our road to D8 

Taking care of your site post-launch

Congratulations, your new site is now launched!

Your Stanford Sites Jumpstart site is now accessible at the predetermined vanity URL, and your site is also now indexable and searchable by search engines. We have also enabled automatic content redirection. What this means for you is that when you move a page to a new part of the menu or change the title of the node the path for that page will change. A redirect from the old path to the new path will automatically be created.

Just a reminder, sometimes websites need a little tweaking after launch. Let us know if you find something that needs our attention.

Editing content

You're welcome to continue editing the site as needed. Please keep in mind that there is more caching enabled on your site now that the site is live, so changes can take much longer to appear for users that are not logged in. We do this to make your site load faster. If you need to make your content live sooner, you can always clear the caches with the Clear Site Cache option in your Site Actions menu.

Analyzing content

We’ve also configured analytics for your site. We have some tips from our blog on interpreting common analytics reports for your site.

Google also has comprehensive documentation on using their Analytics tool.

Requesting help

If you have questions or need assistance with your Stanford Jumpstart Site developed by Stanford Web Services, SWS provides weekly office hours to our clients. You can also submit support requests  directly via our support form on the Get Help page on your admin shortcuts bar.

Maintaining your site

We recommend reviewing the following best practices for content updates to your site.

Best practices

  • Write revision comments when editing nodes

  • Add page nodes to the Main Menu as much as possible

  • Keep headers in semantic order (h2, h3, h4, etc)

  • Add alternative text (“alt text”) to images

  • Use Box for storing large files

  • Create users accounts by having them log in first with SUNet ID, then assign the Drupal role

  • Use a purpose built intranet tool for larger intranet-style sites.

  • Use CAP for maintaining user profiles (CAP can then automatically sync profile information with your website via the CAPx module)

  • Add events in and then set up an importer to sync them with your site. You can create “unlisted” events that do not show up on the main site, but having your event listed on can assist with university emergency coordination).

  • Refresh your courses feed for the new academic year, if applicable. Schedule a visit to SWS office hours to import courses for the new academic year

Things to avoid

  • Put JavaScript or CSS in blocks or nodes

  • Use the Anchor icon in the WYSIWYG editor; create a new page instead

  • Insert tables, unless necessary for tabular data

  • Set links to open in new windows (avoid using target=”_blank”)

  • Set image properties in the WYSIWYG editor; instead, insert the image with available image styles

  • Save in Full HTML when editing a page unless absolutely necessary

  • Create absolute URLs to content within the website, unless it is via the WYSIWYG editor