Jeff IT Self-Service Forms
New Web Development
Contribute    |    Best Practices    |    Contact Jeff IT   |

Below describes the process in developing a new website per the new Jefferson web template.

There are two paths to be considered based on how your website is maintained. All new sites are Contribute-ready offering departments the vehicle to do minor content changes to their sites. View process flow.

Need to update an existing site?

In with the new...

Jeff IT will import current jefferson.edu websites into the newly branded template and place the sites on a secure staging server. There are two maintenance paths:

  • Jeff IT maintains the site
  • The department maintains the site via Contribute

The process to bring your current Jefferson.edu website into the new Jefferson branded template is detailed below:

Jeff IT contacts the site liaison, as identified by the Department Chair,
to meet about the site update and departments objectives.
Jeff IT Maintains Site

  1. Jeff IT presents the site on a
    staging server
  2. Reviews the content structure/organization
  3. Discusses updates, new content or additional needs per the department’s objectives
Department Maintains their Site
(via Contribute)

  1. Jeff IT presents the site on staging server
  2. Reviews the content structure/organization
  3. Discusses updates, new content or additional needs per the department’s objectives
  4. Liaison identifies – else confirms – parties to manage site
  5. Reviews and presents the new Contribute template
  6. Jeff IT trains department representative(s) per the new template
Jeff IT assigns department folder on JeffShare to upload new/revised content and pictures Jeff IT assigns department folder on JeffShare to upload new/revised content and pictures
Jeff IT updates the site using the content as placed by the department liaison in JeffShare folder. Liaison and Jeff IT collaborate in updating/adding content to department site in tandem >> communication is KEY
Jeff IT conducts quality assurance (QA) process prior to releasing to department for their review. The QA Cycle is driven by the size and complexity of the site and will be estimated on a site-by-site basis.
At the least, Jeff IT will need five business days, at the minimum,
for sites that are less than 10 pages without applications.
Know that Jeff IT performs QA as a value-added service. Though thorough as humanly possible,, the client assumes the final responsibility for accuracy and completeness of the content on their web site.
The department reviews the site (prior to Jeff IT's QA and Pre Launch).
At minimum, anticipate at least two review cycles allowing for two weeks
to get through both Jeff IT's QA and your department review.
NEW Jeff IT Change Management Approval Process
Jeff IT is obligated to track changes and their respective approvals to our web servers.
No changes can be made without formal approvals.

This constitutes new web sites (ie. the new brand), changes to site navigation, adding/deleting pages,
this does not include content changes (text and images on existing pages).

This is a two step process: Step 1, as the client, you will need to formally approve
the testing of your site (the testing is via the QA process).
Click here for STEP 1 instructions on how to approve.
[total time needed: 5 minutes]
The Medical Director (the party who is responsible for the content) sends Jeff IT an official release, (KT Ferrera, Associate Director, WAS), stating the specifics of the expectation:

‘This email is to confirm that I have reviewed the website and hereby authorize Jeff IT to replace (current URL) with the site located at vm48.jefferson.edu/______ on [date]. I understand that the Jeff IT QA was performed as a courtesy and that I am responsible for the content on this web site.’
Jeff IT captures the site a PDF and the site is migrated to Jefferson.edu
from the Contribute staging server.
The QA Sheets, the release email and the PDF web site capture is kept as record of the request.
NEW Jeff IT Change Management Approval Process
Final Step of Approval Process: Production Testing
After the site is on www.jefferson.edu, you will go to the new site to verify all is intact as was testing against vm48. If you find the site is in order, you will need to check the client approval on the Change Management form. Click here for detailed STEP 2 instructions.
[total time needed: 5 minutes]
The department updates the content via Contribute


Contribute: Manage your web content
(aka University Website Management System)

Contribute is an Adobe product that allows non-HTML web professionals to manage their content on their TJU websites. You can edit copy, add pictures, and create links and new pages. Jeff IT will train you on how to get the most out of using Contribute to maintain your website. Jeff IT is available to assist you in requests that may require more than a typical Contribute layout.

Getting Started with Contribute at Jefferson:
  1. Purchase a Contribute license from the University Bookstore. Fax the receipt to (215) 503-2648, to the attention of Brian Borowski.
  2. Jeff IT will add you to the Contribute server, assigning you, (and any other designees), to your website.
  3. Make arrangements to be trained on Contribute per the new branding initiative.

Best Practices

Items to consider as you prepare your content:

Key Messages: what is the first and second concept/idea that you want your visitors to capture without ‘studying’ the page?

Identify target audience: who are they and how are they reached, what motivates them?

Outline: organize content from overview to detailed information in delivering your message -- note this will drive the sub navigation of your site.

3-click guideline: web principle that suggests that a user should be able to find intended or sought out information within 3 clicks.

Concepts/Images: what is the nature of your discipline?

Copy/Editorial: who will be the point person in delivering and then approving the content?

Less is more theory: you do not want to overwhelm users with too much information, graphics or accessory applications, particularly at initial landing pages.

date revised 07/08/10


Click to leave feedback
feedback