Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alexa Coffman - Whales #105

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

Conversation

AlexaCoffman
Copy link

@AlexaCoffman AlexaCoffman commented May 27, 2022

Personal Portfolio Site

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Did you have to resolve any issues when running the HTML Validator? If so, what were they? Not really! I was missing alt text for images at first. I do still have a warning for not including a header for two of my section elements. Not sure if this is a huge deal.
Why is it important to consider and use semantic HTML? For readability purposes, primarily. Also for screen readers?
How did you decide to structure your CSS? I had a main styles.css file which contains most of it. Then I also have a file for the portfolio and about pages where I made some minor changes.
What was the most challenging piece of this assignment? Alignment!
Describe one area that you gained more clarity on when completing this assignment I kept forgetting that I could use multiple selectors (for example, to select all a elements in nav). If I'd been thinking about this earlier, it would have gone more quickly.
Optional
Did you deploy to GitHub Pages? If so, what is the URL to your website? I did not. Maybe later!

Copy link

@kaidamasaki kaidamasaki left a comment

Choose a reason for hiding this comment

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

Great job!

I left a few style notes but honestly your HTML and CSS are better than a lot of actual website source code.

Well done!

<li><a href="portfolio.html">portfolio</a></li>
</ul>
</nav>
<section> <img class="about-pic" src="/images/me.jpeg" alt="Photo of Alexa Coffman">

Choose a reason for hiding this comment

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

Style:

Suggested change
<section> <img class="about-pic" src="/images/me.jpeg" alt="Photo of Alexa Coffman">
<section>
<img class="about-pic" src="/images/me.jpeg" alt="Photo of Alexa Coffman">

<body>


<body class="container">

Choose a reason for hiding this comment

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

Putting a class on body is a little redundant, since there is only one per page (unless your page is super invalid) and you can just select by the element in your CSS.

<li><a href="portfolio.html">portfolio</a></li>
</ul>
</nav>
<section> <img id="lighthouse" alt="Photo of a lighthouse on a cliff in Iceland" src="/images/iceland.jpeg"> </section>

Choose a reason for hiding this comment

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

Ah. I see why it was upset about this.

A section that just contains a single image doesn't really make much sense. Ideally you would just have the image here and tweak your styles to accommodate that (using things like adjacent sibling selectors or nth-child if you wanted to make it general.

Though honestly the easiest is probably to just add a rule around img tags in your CSS. If you really need a wrapper element here you could also fallback to using a div.

Comment on lines +25 to +32
<section>
<ul class="portfolio-container">
<li><a class="portfolio-item" href="https://github.com/AlexaCoffman/task-list-api">Task List API</a></li>
<li><a class="portfolio-item" href="https://alexacoffman.com">Photography</a></li>
<li><a class="portfolio-item" href="/images/blanket.jpeg">Blanket</a></li>
<li><a class="portfolio-item" href="https://github.com/AlexaCoffman/swap-meet">Swap Meet</a></li>
</ul>
</section>

Choose a reason for hiding this comment

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

Same here. This should just be a ul.

@@ -0,0 +1,7 @@
.about-pic {

Choose a reason for hiding this comment

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

This might make sense as an id since there will usually only be one about pic per page.

(Though I suppose if you added articles with bylines then having multiples on a page could make sense.)

Generally I like to make things where there is only one an id just for clarity that it's an individual element. That and it uses higher precedence so it's easier to override styles that way.

header {
text-align: center;
}
.container {

Choose a reason for hiding this comment

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

Per previous note:

Suggested change
.container {
body {

text-decoration: none;
}
a:hover {
color: #dab785

Choose a reason for hiding this comment

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

Style: Missing ;.

Technically ;s are only separators in CSS so you can leave it off the last one. It's just good for preventing bugs so you don't need to remember to add it if you add another rule to the block.

text-transform: uppercase;
}
footer {
margin-bottom: -400px;

Choose a reason for hiding this comment

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

Huh, this is interesting.

I'm curious what layout issue required doing this. If you're interested during office hours I'd be happy to take a look at any odd CSS issues you've got.

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

Successfully merging this pull request may close these issues.

2 participants