Earlier quoted context omitted.
You like to live in hard mode. I like that.
Building a website without JS is not hard.
Entire website in a single HTML file
181–190 of 333 posts
Re: Entire website in a single HTML file
#182Re: Entire website in a single HTML file
#183Re: Entire website in a single HTML file
#184Re: Entire website in a single HTML file
#185Earlier quoted context omitted.
You're describing PDF files, but unfortunately Adobe didn't invest much time or money into making them interactive with a scripting language.
PDFs actually have some support for javascript! I don't know any serious use for it and some PDF viewers refuse to support it (ex: Apple's Preview app), but it does exist.
Re: Entire website in a single HTML file
#186Re: Entire website in a single HTML file
#187Here's a tool that helps builds these by "compiling" all files into one html file https://github.com/sean7601/compileJS
Re: Entire website in a single HTML file
#188HTML and CSS alone are really powerful. I decided not to use any JS on my personal site, but you can still have: + collapsible sections with `details` and `summary`[0] + footnotes, with navigation to/from with anchor tags. You can even apply CSS on the currently selected footnote.[1] + Semantic web that is compatible with everything and has sensible defaults so you can focus on what you're actually doing! + Tiny depl…
Re: Entire website in a single HTML file
#189This is something I've always wanted for virtual textbooks. A single .html file with all the JS, CSS, images as inline data blobs, etc. For most physics, math, CS, etc books, this should be possible. It would make it trivial to download the book for offline use and share it with others. Other than the raster images, the entire content of these types of books would probably fit in a couple MB of text. The use of #anch…
And images can be also embedded. These days you can fake a real URL completely on a fronted side.
Re: Entire website in a single HTML file
#190Earlier quoted context omitted.
PDF has a limitation: it defines page size and the layout of everything fixed to this page, and thus can't do responsive layout like HTML can (reorganizing stuff in the page to match the screen size)
Feature. The dimensioning problem isn't PDFs. The dimensioning problem is computer displays. Get yourself an e-ink display of 10" or 13" (standard dimensions offered by the patent-monopoly vendor across multiple OEMs), and discover that online reading of PDFs is 1) quite pleasant (so long as the underlying PDF formatting itself is sane) and 2) vastly preferable to either HTML or "fluid" ePub or Mobi file formats. Boo…
Notably this is not the standard size for most e-ink devices though, on which pdfs are a pain to read. Mobi/epub files, in contrast, are fantastic on my kindle (and on my phone, and on desktop).
If your argument has to boil down to "this file format is great if you just buy a specific device for viewing them, and eschew viewing them on any of the other devices you already own and use more frequently", I'd say your argument provides more evidence for the counterpoint than for the one you're arguing.
I'm happy you found a good way to consume a fundamentally outdated format, but PDFs are a bad format for the majority of use cases.