This challenge allows you to practice the concepts and techniques learned over the past week and apply them in a concrete project. This Sprint explored User Interface and Git. During this Sprint, you studied Semantic HTML, CSS Fundamentals, CSS Flexbox Module, and Git. In your challenge this week, you will demonstrate proficiency by creating a multi page website that has some missing HTML elements as well as CSS specificity problems that need to be solved. You will also create an additional web page that will be linked to from a navigation you will build.
Read these instructions carefully. Understand exactly what is expected before starting this Sprint Challenge.
This is an individual assessment. All work must be your own. Your challenge score is a measure of your ability to work independently using the material covered through this sprint. You need to demonstrate proficiency in the concepts and objectives introduced and practiced in preceding days.
You are not allowed to collaborate during the Sprint Challenge. Your work reflects your proficiency in user interface and your command of the concepts and techniques in semantic HTML, CSS fundamentals, CSS flexbox module, and git.
Commit your code regularly and meaningfully. This helps both you (in case you ever need to return to old code for any number of reasons)
In this challenge, you build a missing header (navigation and image) on the home page, update some CSS styling on the home page, and create an additional page (About) which will link from the navigation you created.
In meeting the minimum viable product (MVP) specifications listed below, your web page should look like the solution screen shots of the home and about pages (found in the design-files folder):
Click here for the home page example
Click here for the about page example
(please edit this file and write your answer below each question. In addition, you may also review these questions with your mentor)
Demonstrate your understanding of this week's concepts by answering the following free-form questions.
Edit this document to include your answers after each question. Make sure to leave a blank line above and below your answer so it is clear and easy to read.
- If you were to describe semantic HTML to the next cohort of students, what would you say?
it is using tags that describe what they are surrounding. they make it a little easier to remember what tags to use for what you are putting inside of them.
- Name two big differences between
display: block;anddisplay: inline;.
block elements take up the entire width provided and push the next item to the next line, whereas inline elements only take up as much room as they have to. also, inline elements cannot take a width or height.
- What are the 4 areas of the box model?
the four areas of the box model are as follows: content>padding>border>margin
- While using flexbox, what axis does the following property work on:
align-items: center?
when using align-items:center; the items are centered in the cross-axis.
- Explain why git is valuable to a team of developers.
git is helpful and valuable because each person can be working on a branch of the main project and it will not interfere with anyone else's work, but they can still merge and communicate those branches back together when they are finished. its like everyone has a different posterboard and is working on different pieces of that poster, but instead of one person having to look at all of the ideas and copy the ones that they like, all of the posters can just easily become one. and you all have a copy on your own computer! its brilliant!
You are expected to be able to answer all these questions. Your responses contribute to your Sprint Challenge grade. Skipping this section will prevent you from passing this challenge.
- [+] Create a forked copy of this project.
- [+] Clone your OWN version of the repository (Not Lambda's by mistake!).
- [+] Create a new branch: git checkout -b
<firstName-lastName>. - [+] Implement the project on your newly created
<firstName-lastName>branch, committing changes regularly. - [+] Push commits: git push -u origin
<firstName-lastName>.
Follow these steps for completing your project.
- [+] Submit a Pull-Request to merge Branch into master (student's Repo). Please don't merge your own pull request
Your finished project must include all of the following requirements:
Review the provided design file for the home page. Notice the navigation and header images are missing.
- [+] Build the HTML and CSS to create the missing navigation and header.
- [+] Link the
Aboutnavigation item to the about.html page
You will also notice there are 10 boxes on the home page that need background colors. Use this list below to correctly style each box:
- [+] box1:
teal - [+] box2:
gold - [+] box3:
cadetblue - [+] box4:
coral - [+] box5:
crimson - [+] box6:
forestgreen - [+] box7:
darkorchid - [+] box8:
hotpink - [+] box9:
indigo - [+] box10:
dodgerblue
Review the provided design file for the about page. You have been provided the HTML wrapper, footer, and page content for the about page. Create the rest of the missing HTML and CSS to match the design file.
- [+] Copy and paste your home page navigation and header into the about page
- [+] Update the header image with the about page image
- [+] Link the
Homenavigation item back to theindex.htmlpage. - [+] Build the rest of the about page layout to match the design
In your solution, it is essential that you follow best practices and produce clean and professional results. Schedule time to review, refine, and assess your work and perform basic professional polishing including spell-checking and grammar-checking on your work. It is better to submit a challenge that meets MVP than one that attempts too much and does not.
Note: Please make sure you are using flexbox to layout your website. Floats, inline-block, tables, etc, should not be used for layout.
After finishing your required elements, you can push your work further. These goals may or may not be things you have learned in this module but they build on the material you just studied. Time allowing, stretch your limits and see if you can deliver on the following optional goals:
- [+] refactor your HTML, make sure it's indented properly, clean, readable, you have written appropriate comments where necessary and that all attributes (required and encouraged) are filled out correctly.
- [+] Ensure your CSS is organized and readable, you've seperated your code by section and that you are using descriptive class names and adding classes in your HTML where styles repeat rather than rewrting the same styles over again
- [+] Use a flex item property of your choice when laying out a section of your website, ensure you can explain how and why you've used this property