I recently wrote about How I massively improved my website performance by using the right tool for the job, and the TL;DR is that being mindful and...
For further actions, you may consider blocking this person and/or reporting abuse
This is well written and I enjoyed it, but somehow loses the focus on the core part: That there are requirements, that could be implemented by only using HTML and/or CSS or at least be limited to the necessary technologies. Then suddenly examples are provided showing in an enjoyable way, what you could do with HTML, but if you want to be serious and need to convince a customer with your results, of course you will use what is needed to design a nice website. If it needs a lot of JavaScript, then you would add it. Anyway the more your Website actually is a Web App, the more you will need to do some programming, which cannot be done only with HTML.
But I like how your article reminds people of the importance of understanding the main parts of any website, beginning with HTML, most likely with some CSS and in case of need the code which could be extended by Frameworks etc., when it is acceptable.
Thank you!
Nice piece.
I totally agree with you on this for building websites, but I can't say the same for web apps.
Also I don't think I'd agree with this
Because honestly I don't think an HTML only website is beautiful in most people's eyes, it can appear well structured, but not beautiful.
But again they say "beauty is in the eyes of the beholder ", if you and your clients find it beautiful, then it is what it is.
I'ts an amazing article and good to share. Very helpful for creating a html website. Many important things are considered for developing a good and interactive website. This might be help me for implementing many good functionalities into Wheels & Tires. Thanks for sharing.
markata.dev/ is html only out of the box and I argue its beautiful.
That uses CSS π
It fits @peerreynders description down below. It's one network request for one document.... plus an oversized favicon thats significantly larger than the rest of the page.
Ah I missed that, not sure how π€¦, in that case if you donβt mind excessive profanity / swearing I have a follow up for βmotherf**kingwebsiteβ I built you might enjoy:
ultimatemotherf**kingwebsite.com
Love that series of sites, your implementation is superb, possibly my favorite one. I'll have to look closer at some point to see if I have made any of these mistakes. satire aside I have taken a lot of inspiration from these to build my personal site (not the home page with it's bloated video at a whopping 4.7kb raw, but the rest of the site.), as well as markata.dev.
Love both sites, sometimes simplicity is better as the information should be the star!
Now this is something you don't see every day :) Brilliant!
HTML only websites? Childβs play!
How about html only βvideo encodingβ? ππ€£
Animations without JS...or CSS...or IMAGES??!? π² Pure HTML animation!
InHuOfficial γ» Apr 16 '21 γ» 2 min read
Clever :D
Adding css vs inlining css feels a bit of a moot point, same effect, but potentially less network traffic if you reuse the same sheet on multiple pages. right?
The target is to produce a page that isn't larger (give or take) than 14Kb (10 TCP packets worth, typically the maximum a server will send on the first round-trip on a new connection). And the inline CSS is typically for the above-the-fold content. Hypothetically that should improve First Contentful Paint (FCP) for the page.
Iβm new to my coding journey and I was told I should not learn HMTL because it is useless. Can you give me more insight?
HTML is fundamental to understanding how a browser page works! What else would you start with? Check out freecodecamp.org and the FIRST module is HTML.
Thank you!