Skip to content
This repository has been archived by the owner on Oct 26, 2020. It is now read-only.

Html css mb week2 #62

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

MartinBoylan
Copy link

Week 2s homework Martin Boylan

Copy link

@Rody-Kirwan Rody-Kirwan left a comment

Choose a reason for hiding this comment

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

Really good work.
Added a couple of pointers regarding classnames, positioning, and other nitpicks.

Also, be careful about formatting your code and removing any unnecessary comments before opening a PR.

Also - there seems to be a lot of extra files committed. Maybe check with your teammates to see what way they did their PRs.

<body>

<header class="nav-header">

Choose a reason for hiding this comment

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

I really think a container would have helped you here.
By having a container - it allows you to give the header element a max-width of say 650px
This would allow you to remove the percentage widths of the logo and nav children and just use justify-content: space-between
You'll notice if you pull in the window your nav items start to stack before all the space is taken up because they are restricted to stay within 60% of the window.
Alternatively you could make the the body a flex box - but I don't encourage this.

<body>

<header class="nav-header">
<div class="logo">
<img src="/img/karma-logo.svg" alt="karma logo" width=42 height=42>

Choose a reason for hiding this comment

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

Suggested change
<img src="/img/karma-logo.svg" alt="karma logo" width=42 height=42>
<img src="/img/karma-logo.svg" alt="karma logo" width="42" height="42">

all html attributes should be enclosed in double quotes

</header>
<section class="image-container">
<div class="image-section">
<p class="big-writing">Introducing Karma</p>

Choose a reason for hiding this comment

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

Nice use of reusable classes :)
FYI - It's common to shorten size notation with sm, md, lg then combine for finer tunes like sm-md md-lg and also using x for extra - xs xl
Also I think font is probably more programmatically correct term instead of writing

These are all nitpicks by the way - not really important - but good to get used to universal standards

<p class="inc">Karma Mobility, Inc</p>
</footer>


Choose a reason for hiding this comment

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

Always remove any comments that are not your own - or comments that no longer make sense in the context of the work being submitted

<!-- Add your HTML markup here -->
<!-- Remember: Use semantic HTML tags like <header>, <main>, <nav>, <footer>, <section> etc -->
<!-- All the images you need are in the 'img' folder -->

</body>
</html>

</html>

Choose a reason for hiding this comment

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

indentation is a little out of whack throughout the file... It's good to make sure your code is correctly formatted before submission. You can find auto formatters on vscode for any language. Some will do it every time you save so you never have to think about it again :)

Again just a nitpick but becomes really important as you move forward.


}
.image-container p {
display: flex;

Choose a reason for hiding this comment

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

None of these attributes seem to be doing anything.
You generally wouldn't be giving text tags a display of flex.
I think you can remove this block altogether.
Also FYI - It's good practice to remove any commented code before submitting a PR


}

#button {

Choose a reason for hiding this comment

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

I would prefer this to be a class.
It's fine for now - being the only button...
But you can imagine this button featuring elsewhere if you were to start doing the other pages on the navbar.
You could of course give them all an id of button but this is generally bad practice. IDs should be unique.
Use classes for styling where possible

padding-bottom: 8rem;

border-bottom: 1px solid rgb(226, 225, 225);
margin-left: auto;

Choose a reason for hiding this comment

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

Would prefer to use flex to center.
Remove margins and use

justify-content: center;
width: 100%;

and on the child elements give
margin: 0 20px;

#facebook {
font-size: 1rem;
color: #4267B2
}

Choose a reason for hiding this comment

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

Can format this also ;)

Try ctrl+a then right click and see if there is an option to format document

@Rody-Kirwan
Copy link

Also - forgot to mention - the image urls are not working as expected.
Remove the first forward slash

@MartinBoylan
Copy link
Author

MartinBoylan commented Jun 4, 2020 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants