Technical Documentation Page (4 your FB)

Tell us what’s happening:

Hi Everyone,
This is my rough draft of the “technical documentation” project. I did this by writing out the requirements, staring at the model version for a few days, then writing the html, and finally adding CSS to make it responsive. I left the colorful borders in place to better see the divs move as I adjust the viewport. Would love some feedback on how to manage/contain the <main> section text and margins while going from 850+ pixels to wider screens on modern desktops. Funny thing, my work computer has a completely square monitor so it looks great here but not-so-much at home. I plan to re-purpose this as a template for a future project. Maybe a walk-through of a JS project. Let me know if you have any suggestions

Your code so far
“Bleeding Edge Alpha Version”

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.66 Safari/537.36.

Challenge: Build a Technical Documentation Page

Link to the challenge:

In the future please make the title descriptive and put the link to your project with the text. The title is not clickable.

Some things to revisit @magopolis;

  • 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 test script is JavaScript and would not go in the head element. It will not work correctly. (codepen is forgiving)
  • Run your HTML code through the W3C validator.
    • There are HTML coding errors you should be aware of and address.
    • Since copy/paste from codepen you can ignore the first warning and first two errors.
  • Codepen provides validators for HTML, CSS and JS. Click on the down arrow 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)