Skip to content

Queues - Elizabeth Deutsch - Static-Site#18

Open
edeutschie wants to merge 5 commits intoAda-C7:masterfrom
edeutschie:master
Open

Queues - Elizabeth Deutsch - Static-Site#18
edeutschie wants to merge 5 commits intoAda-C7:masterfrom
edeutschie:master

Conversation

@edeutschie
Copy link
Copy Markdown

Static 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? It did catch some errors I was able to fix. Only thing we hadn't discussed was puting in the html file when using Lorem ipsum. Not sure if that is necessary.
Why is it important to consider and use semantic HTML? It is easier to style, see mistakes to make corrections, and easier to go back and make changes later if semantic HTML is used. Also, the better the semantic HTML, the better the browser can understand how the programmer intends the website to be seen and translate it for the viewer/user.
How did you decide to structure your CSS? I started with a main.css file and organized it with header, main, and footer sections. This was for the index page and for the elements the index page shared with all the other pages (the main header and nav bar for example). Then I had .css files for each additional page of the website with styling that was specific to them.
What was the most challenging piece of this assignment? Positioning. I gravitated towards using floats, but that created a lot of problems for me if the browser was not set to full screen. I had to go back and rework many of my pages to display: inline-block instead.
Describe one area that you gained more clarity on when completing this assignment Positioning. Same as above. I was much more used to using floats. In this assignment I learned how to use inline-block positioning better. Also, got more practice using percentages rather than pixels.

@PilgrimMemoirs
Copy link
Copy Markdown

Static Site

What We're Looking For

Feature Feedback
Baseline
Appropriate Git Usage ❗️ Need to commit more often.
Answered comprehension questions Well Done
Page fully loads Well Done
No broken links (regular or images) Well Done
Includes at least 4 pages and styling Well Done
HTML
Uses the high-level tags for organization: header, footer, main Well Done
Appropriately using semantic tags: section, article, etc. Well Done
All images include alternate text Well Done
CSS
Using class and ID names in style declarations Well Done
Style declarations are DRY Well Done - there was one ruleset that could have been mostly included with another one (#hero #two, #hero #three could have been combined with #hero #one - then #hero #two, #hero #three could have it's own ruleset for the one different style).
Overall
Portfolio It looks really nice, though doesn't provide any info on the projects - some suggestions would be to have the title of the project show when hovering over the image. Or having the title on top of the image, with a short description below.
Organization HTML and CSS is very well organized and easy to read! Great work!

@morrime
Copy link
Copy Markdown

morrime commented Apr 4, 2017

Great work! Your use of semantic HTML is excellent, as is your organization of the HTML and CSS files. The site is visually pleasing and engaging. Make sure to keep working on committing early and often. Here's an article I've found helpful for writing strong commit messages. Also, nice job using percentages instead of pixels. You can avoid a lot of weird looking formatting for your users if you continue that practice.

Comment thread index.html
<section id="hero">
<h1>Elizabeth Deutsch</h1>
<p>Elizabeth is a junior developer and Seattle native.</p>
<!-- <p>A current student at Ada Developer's Academy</p> -->
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

In future PRs or Code Reviews, feel free to delete any commented out/unused code.

Comment thread portfolio.html
<ul>
<li class="contents"><a href="https://github.com/Ada-C7/Word-Guess/pull/11"><img src="assets/Ducks_Dark.png" alt="ASCII art of ducks"/></a></li>
<li class="contents"><a href="https://github.com/edeutschie/meowspace"><img class="img-circle" src="assets/cat.jpg" alt="cat photo"/></a></li>
<li class="contents"><a href="https://github.com/edeutschie/ride-share-two"><img src="assets/wheel.png" alt="photo of steering wheel"/> </a> </li>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Excellent semantic HTML throughout the project!

Comment thread about.html
</ul>
</nav>
</header>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Nice use of whitespace and proper indentation to help maintain readability.

height: 75px;
}

#portfolio img {
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 styling you chose for the images is really nice!

Comment thread styles/main.css
footer {
margin-top: 8%;
margin-bottom: 1%;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You may want to consider centering the footers on each page.

Comment thread portfolio.html
<h1>Portfolio</h1>
<p>A sampling of recent projects at Ada Developer's Academy</p>
<ul>
<li class="contents"><a href="https://github.com/Ada-C7/Word-Guess/pull/11"><img src="assets/Ducks_Dark.png" alt="ASCII art of ducks"/></a></li>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I agree with Jamie's comment about the titles. It would be cool to see a brief description of the link before clicking. Also, :hover is nice because it makes it obvious to people that the image is a link as well. You could change the border color, the image size, or have the title appear when hovering over an image.

Comment thread styles/main.css
@@ -0,0 +1,116 @@
@import url('https://fonts.googleapis.com/css?family=Slabo+27px');
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

nice font!

Comment thread styles/main.css
@@ -0,0 +1,116 @@
@import url('https://fonts.googleapis.com/css?family=Slabo+27px');

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your organization of CSS files is great!

Comment thread styles/main.css
margin-left: 3%;
}

.emoji:hover::before {
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I like the hover emoji you have here. It's makes it really clear that these are links, and it's cute.

Comment thread styles/main.css
.contents a {
text-decoration: none;
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You may want to consider putting more space between the links, so when you hover over one, it doesn't displace the others with the emoji.

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.

3 participants