Goal: Familiarize yourselves with the usage of inline HTML elements while continuing to practice Git, indentation and spacing. Inline HTML elements are an important building block of most any website, so it's important to become comfortable with them now.
Discuss the following with your partner:
alt
attribute on an image necessary?Here are some exercises for you to practice using inline HTML elements. Don't forget to commit your changes and push to your remote repositories on GitHub. Continue to make sure you are using proper indentation to keep your code clean and readable!
<strong>
and <em>
tags to your my-first-webpage.html
, like I did in the lesson.favorite-things.html
page. Make an img
folder to hold these photos and make sure the path is correctly written on your webpage.favorite-things.html
page, add links to your favorite websites.<strong>
and <em>
tags.The "Further Exploration" section contains additional exercises and activities to explore if all other coursework for the day has been completed.
If you and your partner have completed each of today's lessons and exercises thoroughly with time to spare, below are some additional activities to get started on. Continue practicing implementing HTML elements, tracking changes with Git, correct indentation and spacing and pushing to Github.
Programming does not happen in a vacuum. It requires collaboration and communication. By reviewing the code of a peer, you are able to see alternative solutions to the same problems that you were tackling. You will also experience what it feels like to walk into a code base that you have not contributed to before — something that will be a regular occurrence outside of Epicodus.
At roughly 4:15 pm, plan to begin reviewing the code of your peers. It's all right if you aren't finished with your own code for the day yet. This is a friendly and informal process.
Open the code from a site you've created today in your text editor. Then open the corresponding GitHub repository in the browser. Finally, review the code of a pair across from you. They will review yours. Look at their code and provide feedback on the following questions:
Also, ask questions. Clarify areas you may not understand. Share ideas. Offer advice and perspective. Admire and support your peers. Embrace the opportunity to support and congratulate each other on completing your first day of code school!