Your page looks good @Mikael3211. Iâm thinking this is the tribute page product. Correct me if Iâm wrong. Some things to revisit;
- Keep the test script when forking the pen (
<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>
)- The test script, with all tests passing, should be included when you submit your projects.
- Your page passes 6/10 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
Be sure and read more than just the first line of the failing message. The ability to read and comprehend error messages is a skill youâll need to acquire as a developer. Ask questions on what you donât understand.
- Codepen provides the boilerplate for you. It only expects the code youâd put within the
body
element in the HTML editor. (No need to include thebody
tags). For anything you want to add to the<head>
element click on the âSettingsâ button, then HTML and add it into the âStuff for <head>â box.- For instance, links to fonts go in the box labeled âStuff for <head>â
- Run your HTML code through the W3C validator.
- There are HTML syntax/coding errors you should be aware of and address.
Since copy/paste from codepen you can ignore the first warning and first two errors.
- There are HTML syntax/coding errors you should be aware of and address.
- Codepen provides validators for HTML, CSS and JS. Click on the chevron in the upper right of each section and then click on the respective âAnalyzeâ link.
- The one for CSS is good. Use it and address the issue(s).
(The one for HTML misses things which is why I recommend W3C)
- The one for CSS is good. Use it and address the issue(s).
- Do not use the
<br>
element to force line breaks or spacing. Thatâs what CSS is for.- Reference MDN Docs
- Keep all your styling external. Do not use in-line styling.
- Accessibility is about being accessible to all users. Review the giving meaningful text to links lesson. For a more thorough explanation read Web Accessibility in Mind.
- âvisit our websiteâ can be worded better for accessibility
- You would want the
input
field for the userâs name to be nested in theform
element.
On a side note, when asking for feedback itâs better to post on the #project-feedback subforum where more people will see it.
Iâve taken the liberty of moving this for you.
1 Like
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.