Skip to content

Maria-Hidalgo/refresher-exercise

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Refresher Exercise: BSM Website

The purpose of this assignment is to review material covered in weeks 1-5 of class

Roles: Timer, Typer and/or consolidator, Submission Manager, Contributors, Auditor (ensures completion of requirements and asks clarifying questions to me in Slack).

Text editor: You can use any text editor you would like to complete your project

Submission: Fork the project and create a pull request when complete. 1 pull request per group. (https://github.com/Phillip-Generation/refresher-exercise)

Remeber: Most important part of this activity is to work as a team to write the code to fulfill the requirements below.

Tip: Make use of your resources (Google, codecademy, w3schools.com, MDN Web Docs)

Notes:

  • We will not be answering technical questions during the assignment.
  • Not a graded assignment. If you do not finish all requirements, it is OK.
  • Be creative and have fun!

Requirements:

  • Select a BSM that will be the subject of your site
  • Fork the project found here: https://github.com/Phillip-Generation/refresher-exercise
  • Clone a copy of the project to your local machine
  • Basic structural elements (ex. document type declaration, head tags, body tags, html tags)
  • Page title element inside of appropriate tag
  • A main heading, and 2 sub headings
  • Use of at least 3 paragraph tags
  • A link to usa.generation.org
  • A link to https://www.w3schools.com/ that opens in a new window
  • Use of whitespace and indentation to make code easily readable.
  • 1 table with at least 5 rows and 3 columns
  • At least one row must span 2 columns
  • 1 form containing:
    • 3 Fields and label for text input
    • One of the fields should accept accept input type password
    • Field and label for number input
    • Option for range input
    • Checkbox input
    • Radio button input
  • A nav section with at least 2 links that takes the user to other parts of the page.
  • One instance of inline CSS
  • One instance of internal CSS
  • All other CSS in a linked stylesheet
  • At least 2 uses of each: style by tag, style by class, style by id.
  • One use of multiple classes on a single element
  • A footer with the names of your team members.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors