https://codepen.io/matthew-pourroy/full/YzpyOLZ
I love for any feedback!
Hey, just a few things to consider:
h2
). And then add a title heading (h1
) at the top. I would think it would be 'Computer Components` since that seems to be the title in the TOC. But don’t make the text in the TOC nav the h1
. Your h1
should probably be at beginning of the <main>
. You might add some brief content between the h1
and h2
describing the purpose of this documentation?em
s for the break point then it will also be responsive to changes in text size as well.<code>
element a lot but I’m not seeing any computer code on the page. The <code>
element is typically used just for displaying actual computer code (such as examples form a programming language). I think you can just get rid of all of them completely, but if you need a wrapping element then just use a plain old generic <div>
.Your page looks good @pourroy.matt. Some things to revisit;
code
just to satisfy the user stories. What you can do to meet that requirement is to maybe have things like ‘motherboard’, ‘CPU’, ‘GPU’, ‘PSU’ in the code elements.
Ahh, I didn’t realize that using <code>
is a requirement for this project. Sorry about that. Definitely what @Roma said, figure out a way to incorporate some legit uses. Maybe for the CPU section you could give some examples of assembly language code?
Hey I made some changes, but some of the changes caused the project to not pass all the requirements so those I left out. Here it is now https://codepen.io/matthew-pourroy/pen/YzpyOLZ
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.