<commit_before># COMP1950 Final Project

<div class="contblock">
<h3>Project Overview</h3>
<p>Using production methods and development techniques from throughout this course, your group will create a proto-site and documents to support the redesign of the COMP1950 web site.</p>


<h3>Requirements</h3>
<p>The COMP 1950 owner would like the web site redesigned in order to better meet the needs of students.  The website owner has contracted your group, as students of the class, to act as contractors for this project.</p>

<h3>Project Goals</h3>
<ul>
	<li>Students must have easy access to notes, examples and other information</li>
	<li>The site should reflect the aims of the course: Standards compliant web development, CSS, HTML 5, Methodology-driven design, etc</li>
	<li>Think outside the box - don't just copy the current design.  Look around at other sites and use your creativity.  But - be realistic!  Make your suggestions something that can work</li>
	<li>If you have questions that will further refine your own direction, ask the owner of the site for details</li>
	<li>Think about this project in context of the Methodology discussion of session 10.</li>
	<li>Your client (instructor) has filled out a <a href="http://bcitcomp.ca/comp1950/downloads/project_questionnaire_filled_out.pdf">project questionnaire </a> to better clarify what they are looking for.</li>
</ul>

<h3>Deliverables</h3>
<ul>
	<li>For this project, you have been contracted to provide a protosite and supporting documents for the proposed website</li>
	<li>You will create a web site that describes the project and includes links to various project artifacts.  This is generally known as a <em>meta site</em>. Note the meta site is about the entire redesign project, it will include the proposed site redesign, but it is not itself the redesign. It should have its own appealing design and layout, distinct from the proposed site redesign</li>
	<li>The meta site should include: </li>
	<li>An <strong>Introduction</strong> page that describes the project and the members of the team.  This page should also list what each team member actually did during the project, and provide a navigation for the rest of the project web site.</li>
	<li>A <strong>proto-site</strong> that has at least four of the pages mocked up.  Preferably pages that are representative of different page types, eg: the home page, a lecture page an example quiz page, etc. The mockup pages must be styled to reflect the website you propose to build. It should demonstrate the proposed layout, color scheme, font choices and an example site navigation. All proto-site pages should have two optional stylesheets: one normal view, one for the in-class overhead projector. They should also feature a printer optimized stylesheet.</li>
	<li><strong>Sitemap</strong> should demonstrate the proposed website information architecture by showing a site map. The links of the sitemap dont need to link to anything. (<a href="http://bcitcomp.ca/1950/lectures/eleven/sitemap.html">Example sitemap</a>) (HTML, Word or Visio)</li>
	<li><strong>Rationale</strong> page - this is among the most important pages in your project. This is your chance to 'sell' your efforts to your client instructor. This is where you describe <strong>why</strong> you chose to build the site in the way you have proposed. List all the deliverables you have implemented, and and any features or improvements you have added. Justify your decisions for choosing a particular layout and design. If you used advanced technology such as jQuery or CSS3, mention where it is being used, and why. Also List any features you had planned to implement but could not complete. If your rationale does not decribe a sufficient quantity of improvements, and if it does not effectively make a case for how these changes improve the site, your client will not be conviced that your team is the best choice.</li>
	<li>All of this should be presented in an <em>HTML 5 compliant web site with CSS</em></li>
	<li>The layout must handle well in desktop and laptop <em>modern browsers</em> with varying widths and heights. It does not neccessarily have to be optimized for handheld devices, unless your group decides this would be a useful feature.</li>
	
</ul>

<h3>Teamwork</h3>
<ul>
	<li>This project will require work from all members of your team</li>
	<li>Start by agreeing on a plan of attack - get agreement!</li>
	<li>Begin making decisions on how the site will look, what functions it needs to have, how users will access information</li>
	<li>Draw some sketches for how it could look, think about labels and information design</li>
	<li>Once you know what needs to be on the site and how it will look, divide up the work for the entire project. Make sure your team knows who is doing what</li>
	<li>There is plenty to do, you may have to be willing to delegate tasks you might otherwise prefer to do yourself</li>
</ul>
 

<h3>Validation and Presentation</h3>
  <ul>
    <li>All content must be valid HTML 5 (exceptions allowed for non-structural errors)</li>
    <li>All presentation must be valid CSS</li>
    <li>Add a link on each page to validate:
        HTML: <a href="http://validator.w3.org/">http://validator.w3.org/</a>
     </li>
    <li>Exceptions will be made for non-structural errors (eg: query strings)</li>
    <li>Code must be commented and tabbed</li>
    <li>SEO principles must be followed on all documents</li>
    <li>Demonstrate to your client that your team takes pride in their work by ensuring the entire meta-site and proto-site experience is built with care. </li>
  </ul>
	

<h3>Remember!</h3>
    <ul>
        <li>Look at the existing site, but don't necessarily base your new site on that one. Think outside the box! Be creative!</li>
	<li>As a student, <em>YOU are the audience</em>.  Talk to your cohorts, spend time considering the current experience, design the site the way you think it would work best.</li>
        <li>You <strong>do not</strong> have to include actual notes for the class.  This project is to produce a proof-of-concept of the new COMP 1950 site</li>
        <li>Be sure to schedule time to 'bring it all together' before due date.</li>
    </ul>

<h3>Submission</h3>
    <ul>
	<li><strong>The final project is due by midnight the night before session #12.</strong>	</li>
	<li>Once complete, have your team representative email a URL for your project site to your instructor</li>
    </ul>
</div>
<commit_msg>added link to contract<commit_after># COMP1950 Final Project

<div class="contblock">
<h3>Project Overview</h3>
<p>Using production methods and development techniques from throughout this course, your group will create a proto-site and documents to support the redesign of the COMP1950 web site.</p>


<h3>Requirements</h3>
<p>The COMP 1950 owner would like the web site redesigned in order to better meet the needs of students.  The website owner has contracted your group, as students of the class, to act as contractors for this project.</p>

## <a href="http://bcitcomp.ca/comp1950/downloads/project_questionnaire_filled_out.pdf">Contract</a>

<h3>Project Goals</h3>
<ul>
	<li>Students must have easy access to notes, examples and other information</li>
	<li>The site should reflect the aims of the course: Standards compliant web development, CSS, HTML 5, Methodology-driven design, etc</li>
	<li>Think outside the box - don't just copy the current design.  Look around at other sites and use your creativity.  But - be realistic!  Make your suggestions something that can work</li>
	<li>If you have questions that will further refine your own direction, ask the owner of the site for details</li>
	<li>Think about this project in context of the Methodology discussion of session 10.</li>
	<li>Your client (instructor) has filled out a <a href="http://bcitcomp.ca/comp1950/downloads/project_questionnaire_filled_out.pdf">project questionnaire </a> to better clarify what they are looking for.</li>
</ul>

<h3>Deliverables</h3>
<ul>
	<li>For this project, you have been contracted to provide a protosite and supporting documents for the proposed website</li>
	<li>You will create a web site that describes the project and includes links to various project artifacts.  This is generally known as a <em>meta site</em>. Note the meta site is about the entire redesign project, it will include the proposed site redesign, but it is not itself the redesign. It should have its own appealing design and layout, distinct from the proposed site redesign</li>
	<li>The meta site should include: </li>
	<li>An <strong>Introduction</strong> page that describes the project and the members of the team.  This page should also list what each team member actually did during the project, and provide a navigation for the rest of the project web site.</li>
	<li>A <strong>proto-site</strong> that has at least four of the pages mocked up.  Preferably pages that are representative of different page types, eg: the home page, a lecture page an example quiz page, etc. The mockup pages must be styled to reflect the website you propose to build. It should demonstrate the proposed layout, color scheme, font choices and an example site navigation. All proto-site pages should have two optional stylesheets: one normal view, one for the in-class overhead projector. They should also feature a printer optimized stylesheet.</li>
	<li><strong>Sitemap</strong> should demonstrate the proposed website information architecture by showing a site map. The links of the sitemap dont need to link to anything. (<a href="http://bcitcomp.ca/1950/lectures/eleven/sitemap.html">Example sitemap</a>) (HTML, Word or Visio)</li>
	<li><strong>Rationale</strong> page - this is among the most important pages in your project. This is your chance to 'sell' your efforts to your client instructor. This is where you describe <strong>why</strong> you chose to build the site in the way you have proposed. List all the deliverables you have implemented, and and any features or improvements you have added. Justify your decisions for choosing a particular layout and design. If you used advanced technology such as jQuery or CSS3, mention where it is being used, and why. Also List any features you had planned to implement but could not complete. If your rationale does not decribe a sufficient quantity of improvements, and if it does not effectively make a case for how these changes improve the site, your client will not be conviced that your team is the best choice.</li>
	<li>All of this should be presented in an <em>HTML 5 compliant web site with CSS</em></li>
	<li>The layout must handle well in desktop and laptop <em>modern browsers</em> with varying widths and heights. It does not neccessarily have to be optimized for handheld devices, unless your group decides this would be a useful feature.</li>
	
</ul>

<h3>Teamwork</h3>
<ul>
	<li>This project will require work from all members of your team</li>
	<li>Start by agreeing on a plan of attack - get agreement!</li>
	<li>Begin making decisions on how the site will look, what functions it needs to have, how users will access information</li>
	<li>Draw some sketches for how it could look, think about labels and information design</li>
	<li>Once you know what needs to be on the site and how it will look, divide up the work for the entire project. Make sure your team knows who is doing what</li>
	<li>There is plenty to do, you may have to be willing to delegate tasks you might otherwise prefer to do yourself</li>
</ul>
 

<h3>Validation and Presentation</h3>
  <ul>
    <li>All content must be valid HTML 5 (exceptions allowed for non-structural errors)</li>
    <li>All presentation must be valid CSS</li>
    <li>Add a link on each page to validate:
        HTML: <a href="http://validator.w3.org/">http://validator.w3.org/</a>
     </li>
    <li>Exceptions will be made for non-structural errors (eg: query strings)</li>
    <li>Code must be commented and tabbed</li>
    <li>SEO principles must be followed on all documents</li>
    <li>Demonstrate to your client that your team takes pride in their work by ensuring the entire meta-site and proto-site experience is built with care. </li>
  </ul>
	

<h3>Remember!</h3>
    <ul>
        <li>Look at the existing site, but don't necessarily base your new site on that one. Think outside the box! Be creative!</li>
	<li>As a student, <em>YOU are the audience</em>.  Talk to your cohorts, spend time considering the current experience, design the site the way you think it would work best.</li>
        <li>You <strong>do not</strong> have to include actual notes for the class.  This project is to produce a proof-of-concept of the new COMP 1950 site</li>
        <li>Be sure to schedule time to 'bring it all together' before due date.</li>
    </ul>

<h3>Submission</h3>
    <ul>
	<li><strong>The final project is due by midnight the night before session #12.</strong>	</li>
	<li>Once complete, have your team representative email a URL for your project site to your instructor</li>
    </ul>
</div>

{'fraction_non_alphanumeric': 0.07619921964654579, 'fraction_numerical': 0.0079565450233341, 'mean_word_length': 4.305194805194805, 'pattern_counts': {'":': 0, '<': 265, '<?xml version=': 0, '>': 265, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 3, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1389999', 'n_tokens_mistral': 3561, 'n_tokens_neox': 3397, 'n_words': 1893}