Content Developer Overview
During the meeting I hope to accomplish the following tasks:

1. How to create a storyboard
2. What are production standards
3. How to make up a list of deliverables.
4. What is a shell site and why do you create one
5. How much content have you received from the client
6. Team relations
7. Client relations
8. CD's responsibilities
9. The project development cycle and your place within the cycle
10. Review the HTML certification process

Document which may prove useful is the Class Meeting Schedule

One key element in the content Developers role is the completion of the HTML Certification Exam, more information is included in the links below. Some of you may find that the first few weeks of class are slow for you. This may be a good time toget the exams out of the way so whent he class gets busy later on, you have already completed the exams. If you have questions about the exams please send me a note.

HTML certification explained
Sign up for HTML Testing
Review HTML test schedule

Content Developer's Responsibilities

Attend the client meeting. Since you will be responsible for creating a large # of the pages make sure you speak up if the size and scope of the project seems to be getting out of hand. You also need to make sure the client understands what data needs to be brought to the content meeting. Since you will be handing the files make sure they come to you in a format you can handle. also determine who will be maintaining the site and if you will be required to provide training. Review the elements of HTML which the team is considering for the project. If your table code, form, or Cascading Style Sheet code is a bit rusty. Drag out the book and brush up on the concepts. Make sure you understand what information the client wants to include since you will be responsible for creating those pages.

Relax and enjoy the experience. This is a great group of people. The clients are grateful for your help, your teammates want to like you. Everyone is nervous and a bit confused - it will wear off in about 18 weeks. :->. When you attend the meeting dress in appropriate business attire (suit and tie is not necessary but maybe one step above student grunge). If the client seems really casual you can wear whatever you want to the subsequent meetings, but it never hurts to look professional the first time. Develop a plan for folks who are late to the client meeting

The first assignments which you need to complete all involve creating elements which will be included in the Web Proposal. Each member of the team is responsible for contributing to this document. The CD creates the storyboard, deliverables, and production standards.The shell site will also be created by the CD but it may not be done by the proposal due date since the client may not have supplied all the content.

If you are on a team with 2 CDs the PM will assign each of you specific tasks for the proposal. If you are the only CD on a team you will need to create all 4 items

1. Analyze client content
   This is done from the first client meeting (if the client has content) and must begin by 9/24when 40% of the content is due. 80% of the content is due by 10/8. All content must be in by 10/22 . Please do not accept content after that date unless you have instructor approval. As you analyze client content - do not hesitate to ask the client questions if you do not understand where the content goes or have problems opening the content files.

2. Create a storyboard based on the content and the client needs. This is a series of boxes which are a picture of the site. Use one box for each page and show the hierarchy and structure of the site. Create a rough draft of the storyboard right after the first meeting. Run it by your team for their approval, and then show it to the client as soon as possible. The storyboard is based on what the client asks for in their site, if you are unclear on the storyboard you need to ask your PM for guidance, or contact the client for clarification
   
   The storyboard is a crucial element since the deliverables and design are based on this document. Since the designer will want to start making comps right away, create a rough storyboard asap after the first meeting. This can be an email storyboard where you describe the main navigational items in words, or a hand drawn flow chart that is sketched on a piece of paper and shared with the designer.
   
   Examples of storyboards include:
   TLT - http://www.sonic.net/~webclass/TLT/storyboard.html
   Petaluma Arts Council - http://www.thedrexlers.com/final/storyboard.html
   Friends House - http://www.sonic.net/~webclass/BusWeb/friends/storyboard.html

3. Create Production Standards which describe how the files will be stored and what the files will be named. Where will the web pages, pdf files, scripts, images, css and if applicable ssi files be stored?This document helps the Designer and Content Developer understand where all the files are put and what the linking code should be. The best way to represent the production standards is with a screen shot of the folders and files and a written description of the file names and storage system. See the examples below.
   
   The due date for the production standards is 10/15 . Once again the CD may create a rough version of this document at an earlier date, since in order to create the shell site, you need to have the production standards in place.
   
   Examples of Productions Standards include:
   TLT - http://www.sonic.net/%7Ewebclass/BusWeb/TLT/standards.html
   Culinary Arts - http://davidswilliams.com/srjc/project/project/standards.asp
   

4. List of Deliverables (your teammates help you create this document) This is a detailed list of what the client will receive, include the number of pages, the images you will provide, any scripts you create, PDF files, training, marketing, etc. Make this document very detailed to avoid confusion later.
   view example
   
   This document cannot be created entirely by the Content Developer, they need to send email to their teammates asking them what they will be contributing. The designers submit a list of graphics, programmers submit scripts and forms, and the content developers list the web pages, training, and marketing. It is due 10/15 .
   
   Remember we have small teams, so don't bite off more than you can chew, a small list of deliverables which can be delivered on time, is better than a long list which never gets done or wipes out the team.

   Examples of deliverables include:
   SRT - http://www.sonic.net/~webclass/BusWeb/srt-del.html
   Petaluma Arts Council - http://www.thedrexlers.com/final/deliverables.html
   TLT - http://www.sonic.net/~webclass/TLT/deliverables.html
   Friends House - http://www.sonic.net/~webclass/BusWeb/friends/deliverables.html

5. Create shell site
   A shell site is defined as a web site which has the content displayed on all the pages which will eventually make up the site, but does not look like the finished product. The pages are plain white pages, with black text, and blue links. The purpose of the shell site is for the Content Developers to become familiar with the site and for the client to get a preview of how the site will navigate and flow.
   
   This project begins as soon as content is provided by the client and is due 10/22 . The deadline for 40% of content is 9/1780% of the content is 10/8. If you do not feel the content is coming in quickly enough, talk to your Project Manager. If that does not help, send your instructor a note
   
   Examples of a shell site
   TLT shell site
   Kenwood Pillow Fights shell site
   
6. Complete the HTML certification exam process. Review information about How the HTML Exams Work. If you have any questions about this process please contact your instructor.
   
7. Convert shell site to client pages which incorporate the designer's template
   We have a class meeting set for 10/29when the designers and content developers will review the template code with your instructor. After that date the code should be ready to duplicate. If you do not understand the code, set up an appointment with your instructor, I am happy to help.

8. Perform Typical User Testing
   This begins after the class meeting on 11/26must be completed 12/10.

9. Contribute to the bid revision
   This is partially completed every time you complete a team report. The actual bid will be created by your Project Manager and is due 12/17.

10. Contribute to the Client manual
    The client manual is due . 12/17

Content for these teaching materials were developed by Linda Hemenway. If you have questions or comments on the material I can be contacted through
lhemenway@santarosa.edu
(707) 527-4855

Web site design by Jessica Hirsch - jessicahirsch@email.msn.com

Funding for these notes provided by Project FIVE and Project PICTS supervised by Doug Garrison - Dean of the Petaluma Center.