Information For

E-mail this page to a friendE-mail this page

Overview of the Official Web Development Process

Step 1: Meet with the Web Editor

Once you have been identified as a content provider, schedule a meeting with the Web Editor. This initial meeting provides a brief overview of the tools the college uses, web standards, what constitutes good web writing, and what research shows to work best on the web.

How to Contact the Web Editor

Step 2: Attend WIDGET Training

After your initial meeting with the Web Editor, you may be asked to attend a WIDGET training session. WIDGET is the college's content management system.

Step: 3: Follow-Up Meeting with the Web Editor

After you have completed WIDGET training, schedule a brief follow-up meeting with the Web Editor.

Step 4: Content Development

The development process will follow a development timeline. Both web developers and content providers will have assignments and due dates. However, Deans may re-prioritize projects, which may impact timelines and deadlines.

Initial development is done on the Development server. This is a sort of "sandbox" that allows you to explore your ideas.

The final, and crucial, part of this step is the editorial review process. Although the web development team maintains editorial control, content providers still control their messages. The function of the editorial process is to clarify your messages, ensure accessibility, and consistency.

Step 5: Site Launch

Once good content has been written and an effective site has been built on the Development server, the site is migrated to the Production server.

Changes made on this server are live. Accordingly, development on this server is limited to updating and fixing content. Creating new pages and modifying the navigation is limited to the Development server. You are still encouraged to develop new content, but any additional development needs to follow the process outlined here.

Step 6: Maintenance, Updating and Assessment

As we know, work on your website is never really "done." Think of it as a process rather than a destination. You should think of your website as an open-ended conversation with your audiences.

Once a site is in maintenance mode, content providers are encouraged to make corrections and updates as needed. However, you must notify the Web Editor or Associate Web Editor of any changes made on the production server.

These pages are live, so it is critical that they be proofed for proper XHTML, structure, acceptable images size, etc. This can be done easily via e-mail, indicating that some updates have been made and by providing the URL of the page. This allows us the chance to catch any possible problems as soon as possible.

It is your responsibility to ensure that your content is up-to-date, that links work, and that you are continuing to meet your audiences' needs. Your students are an excellent resource.

Contact Dan Lewis for more details about how to work with your students to assess the content on your site.

Questions, Comments, Suggestions?

If you have questions about SUNY Plattsburgh web policies, or want to learn more about how to write for the web, please contact:

Office of the Web Editor
Daniel J.S. Lewis, Web Editor
Phone: (518) 564-3977

Was this page helpful?

This is an official publication of SUNY Plattsburgh

Copyright © 1996-2009 SUNY Plattsburgh 101 Broad Street, Plattsburgh, NY 12901 Phone: (518) 564-2000