Singuelema-trubute-project

Code Feedback
1

Here is the link for my tribute project willing to get feedback
https://github.com/singuelema/singuelema-tribute-page-project.git[My tribute [ tribute link]https://codepen.io/singuelema/pen/XWXdPva

2

Your page looks okay @Singuelema. Some things to revisit;
First thing, verify your email addr with codepen so people can see your page full view.

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>).
    • The test script should be included, with all tests passing, when you submit your projects.
    • Your page passes 4/10 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
  • Codepen provides the boilerplate for you. It only expects the code you’d put within the body element in HTML. (No need to include the body 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.
    • The link to your font goes in the box labeled ‘Stuff for <head>’
  • Run your HTML code through the W3C validator.
    • Since copy/paste from codepen you can ignore the first warning and first two errors.
    • There are HTML coding errors you should address.
  • All of your styling should be external. Don’t use in-line styles.
  • Don’t use <br> to force line breaks or spacing. Use CSS
  • Review the lesson about giving meaningful text to links.
3

i can’t see the red button you mentioned to click in either to see the test i failed

4

Hello!

Here is how you can view the tests you are failing and the error messages associated with them:

test
test850×368 1.09 MB

5

Finally i get it after the test i pass 10/10

check it again !

thank you for your help

6

Good job passing all the user stories @Singuelema. There are still some other things you can do to clean up your page. Mentioned in my previous post,

  • use the W3C validator
  • don’t use in-line styling, do all styling externally
  • don’t use <br>, use CSS
  • read up on accessibility…“learn more” is not accessible