Sorry to say it, but complete and epic /FAIL/ at using HTML, CSS, and JavaScript for that matter.

  1. You’re using painfully cryptic single letter classes, way to tell other developers to go plow themselves when it comes to code clarity.
  2. You’re using presentational classes. HTML is for saying what things ARE, and not what you want them to look like. That extends not to just your semantic tags (aka all tags inside BODY except DIV, SPAN, and A), but things like classes as well since for different media targets you likely WON’T have the same appearance. The web is about MORE than “screen only”. This is what makes most frameworks a monument to ignorance, incompetence, and ineptitude; if you’re gonna vanilla don’t replicate what’s WRONG with frameworks!
  3. Where’s your DOCTYPE? Enjoy your legacy JS and quirks rendering, even in modern FF. (Don’t forget FF has it’s own flavor of quirks mode!)
  4. You have your TITLE tag before your charset META. You know that makes the browser start over parsing from the beginning, right? The charset META belongs BEFORE any and all content-bearing elements. This includes the title tag and any META with content=””.
  5. Not one legitimate UA gives a flying purple fish about the author META.
  6. Blocking script in the head for UA’s that don’t know module, static scripting in the markup missing a caching opportunity. Any quality scripting would a) be in an external file to not waste bandwidth on people who block scripting, and b) right before </body> so that you don’t need that DOMContentReady crap and have a faster load without “module”
  7. Static style in the HEAD again missing caching opportunity. 99% of the time you see <STYLE> and 90% of the time you see style=”” you’re looking at garbage code made by people who shouldn’t be writing HTML. Also, the style opening is invalid, you have <style style=”text/css”> where you probably meant <style type=”text/css”>… except:
  8. This is 2020, we don’t say type=”text/css” anymore on STYLE tags any more than you do type=”text/javascript” on SCRIPT tags. HTML 5 got rid of that trash.
  9. Pixel paddings or px for other values will likely be broken for users like myself once a real layout is built, since you didn’t set the font size to same. Pixels on the whole is a broken metric hence your media queries are likely also broken banjaxed garbage for non-standard font metric users. It’s called EM, use ‘em!
  10. Why are you declaring Arial then declaring another stack later?
  11. Since there should only ever be one MAIN tag, why are you wasting an ID on it?
  12. Does SECTION inside ARTICLE even make sense?

And not as big an issue since I assume that’s placeholder content, but it’s called keywords. Not keyphrases, not keysentences, but keyWORDS! It’s supposed to be 7 or 8 single words or proper names that exist as plaintext inside BODY, totaling under 96 characters. You go outside those parameters and you end up with why people THINK it’s ignored. Even crazy Goog seems to have forgotten how it works, and even still works in their own flipping search engine.

Sorry, but you might want to go back and learn HTML… and semantic markup… and separation of presentation from content, and good JavaScript practices…

Why is it that so many JavaScript fans don’t know enough about HTML or CSS to be using JavaScript in the first place? Certainly explains a lot of the garbage that’s been added to JS lately… like that stupid “fetch” promise that provides zero error handling and sends scripting off to never-never-land on failure.

Of course looking around your git directory, that “router” thing is exactly the type of bloated trash I’m so used to seeing from a “JavaScript Teacher”. Basically a SPA with zero scripting off graceful degradation, an INSTANT WCAG violation that if used on certain types of sites could get you a summons, fines, civil lawsuits under laws like the US ADA, UK EQA, etc. The type of stupid bloated “JS for nothing” that wouldn’t be needed if people would just bother leveraging cache and stop believing lies like “wah wah, teh pageloads r teh evils”.

A better starting HTML would/should be more like this:

<header id="top">
<h1>Site Title</h1>
<!-- menu code here -->
</header>
<main></main><footer>Disclaimer Here</footer><script src="scripts/library.js"></script></body></html>

Remembering that style does NOT belong in the markup and should be targeted for specific media, scripting in the markup should be avoided and included right before you close BODY, quality JS should enhance an already working page whenever possible and NOT be the only means of providing basic functionality on the majority of sites, etc, etc, etc.

Otherwise, well, you’ve got:

JS for nothing and your scripts for free. That ain’t workin’, that’s not who you do it. Lemme tell ya, these guys ARE dumb.

Bottom line, for 2020 it really looks like you’ve got the WORST of 1997 practices pretending to be “modern”.

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store