Skip to content

Latest commit

 

History

History
62 lines (36 loc) · 2.78 KB

final_project_requirements.md

File metadata and controls

62 lines (36 loc) · 2.78 KB
Raw

GeneralAssemb.ly

#FEWD: FINAL PROJECT

##DESCRIPTION

The final project for FEWD will be to design and build a website of your choice. This project will test your knowledge of front-end web development, and it encapsulates everything you’ve learned in this course. The result will be a site that can be used in your portfolio.

The objective of this project is to: • To demonstrate understanding of all topics covered during this course. • To apply knowledge gained during this course by building a website from the ground up. • To combine technical and design skills to create an efficient website that is compatible with all the latest modern browsers and devices.

We encourage you to exercise your creativity; instructors will validate feasibility and manage scope. Below are the core requirements that must be included.

##CORE REQUIREMENTS

  • Demonstrate the process to plan and build your website by submitting all milestones. (see below)

  • Use HTML to correctly structure the DOM.

    • Use HTML5 structural elements (header, footer, nav, footer).

    • Demonstrates correct use of classes and IDs. Use classes for identifying a type of element, and IDs for identifying a specific unique element on the page.

    • Selects appropriate tags to markup content.

  • Styled with CSS

    • Demonstrate apply fonts, color to a page.

    • Demonstrate use floats and the box model.

  • Interactive

    • Make use of JavaScript/jQuery events to add interactivity to the page.

##MILESTONES

Milestone # Due Date Deliverable
Milestone 1 Week 05 Project Proposal / Wireframes
Milestone 2 Week 07 Pseudo Code
Milestone 3 Week 08 First Draft

##DELIVERABLES

Project folder with HTML/CSS, JS and all necessary assets.

##BEST PRACTICES

Your instructional team will provide feedback on how well you execute best practices. Even though it is not part of the requirements, you should keep these in mind.

  • Clean And Readable Code. The instructional team should be able to read and follow code easily. Maintain clean and readable code including: consistent indentation, code commenting (e.g. when closing <div> tags, demarcating sections of code, describing possibly ambiguous code choices) and use proper and consistent naming conventions.

  • Search Engine Optimization (SEO). Implement SEO best practices related to HTML markup, and content optimization.

  • Avoid deprecated tags. Uses best practices and build using supported HTML and CSS tags.

##GRADING

A project is considered satisfactory if it meets all core requirements and submitting all milestones.