17 ms·
The appeal of using plain HTML pages (2019)
- krsdcbl 5y agoFeel like this post confounds "plain html" for "minimal styling"
- steren 5y agoI wrote about static HTML sites in "My stacks will outlive yours": https://blog.steren.fr/2020/my-stack-will-outlive-yours/ https://blog.steren.fr/2020/my-stack-will-outlive-yours/
- PaulHoule 5y agoI always thought there was more potential in HTML than gets realized https://ontology2.com/the-book/html5-the-official-document-language.html https://ontology2.com/the-book/html5-the-official-document-l... but practically it never happens. So we get stuck with languages like markdown, restructured text and various sorts of wiki markup. Just about everybody who gets serious about extracting data from Wikipedia learns the hard way that parsing wikimedia markup is possible to get 90% right with a lot of suffering but if you have a DOM-intelligent HTML parser often you can get 99.95% right with 2 minutes of work parsing the HTML. (The reason why is that people look at HTML and fix the markup until the HTML looks right, they don't look to see that the markup is conformant to any spec.) For a long time I've wanted to like Dreamweaver and it didn't seem so bad in 2003 but today I type a few characters into the live view and then I can go on vacation and the characters might have appeared a week later. You'd think every HTML editor that is embedded in HTML was developed by a sadist except that it seems there is a basic conceptual problem that makes WYSIWYG HTML editing completely impractical.
- togaen 5y agoI love reading all the hate the author is getting here. It means he’s right.
- jefftk 5y agoHTML as an authoring language is underrated, but several commenters are confusing "writing HTML" with the aesthetic of nearly unstyled HTML. I think this is happening because the post we're discussing is not itself an example of what the author is describing: it's authored in DWikiText. An example (that I maintain) of what the author describes: https://www.bidadance.org https://www.bidadance.org. Each of the pages is just plain HTML on disk.
- thunderbong 5y agoWhy aren't any of the paragraph tags closed?
- enriquto 5y agoBecause it's unnecessary in html5, just like closing li, td, tr tags. When you use implicit tags (body, header, etc) and auto-closing tags (li, p, tr, td,...) then html becomes refreshingly lean and human-editable. EDIT: for a nice summary, look at google's html style guide. Section 3.1.7 is particularly neat [0]. [0] https://google.github.io/styleguide/htmlcssguide.html#Optional_Tags https://google.github.io/styleguide/htmlcssguide.html#Option...
- jefftk 5y agoMore details: https://html.spec.whatwg.org/multipage/syntax.html#optional-tags https://html.spec.whatwg.org/multipage/syntax.html#optional-...
- niconii 5y agoJust to clarify, HTML5 didn't introduce this, it's been the case since at least 1993. https://www.w3.org/MarkUp/HTMLPlus/htmlplus_1.html https://www.w3.org/MarkUp/HTMLPlus/htmlplus_1.html
- jefftk 5y agoBefore HTML5 it was common to hear things like "technically you don't need it, but it's not to spec so don't do it".
- uncomputation 5y agoYes, this one million times over. I have went from home-rolled React to Jekyll to Gatsby to Hugo and now seriously considering just doing my own HTML/CSS. Practically, I have rarely run into the issues other markup languages and SSGs are supposed to fix and more often, I find their constraints actually limiting/complicating my fairly simple desires. If I want to add movie/album reviews, rather than just making /reviews directory with some files and some basic CSS, I get stuck thinking about Hugo "archetypes" and templates and _index.md and layouts and all of this baggage. I wanted to add support for my site to use my custom "CSS as S-expressions" parser [0], but got turned off by the idea of integrating Hugo "pipelines" or "assets" or all of that. Not to mention that this grows ever more overwhelming if I take a months-long break and have to Google how to start my own blog server! Then I look at RMS' site and, ugly as it is, it has held up and looks way easier to update and less constrained by any premeditated structure/hierarchy. [0]: https://uncomputation.net/cascading-style-s-expressions/ https://uncomputation.net/cascading-style-s-expressions/
- hk__2 5y agoHave you tried Jekyll? I don’t know Hugo; I like Jekyll because it’s very simple with very little abstraction. My blog is just some hand-written HTML with liquid templating. I like how you can add any metadata you want to a post/page and then use it in your templates.
- seanosaur 5y agoJekyll was literally mentioned in the second sentence. You may have missed the point of the comment.
- klodolph 5y agoI have various static sites that I maintain, I recently added a new site created in Jekyll and wrote a bunch of content for it. While I like Jekyll and I'll continue using it, I can definitely relate to the frustration when first using it. I get this feeling that I already know what I want Jekyll's HTML to look like, and now I need to work backwards and develop an understanding of Jekyll in order to figure out how to get Jekyll to produce the desired output. By "HTML" I don't actually mean that I have a problem with embedding specific markup in the page, it's stuff like putting the files in the right place, getting the template to contain the right material, etc. And to be clear, I'm going to continue using Jekyll since it seems more practical than e.g. Hugo given my constraints / available resources / etc, and I may even migrate some other sites I maintain to Jekyll, but Jekyll, like other static site generators, seems to throw a lot of mess in the way of simple desires, as the parent comment articulates.
- 0des 5y agoImagine my smug face as the pendulum finally swings back to me, with my hand typed, hand crafted, fair trade, organic and bespoke HTML. For my next trick, I will achieve the unthinkable and show you how I launch my blog without a dual redundant k8s cluster.
- cxr 5y ago
- bob1029 5y agoIn my estimation, the point the parent comment is trying to make is regarding the unfortunate extent to which the developer community currently relies upon technological sprawl and other unnecessary complexity.
- mdp2021 5y agoIt's not perfectly clear, but estimates do not go far away from "What a satisfaction it will be, when I will return in control with my properly crafted markup. Next, I'll prove a simple server suffices to serve it". About 'snarky', I never understood what it is meant to mean exactly (in spite of many reviews of the guidelines) but I took it to be a variant of bluntness for short-tempered expressions of contempt. I would not interpret it to cover criticism in general, especially of practices.
- TAKEMYMONEY 5y ago> my blog ...is the usual use case for the "why not just use HTML?!" argument. Still, even at the enterprise level, considering SSR's popularity, the "pendulum" has been in favor of static HTML for a while.
- Closi 5y agoYou mean static HTML loaded onto serverless cloud storage with cloudfront, using Hugo to compile markup into HTML with a CI/CD pipeline created to push the content up to your S3 bucket, then with a headless CMS visual editor which sits on some SaaS platform, with any server-side interactions written in Lambdas?
- PaulHoule 5y agoSomething I've experimented with is web templating systems that are HTML 5 native, that is, you parse documents to the DOM, process them in the DOM, then serialize them to the disk (like Hugo) or the web browser. For instance the "template" of your web site might be an HTML document that has something like <div id="content"/> in the middle of it. The content is in another HTML document, there is some logic that merges the document <head>(s), and the contents of the <body> of the content goes into the above <div>. It's not that hard but I think it's never caught on for a few reasons. One of them is that DOM parsing and unparsing is an order of magnitude or two slower than text-based templating sytems. I guess you could parse the template once and cache it but it's still going to be slow. Another is that you run into "hygenic macro" problems if you want to merge random DOM trees into each other: for instance you could have multiple elements with the same id, the same classes used for different meanings in some other places. You need some answer to this if you want to make something scalable (e.g. the whole point of this exercise is that you should be able to transclude HTML + CSS from anywhere and have it "just work") Finally it would be really nice to have a reliable WYSIWYG HTML editor, particularly one that would help you use CSS classes in a disciplined way to customize the system to add whatever markup features you want for your site. It doesn't exist and I wonder why. Every HTML editor I've seen is just garbage. Latency for typing characters is several round trips to the moon. Navigation, selection, where characters appear when I type all seem to be random, like my computer is possessed by the devil. (It's a general problem w/ most WYSIWYG editors that look like MS Word, including MS Word. I'm sure there is something conceptually wrong with the model which is why all those editors are buggy, but it seems everybody else thinks it is OK for selection, navigation and where you type characters to be random.)
- lazide 5y agoThe problem is browsers don’t render like a word processor, so it’s hard to fit the model to reality.
- klodolph 5y agoI use something like this for my personal website. I don't know how fast text-based template systems are, but I can do a clean build of my entire website in under half a second. That seems pretty fast to me. I've been adding content to it for over 20 years now... it's not a massive site since it's just me, but it's not exactly small either. Every page is authored as HTML, with some extra headers at the top. It's parsed as HTML5. The processor will apply templates in a fairly simple way... merge everything in <head>, merge everything in <body>. There's a special tag for templates that means "put the <body> here, instead of merging". Any given piece of HTML will be parsed / unparsed only twice, because the templates work on DOM manipulation. The second parse / unparse is there because I use an HTML minifier, and the HTML minifier has a bytes in/bytes out interface. > Another is that you run into "hygenic macro" problems if you want to merge random DOM trees into each other:... This is a beast of a problem. If I need an ID in a template that may get used in multiple places, then there's some piece of code somewhere generating the ID. My experience is that it really becomes a problem when you have large, large sites with tons of people working on them, and it's not a problem at all for one person. > Finally it would be really nice to have a reliable WYSIWYG HTML editor, particularly one that would help you use CSS classes in a disciplined way to customize the system to add whatever markup features you want for your site. It's called "Dreamweaver". Truly one of the most powerful web authoring tools ever made.
- jklinger410 5y ago<link href="/~cks/dwiki/dwiki.css" rel="stylesheet" type="text/css">
- klodolph 5y agoI love plain HTML. The chief problem I have with it is just dealing with templates--stuff like navigation. Lots of other people have the same problem. So they add some simple templating system, where they stick some text around the HTML. Ok, and then they want to automatically generate navigation, maybe add a few other features here and there. Add width/height to <img>, syntax highlighting for code snippets, etc. It's really easy for this kind of endeavor to get out of hand. The hardest part of plain HTML is sticking with it and writing just enough automation to keep you sane. It's also far too easy to get sloppy when working on something that does some basic preprocessing. My personal preference is to keep the pages as HTML, and write a processor that does minor modifications to the HTML DOM, using a proper HTML5 library. If done carefully, you can keep the experience close to the experience of editing pure HTML. For example, rather than some custom "shortcodes", you can use custom HTML elements. Custom HTML elements are a more verbose, but come with major advantages over terser shortcodes (use existing tooling, you don't need a parser). You can do simple stuff like automatically add alt="" or srcset="" to your <img> based on image metadata, or automatically generate breadcrumbs using site structure. The general idea is to keep it as close to plain HTML as possible. If possible, make it so the page is plain HTML.
- jll29 5y agoI'm sympathetic to your view in favor of siplicity. > I'm normally someone who's attracted to ideas like writing in a markup language instead of raw HTML and having some kind of templated, dynamic system (whether it's a wiki, a CMS, or a themed static site generator), as you can tell from Wandering Thoughts and DWiki itself. Note that HTML is a markup language (an SGML application) and so is XHTML (an XML application). If you meant by "a markup language" a user-friendly or domain-specific markup language, then there is good news: if you use XML as your markup (ideally by defining your own wiki's DTD, as simple or as sophisticated as you like) then you can associate an XLST transform "program" with it, and then a click on "view HTML" in the browser will display the underlying XML [sic], not as you would expect the generated XHTML, as the XHTML is generated from the XML on the fly only (not stored persistently anywhere, thus avoiding file clutter). For example, you may like a structure like: <docs> ... <doc> <title>...</title> <text>...</text> <keywords>...</keywords> </doc> ... </docs> The XSLT can insert the standard XHTML boilerplate as well as your logo and a header after the <doc> and before the <title> element, for instance, and any potential footer between </text> and </docs>. That gives you much in terms of separation between structure and content, yet no separate conversion pass is required to render the pages in a standard browser, and no special viewer plug-ins are required either.
- eurasiantiger 5y agoSimple can be powerful. For example, the humble Apache directory listing can be JS-enhanced to a blog, a photo gallery, an album-per-folder music player and so on, and without JS it gracefully degrades to a list of posts, images or whatever media, or to a folder structure — just hide in .htaccess whatever files you don’t want visible.
- ilaksh 5y agohttps://gemini.circumlunar.space/ https://gemini.circumlunar.space/ https://github.com/runvnc/tersenet https://github.com/runvnc/tersenet (note that Gemini is a real system, mine is just an idea)
- zzo38computer 5y agoTerseNet seems like it has some good ideas, and I had some similar ideas, too. I would do some things differently though, such as not loading even one small image automatically (everything must be loaded explicitly), not having such a small limit for text files (I think that many documents will be much longer), not using Unicode, and some other things differently too, but much of that is like what I would have wanted to make, and I could write some of my own ideas about it too, in future, maybe.
- 1vuio0pswjnm7 5y ago(2019)
- notorandit 5y agoAnd plain old Html works with almost any device, even old nokias, motorolas, nintendos.
- swayvil 5y agoDoes PHP count as plain HTML? How about PHP + CSS?
- mftb 5y agoI like plain html pages for presentation too, but this writer is making a fundamental mistake. He keeps making it, as he vacillates between solutions. He keeps mixing his data into his presentation of that data. Keep your data however you like, plain text files in a simple directory structure, database, whatever. The important thing is, as much as possible, organize the data in a presentation neutral way. Choose whatever programs you want to present that data, in whatever context. When you eventually tire of some of those solutions, if you've done things right, you will simply discard them and pick new ones to present your data in new ways. As long as he continues to mix his data with it's presentation at the outset, he doesn't have data, he has a website, or a wiki, or whatever, and he'll keep having to solve the same problem.
- munk-a 5y agoI adore plain HTML but their lack of any versioning seems silly to me. It's so easy to use (for instance) git to sync changes back and forth that eschewing it from the process just seems unnecessarily dangerous. Throw it all in source control (and maybe if you're using git create a public github repo) and you've got a free backup along with a safer way to edit the files. Considering it's all plain HTML local edits can be trivially vetted by just opening .html files in browsers or, for the more advanced, taking five seconds to download an appropriate WAMP/MAMP/LAMP binary that sets up apache and some crap you don't need - then just move your source dir into whatever their public_html is called. It is so so trivial to vet local HTML changes and use a repository where you just directly push to master that I'd suggest it to anyone building a plain HTML site just for the fact that you're getting free backups as a side effect.
- cellularmitosis 5y agoAlternatively, they could just throw an rsync one-liner into a crontab and slurp down a backup copy of the files once per day, in case they make a mistake. This optimizes for the common case (the days where you don't make a mistake) and removes the requirement that everyone on the team needs to know git.
- munk-a 5y agoIn the article they mention they're generally using vi for editing. The learning barrier for git is so much lower than vi. Git, when used without branches and merges, is really dead simple.
- jameshart 5y agoJust one caveat: you might need to make sure the .git directory isn’t publicly accessible via the web server.
- munk-a 5y agoI guess though to be honest there isn't any privileged information stored in there to my knowledge? It's just historical information which you're probably going to end up publicly exposing on github anyways.
- olliej 5y agoMy website has remained unsullied plain html since I wrote it. This would be more impressive if I ever actually updated it :D (behold http://nerget.com http://nerget.com and weep when you see the "new" features it refers to :D )
- api 5y agoThis would be far more versatile as an approach if HTML could include other HTML. Not SSI but built into the spec and requiring nothing from the server and no JavaScript. Couple this with good CSS and HTML could actually be composable. Composability was known to be a good thing in GUIs in the 1970s and the web still struggles with achieving it without heaps of JavaScript. Of course I’m sure there is some weird reason this was never done, so instead you need mountains of shit to work around it.
- superkuh 5y agoThis is pretty much server side includes, SSI, and it's amazing and still in your server binary's today. It's a tiny, negligible, attack surface with just enough power to include bits of html so you can do templating and single file edits of the entire site. It's old tech but it's really at the sweet spot for power versus complexity. I still use it and recommend others do as well. It makes a static site much easier to maintain.
- fedeb95 5y agoI'm with you with going stackless way for projects that don't need to be complicated, but you don't need javascript to add headers. Just a few commands would do
- ggm 5y ago"plain" here being "with judicous but none the less not exactly vanilla" CSS and JS
- sircastor 5y agoI remember hand coding my website in 1996 and then again in the early 2000s. I remember learning how to use whatever perl scripting or apache extension that enabled the .shtml extension to be rendered into a single page. I remember a friend introducing me to Frontier! and trying to figure that out. Honestly, it was a lot more fun when it was my hobby and just me messing around in my spare time. I know WordPress is not particularly popular on HN, and I understand the reasons. That said, I use it for my personal blog because it reliably gets out of my way.
- Minor49er 5y agoA friend of mine runs a netlabel. Its website is a single static HTML page with no Javascript. Links to sectons are all anchor refs. It feels like Web 1.0 construction with a basic Web 2.0 face https://moonmusiq.com/ https://moonmusiq.com/
- steve76 5y ago
- likortera 5y agoYeah, plain HTML and CSS is great and all, until you need a shared layout, dynamic ObjectGraph headers, a RSS feed, translations, or anything else more complex than a one-page landing page. Right tool for the job. I still remember the days of "plain HTML pages", most people didn't even get to close tags properly and shipped malformed HTML to browsers.
- WalterBright 5y agoMy entire web site is plain html, although I wrote the program that generates it.
- bananzauser 5y agoAfter getting frustrated with SSG, I evaluated a few options. SSGs usually begin as niche products and then add more features and become bloated with them. Ultimately, they have so many bells and whistles I don't need that it's not worth dealing with them. I wanted something simple e.g. based on pandoc. I have also tried writing posts in pure HTML. HTML has lots of advantages, but when you have to read your own stuff, it's not very pretty. Markdown brings more clarity to your documents and also allows you to embed HTML. I have used Sergey [1] to create some basic HTML templates, but it is not as pleasant to use as Markdown. Also, generating RSS and creating archives are problematic. This should be automated. I decided to use Blot [2]. I am not familiar with the author, but I think it is a good tiny product worth recommending. It will turn any document into a page. You can create an HTML page and it will be embedded into your template. The author appears to be nice [3]. The code is open source. [1]: https://sergey.cool/ https://sergey.cool/ [2]: https://blot.im/ https://blot.im/ [3]: https://blot.im/about/notes/politics https://blot.im/about/notes/politics
- cryptos 5y agoI've been a fan of Hugo (even if I don't like the strange Go template engine), because it offers a lot like tagging, generation of overviews etc. But Hugo breaks backwards compatibility on a regular basis and I'm bored of "fixing" my project just to be able to get a bugfix! I will not go back to plain HTML, though. That is the other extreme, which is even harder to maintain, because changing the general structure, navigation or layout would require a lot of manual work. Maybe I'll write a site generator on my own ...
- devnulll 5y agoGitHub pages seem to be about the simplest way to do this today - bringing the goodness of basic source control, simple issue management, and related.
- cellularmitosis 5y agoAnother lightweight github-based approach is to just link together a bunch of gists: https://gist.github.com/cellularmitosis/fdac60efe210d1cee26391b4a3beb891 https://gist.github.com/cellularmitosis/fdac60efe210d1cee263...
- canadianwriter 5y agoYup! I use Github pages as my "CMS" for my pure HTML static site (https://kolemcrae.com https://kolemcrae.com) works beautifully!
- ExtraE 5y agoI have a fair number of sites on Github pages but I've ended up migrating most of them to Netlify (which is a very easy process) when I've needed more features, like wildcard ssl or multiple domains. Still haven't paid a cent!
- vmception 5y agofor my sites that expect an occasional burst of traffic, I moved all the media assets to IPFS and served by one of the gateway that functions as CDN for IPFS stuff. this circumvents Netlify's bandwidth metering and all the users retrieving the IPFS assets keeps the IPFS assets loading quickly
- dvasdekis 5y agoHow did you do this? Is there a tutorial that you followed? I would love to do the same, potentially with Cloudflare further caching the IPFS-hosted files.
- 5y ago
- ape4 5y agoKISS
- SemanticStrengh 5y agoThat's lovely
- robertoandred 5y agoUsing JS to insert headers and footers already makes them non-plain HTML pages. This is just trading one set of issues for another.
- petepete 5y ago100% this, there's no good reason to do this in JS. Apache has supported Server Side Includes forever. All you need to do is drop an 'include' in your HTML file and Apache will inject the contents in the right place. <!--#include virtual="/header.html" --> I don't know for certain but suspect other webservers will have similar functionality. https://httpd.apache.org/docs/current/howto/ssi.html https://httpd.apache.org/docs/current/howto/ssi.html Edit: IIS: https://docs.microsoft.com/en-us/iis/configuration/system.webserver/serversideinclude https://docs.microsoft.com/en-us/iis/configuration/system.we... Lighttpd: https://redmine.lighttpd.net/projects/1/wiki/docs_modssi https://redmine.lighttpd.net/projects/1/wiki/docs_modssi Nginx: https://nginx.org/en/docs/http/ngx_http_ssi_module.html https://nginx.org/en/docs/http/ngx_http_ssi_module.html Tomcat: https://tomcat.apache.org/tomcat-7.0-doc/ssi-howto.html https://tomcat.apache.org/tomcat-7.0-doc/ssi-howto.html Jigsaw: https://www.w3.org/Jigsaw/Doc/User/SSI.html https://www.w3.org/Jigsaw/Doc/User/SSI.html
- matheusmoreira 5y agoI wish this functionality was part of standard HTML.
- mfontani 5y agoFrames are the closest thing HTML has to this
- throwawayboise 5y agoFrames trigger bad memories for some older devs for how they were abused but this is really the best way to do it. Doesn't depend on server modules for includes, and even text-mode browsers generally support frames (but many do not support JavaScript).
- chrisco255 5y ago<p>I think writing in HTML is <em>very</em> frustrating. It can be particularly difficult to write it on a mobile device due to lack of easy access to special symbols.</p>
- LAC-Tech 5y agoLet's face it, mobile devices are primarily for consuming, not producing.
- superkuh 5y agoMobile's deficiencies in UI and networking were bad enough when they were just mobile's problem. But now people just assume everything should be gimped so that mobile can keep up.
- recursive 5y agoI'm sure there are 3rd party keyboards that optimize for different use cases, such as angle braces and double quotes.
- ziddoap 5y ago>It can be particularly difficult to write it on a mobile device due to lack of easy access to special symbols. I'm assuming this excludes laptops, so we're talking tablets/smartphones? If so, out of curiosity, how often are you writing code on a smart phone/tablet? I've never written a line of any code on anything other than a laptop (when travelling) or desktop.
- number6 5y agoFixed production on a terminal running in my phone. Would not recommend.
- _jal 5y agoSeconded. Ssh on a phone is better than no ssh, but good lord is it frustrating. I would never willingly edit HTML (or anything else for machine consumption) on a phone, that's what real keyboards are for.
- litoE 5y agoI've used htp (https://sourceforge.net/projects/htp/ https://sourceforge.net/projects/htp/) to manage what are essentially HTML-only web sites. It provides the ability to use "include" files and macros, which allow me to give all the pages a consistent look and feel that can be easily changed. I usually create a simple makefile so that all the HTML files can be updated as necessary whenever the source files change.
- layer8 5y agoReference with tutorial here: http://htp.sourceforge.net/ref/ http://htp.sourceforge.net/ref/ One selling point is that it only uses regular HTML syntax, so no need for dedicated syntax highlighting. Development seems to have stopped though since 2015.
- brimble 5y agoGood old m4 can get you pretty far, as a template system for generating html.
- TheGoodBarn 5y agoI LOVE static html sites. I fell in love with https://surge.sh/ https://surge.sh/ when I first started making sites, and now for the most part just host everything on GitHub or GitLab pages depending. I also love Vue and the simplicity of remote html resources/dependencies for simple sites. I created a single html file VueJS template that has a bunch of resources out of the box for things that I commonly want if I want to create a quick simple site. Check it out -> https://vue-template.spaghet.me https://vue-template.spaghet.me The beauty of the site is its basically a quine. You can get started by just running: curl https://vue-template.spaghet.me https://vue-template.spaghet.me -o index.html
- jjnoakes 5y agoJust curious - why does your template include web3.js? Do you end up using that on tons of quick simple sites, and if so, what for?
- TheGoodBarn 5y agoThat is leftover from another template, I actually meant to remove it! --- I have created a few NFT / Web3 pages using that template. For the most part, a lot of Web3 UIs are just client side sites that connect to on-chain data, so another super lean use-case for simple HTML pages.
- pipeline_peak 5y agoYears ago I had a simple blog site hosted by 1&1. Because dynamic layouts are so expected to keep pages modern, I found it's often a hassle to go static because web hosting platforms often come with WordPress or some templating engine. I wish I knew a way around this because my knowledge of web design is incredibly small and I intend to keep it that way.
- notriddle 5y ago> I wish I knew a way around this because my knowledge of web design is incredibly small and I intend to keep it that way. Just copy the CSS from http://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/ Anything else is probably overkill.
- pipeline_peak 5y agoThanks, this is great. There’s so little CSS that is actually needed to make a modern looking page. Template engines have tricked us so badly.
- pooper 5y agoIf you use sane markup, modern browsers have "reader mode" that will take care of presentation for the most part. If you don't want to learn web design, you don't have to learn web design. Keep creating and serving sensible html pages and you will be alright.
- 11372 5y agoThis is what happens when UNIX terminal users bring their anti-gui baggage to the web. He doesn't even use pure html he's got all kinds of dynamic stuff going on. Advocate for simple and easy to read UI if you want but come on now.
- Bancakes 5y agoIt's ironic you should call anything UNIX baggage since that whole website is a few kilobytes and renders instantly. As opposed to any 5MB JS-filled flaming cistern of a site a modern developer would make.
- alx__ 5y agoHonestly I feel these sorta of posts are just trolling for views. Hey if you wanna make your site feel like a '90s/Brutalist design throwback that's cool. But don't act like you're a more enlightened developer. When you're just relying on browser defaults and there no basic styles to make the text readable. The pages are a challenge to understand. You can have plain html but using CSS to create some visual hierarchy would go a long way. Feels like there's two text sizes and two colors.
- PaulHoule 5y agoI'd say the author is one of the most respected tech bloggers out there. With pure HTML and possibly some cleanly included JS he could get any visual appearance he wants, such as the common hero video or the effects you see where scrolling manifests differently as you scroll through different parts of the document.
- throw10920 5y agoI'm pretty sure that this is just a lower-strength version of "the wiki trap" mentioned in the article - if you write all of your pages in HTML, then they're going to stay HTML unless you invest the effort in writing a parser+translator that converts all of your content into Markdown or Wikitext or whatever else you might want to migrate that content into. For instance, if you decide you want to give a templating language like Mustache a try - have fun programmatically extracting your content from those HTML pages and translating it into Mustache. Doable? Sure. Easy? Certainly not - and it's going to be very painful and manual if you didn't keep the same format for all of those HTML pages.
- Dunedan 5y ago> if you write all of your pages in HTML, then they're going to stay HTML unless you invest the effort in writing a parser+translator that converts all of your content into Markdown or Wikitext That can be a problem the other way around as well. I wanted to convert a Mediawiki-based site to static HTML pages, but ultimately gave up and instead updated to a recent version of Mediawiki, because I couldn't find a solution which would've kept all existing URLs working.
- JadeNB 5y ago> if you write all of your pages in HTML, then they're going to stay HTML unless you invest the effort in writing a parser+translator that converts all of your content into Markdown or Wikitext or whatever else you might want to migrate that content into. The designed virtue of Markdown is its ease of authoring; why would you want to convert to it? It's surely easier to convert directly from HTML to whatever other format you want than from Markdown to that format.
- notriddle 5y agoBecause you're migrating a living document.
- bachmeier 5y agoThese days, it's easy to type your markdown into a text area and then use a JS library to convert it to html. If they're already loading Javascript, all they'd have to do is insert the necessary Javascript in there. No need to write any html.
- jrd259 5y agoManually edited HTML requires great diligence to be well-formed, and this is important for accessibility.