Project Proposal

Freedom Project Seattle
Attn: Pax Keenen
4759 15th Ave Ne, Suite 301
Seattle, WA 98105.

 

  1.  Project Description

Our student group, the Vendor, has been asked by Pax Keenen of the Freedom Project Seattle, the Client, to redesign, produce and develop the website for the Freedom Project Seattle, the Project, to be viewed publicly via their website.

Said Project is intended to improve the effectiveness of the Freedom Project Seattle public website as to showcase the mission and services of the Freedom Project Seattle with the following requirements:

  1. Design: Creation of an on-brand website design representative of the mission and services of the Freedom Project Seattle
  2. Technology: Implementation of a Content Management System (CMS) powered by WordPress as to allow the Client to update and manage their own content

 

  1. Functional Requirements

Said Project will be produced by the Vendor with the following functional requirements:

  1. Navigation: Designed for optimum clarity including better naming conventions and visibility of which page a user is currently on.
  2. Volunteer Page: Will Include pre-screening surveys for volunteers who would like join the organisation and clearer layout.
  3. Donation Page and Links: Donations page and links that are highly visible for maximum effectiveness.
  4. Blog: Blog for news that will integrate with other Social Media (Facebook/Twitter), SEO optimization and improved deployment capability.
  5. Event Calendar: Dynamic calendar which will automatically populate from listed events.
  6. Email Newsletter Signup: Page and links for users to sign up for regular updates via email.
  7. Responsive Design: Create a website design that renders correctly on multiple mobile devices.

 

  1. Content Requirements

Said Project will be produced by the Vendor with the following content requirements:

  1. Brand Imaging: Said Project will incorporate the Freedom Project Seattle logo and brand specifications as supplied by the Client.
  2. Photographic Images: Photos for said Project will be supplied to and or will be chosen by the Vendor to be incorporated into the design of said Project. The Client will be responsible for approval and license of each photograph.
  3. Written Copy: Written information for said Project will be incorporated into said Project by the Client via a Content Management System (CMS).

 

  1. Technology Requirements

Said Project will be produced by the Vendor with the following technology requirements:

  1. Markup Code: Markup code for said Project will be written in valid HTML5 as to control the structure of website components. Said markup code will adhere to standards as set forth by the W3C.
  2. Presentation Code: Presentation code for said Project will be written with Cascading Style Sheets (CSS) as to control the design and layout of the website components. Said Presentation code will adhere to standards as set forth by the W3C
  3. Client-Side Scripting: Client-Side Scripting code for said Project will be written in Javascript as to control website item applications
  4. Server-Side Scripting: Server-Side Scripting code for said Project will be written in PHP as to control elements that interact with the server and database component
  5. Database Component: Database components for said Project will be written in MySQL as to control functionality that stores and retrieves content data

 

  1. Project Phases

Said Project will be produced by the Vendor as described in the following phases:

  1. Discovery: The Vendor will meet with the Client to clarify objectives, identify preferences, discuss goals, and analyze overall needs for said Project.
  2. Content Audit: The Vendor will conduct a content audit as to assess how present and potential written and visual content will satisfy user needs assessed during the discovery phase for said Project.
  3. Information Architecture: The Vendor will create an information architecture to describe how the structure of the (website) content will be presented based on data collected during the Discovery and Content Audit phases of said Project for the Client’s review, approval and sign off.
  4. Content Design: The Vendor will create and present a (wireframe) content design study for all inscope pages that will illustrate blocks of content, navigational schemas and user functionality that will adhere to the information architecture of said Project for the Client’s review, approval and sign off.
  5. Visual Design: The Vendor will create and present a visual design study consisting of at least three initial visual design concepts that incorporate the Content Requirements in the manner as stated above for all in-scope pages of said Project for the Client’s review, approval and sign off.
  6. Production & Development: The Vendor will be responsible for producing said Project on the  student group  development server with the Content and Technology Requirements in the manner as stated above for all in-scope pages of said Project for the Client’s review, approval and sign off.
  7. Testing: The Vendor will be responsible for testing all website pages as to ensure functionality across multiple platforms and browsers for all in-scope pages of said Project for the Client’s review, approval and sign off.
  8. Style Guides: The Vendor will be responsible for producing design style guides for all in-scope pages of said Project for the Client’s review, approval and sign off.
  9. Launch: The Vendor will be responsible for launching said Project to the Client’s server space.

 

  1. Rights of Usage

Rights of usage for said Project described as follows:

  1. The Client is granted usage rights of said Project as designed and produced by the Vendor via the World Wide Web.

2.The Vendor reserves the right to use design and development elements of said Project as case study and training materials.

 

  1. Project Terms

The Client, will adhere to terms for said Project described as follows:

Any other vendor fees such as domain registration, ISP, etc. are to be negotiated and billed separately by the respected vendors and are not the responsibility of student group.

 

H. Project Responsibilities

The Client, will adhere to responsibilities for said Project described as follows:

  1. The Client is expected to participate and be available for review and approval of all project deliverables, as described in the project phases section, according to the proposed schedule. If at any time the Project is delayed or halted by the Client, including but not limited to phase acceptance delay longer than 7 days, work on said project may be cancelled.
  2. The Client is to understand that this is a class project that is being worked on by students as a learning experience. A reasonable attempt will be made by both instructors of the class and students enrolled in the class to complete the project in a professional and timely manner. However, Seattle Central Community College cannot guarantee nor be responsible for the quality of work produced in this class.

 

  1. Project Approval

By signing this document, this Project Proposal is considered “agreed upon” by the Client and Vendor.

 

Name: _________________________________              Date: ______________

Pax Keenan, Freedom Project Seattle

4759 15th Ave Ne, Suite 301, Seattle, WA 98105

 

Name: _________________________________              Date: ______________

Akash Tolangee, Seattle Central College
1701 Broadway Seattle, WA 98122

 

Name: _________________________________              Date: ______________

Mark Pfaff, Seattle Central College
1701 Broadway Seattle, WA 98122

 

Name: _________________________________              Date: ______________

Max Diediker, Seattle Central College
1701 Broadway Seattle, WA 98122

 

Name: _________________________________              Date: ______________

Stephanie Woodward, Seattle Central College
1701 Broadway Seattle, WA 98122

Leave a Reply

Your email address will not be published. Required fields are marked *