Here is my attempt on the 4th project-Technical Documentation page
It’s quite a simple one, but it took time, because I couldn’t get the responsiveness perfect. Also, there was a lot of content that I needed to type in(Typing all this in a day or two still seems impossible to me.)
Kindly provide your constructive feedback, so that I can improve on my skill and make myself skilled enough to be able to contribute to this wonderful community
Thank you so much
Thank you for this info.
I’ll check why the rendering on Chromium edge is like this.
I tested it on my other system. And also tested it on my iPad. Looked alright.
Will deep dive into this issue. Thank you for your feedback, Julio
your use of spacing is very good; I would even add a little bit more spacing above the section headings (e.g. Pre Requisites or Printing Hello World ) to give the user a better visual break
I can reproduce what Julio said on Chromium 84.0.4147.105 and Firefox 80.0b1
@miku86@julio-pinheirooCan you guys tell me the steps to reproduce this error? I am not able to do so, but I see that there is a problem with the page.
Your page looks good @anicsekaran. 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>’
Mentioning because you have elements out of order. The links to the stylesheet and fonts belong in the head element. The link to the fcc test script belongs right before the closing body tag. Everything the browser renders belongs in the body element. So that last div element belongs in the body.
When cleaned up, run your HTML code through the W3C validator.
There are HTML coding errors you should address.
Don’t use <br> to force spacing or line breaks. That’s what CSS is for.
Hello @julio-pinheiroo and @miku86 : Thank you for your feedback
I’ve tried improving the responsiveness of the page, and found out a couple more flaws, which I have corrected.