We had a class in the first semester of uni where we had to create a static html page based on a screenshot.
There was this one textbox at the top of the site, where the only way you could recreate the screenshot was by using a <br/> in the middle of the text.
The prof was very picky about your HTML being semantically thorough and correct, so that was super weird that that was necessary.
You can style your whole webpage with divs, but using main, nav, footer or whatever blocks is semantically more correct, because you group elements together that have a certain purpose.
A HTML Tag in the middle of a sentence is not wrong per se, but when parsing it a line break could signify two sentences where one has missing punctuation, instead of a complete sentence as your original intention was.
I don’t really care how the design you want is achieved to be honest, but I don’t get why the prof didn’t argue against.
Oh boy.
We had a class in the first semester of uni where we had to create a static html page based on a screenshot.
There was this one textbox at the top of the site, where the only way you could recreate the screenshot was by using a
<br/>in the middle of the text.The prof was very picky about your HTML being semantically thorough and correct, so that was super weird that that was necessary.
A break is absolutely correct html though.
My point is sematics.
You can style your whole webpage with divs, but using main, nav, footer or whatever blocks is semantically more correct, because you group elements together that have a certain purpose.
A HTML Tag in the middle of a sentence is not wrong per se, but when parsing it a line break could signify two sentences where one has missing punctuation, instead of a complete sentence as your original intention was.
I don’t really care how the design you want is achieved to be honest, but I don’t get why the prof didn’t argue against.
<img>tag harr harr