Technical Documentation page - i ask for some feedback!

Hi FreeCodeCampers,

I let you here my last page, the fourth one:

https://codepen.io/silvamaxi93/pen/NWxpbjO

I will apreciate your thougths and feedbacks!!!
thanks!!!

Hello! Try to edit your post and link the full page view, because at least for me the link you used doesnt work.

hi @maxi1225

we cant see your work, as you shared the debug view, unless you are codepen pro member, it can’t be viewed by others.
it only works on your side.

NEW LINK : https://codepen.io/silvamaxi93/pen/NWxpbjO

Best to edit your first post with the proper link

The page looks great, but you might want to try using other fonts to make it look even better :slight_smile: I recommend using google fonts.
EDIT: I noticed you use a font for your navbar elements only when you hover on them, I recommend using the font for them even when you are not hovering over them, and maybe add <strong> to the text when hovering to get the effect you want

Yes i used google fonts, i did that with the hover because i was playing…

I’m gonna do some changes to look even better.

thanks!

1 Like

Your page looks good @maxi1225. Some things to revisit;

  • 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 the font goes in the box labeled ‘Stuff for <head>’
    • The test script, being JS, does not belong in the head element. It wouldn’t work. It should be just before the closing body tag. (If you follow codepen’s way of only coding what goes between the body tags it doesn’t matter whether you put the script at the top or bottom of the HTML section.)
  • Run your HTML code through the W3C validator.
    • There are HTML coding errors you should address.
    • You can ignore the warnings if you want. They’re there to help you with semantics.
1 Like