Skip to content
This repository was archived by the owner on Jan 14, 2024. It is now read-only.

NorthWest Class - Alexandra Ciungan - HTML CSS Week 1 - #84

Closed
allosaurus1 wants to merge 2 commits into
CodeYourFuture:masterfrom
allosaurus1:master
Closed

NorthWest Class - Alexandra Ciungan - HTML CSS Week 1#84
allosaurus1 wants to merge 2 commits into
CodeYourFuture:masterfrom
allosaurus1:master

Conversation

@allosaurus1

Copy link
Copy Markdown

Volunteers: Are you marking this coursework? You can find a guide on how to mark this coursework in HOW_TO_MARK.md in the root of this repository

Your Details

  • Your Name:
  • Your City:
  • Your Slack Name:

Homework Details

  • Module:
  • Week:

Notes

  • What did you find easy?

  • What did you find hard?

  • What do you still not understand?

  • Any other notes?

Comment thread index.html
<!-- Remember: Use semantic HTML tags like <header>, <main>, <nav>, <footer>, <section> etc -->
</body>
</html>
<div id="side">

@mike-shields-cyf mike-shields-cyf Jun 16, 2021

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although a navigation was not asked for in the assignment, remember to use semantic html tags. For navigation links, the parent element should be a nav element rather than a div. Using a nav would also remove the need to add the class of nav to your navigation links. You could target the navigation links in the stylesheet using the selector below:

nav a {
    /* styles... */
}

It might also be better to have only navigation links in a nav and a menu toggle button (hamburger) if needed. Consider moving the image in this section to somewhere else, maybe the <header>. This would also solve the issue of the image and the links all flowing on the same line.

This portion of html also belongs inside the <body> because it is intended to be seen by the user.

Comment thread index.html
</div>
</section>
</body>
<footer>

@mike-shields-cyf mike-shields-cyf Jun 16, 2021

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The <footer> is intended to be seen by the user, so it should be nested inside the <body> element.

Comment thread index.html
<a href="#social" class="nav"><img src="http://png.findicons.com/files/icons/2260/iphone_toolbar/26/plus.png" width="12" class="xtra_icon">&nbsp;&nbsp;Social</a>
</div>
<br>
<body>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please include the following:

  • A page <header> with a title and description for the site.

    • Maybe you could take the .content section and convert this to your <header>?
  • An articles section with three articles, each including a title, summary and a link.

    • It's great that you have separated your content using <section> elements,
      maybe you could swap these section elements for <article> elements and nest them inside a ``
      ``` element with the name of articles. Make sure your article elements each have a title, summary and a link.

Comment thread index.html

<section id="social">

<div>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Try to keep your html "shallow", by this I mean try not to create unneccesary nesting. This div does not serve any purpose as the elements inside it could be direct children of the #social element.

@github-actions

Copy link
Copy Markdown

Your coursework submission has been closed because nobody has interacted with it in six weeks. You are welcome to re-open it to get more feedback.

@github-actions github-actions Bot added the Stale label Jul 29, 2021
@github-actions github-actions Bot closed this Jul 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants