Production Server

The following aspects have dedicated spaces on the webdev.bu.edu production server.


Webteam Projects

Each client project is provided a space for Interactive Design to be present on bu.edu/webteam/projects. This portal includes a project’s information architecture, wireframes, and mockups for review and approval. Clients can access these materials anytime, streamlining the approval process and ensuring transparency throughout the project.

webdev.bu.edu/web/w/e/webteam/projects/

Example Webteam Project


BU CDN

Our single-location setup that stores and delivers web logo assets, webfonts, and icons — offering an efficient content distribution, without needing to rely on licenses or global server outages.

webdev.bu.edu/web/c/d/cdn/

It has been previously managed by Senior Lead Designer Michael Jordan.

BU CDN


The following aspects have dedicated spaces www-staging, sites-staging, test-staging, wpdocs and www.bu.edu are on our production server.

Staging

A staging environment is a replica of the production, or live setting environment where internal project team members and client alike can review content, design, development features before we go live on launch day. It ensures that updates work correctly and do not disrupt the existing live site.

Example: www-staging.bu.edu/met or sites-staging.bu.edu/met or test-staging are considered ‘Staging’ Production sites.

Staging Site Requests

For a new site staging request, the creative director or project manager must contact IS&T by requesting a ticket.

For staging an existing site, the lead designer, developer, or creative director should have the project manager confirm with Jon Brousseau, a content manager, and the client before submitting the request.

Types of Staging

www-staging is regulated to content editing and redesigns.

sites-staging is meant for private, internal BU websites.

test-staging is for migration or new infrastructural testing.

Request a Staging Site


Documentation Websites

Remember to Tango

Tango is a free Chrome extension that auto-generates step-by-step documentation, saving time on theme docs, training, and user flow evaluations.

For every project and its deliverables, lead designers or developers must include well-written documentation that explains how to best utilize a product’s features for WordPress users of all experience levels. Our default Responsive Framework Documentation site is a starting point. It’s cloned for project themes to be applied to — with content expanded upon for any unique features. Its structure follows a beginner-friendly format of baseline demos, how-to guides, content advisories, and even a glossary and tooltips explaining common WordPress terminology for a beginner.

Example: wpdocs.bu.edu/cds is considered an unlisted Production site.

Starter Documentation Site

wpdocs Clone Tool

All Documentation Sites
(WordPress Login Required)


Live Setting

The live setting is where a staging site moves to on launch day. It hosts the final version of the website or component to the public.

Example: www.bu.edu/met is considered a ‘Live’ Production site.

Any website accessible on the web by either a client or the public is considered a ‘Production’ or ‘Live’ site.


Server Support

If any server is ever unreachable and WordPress is lagging, giving getting 504 errors, clone tool is broken or media is not loading: we encourage all users to make it known to @istweb in the #webteam Slack channel, following up by filing a ticket with IS&T.