MxAshlynn

coder, producer, music fan, teagirl


my building-gamer blog
cohost.org/MxBuilder
my yurivania shrine
midnightpalace.gay/
You must log in to comment.

in reply to @MxAshlynn's post:

Honestly I don’t think there’s really a developed standard for this. I’ve taken part in that discussion and even have its badge on my site (WeMakeSmall.Games).

It’s honestly like a vibes kinda deal. Going for the simpler times when JS / Dynamic pages didn’t like consume the web. The purpose is also to allow older devices and operating systems from that time period to load Web 1.1 pages

Follow up question, if you have the time: 🙂

Do you happen to know why the discussion settled on HTML 4? I understand avoiding Web 2.0 items like <canvas>, but HTML 5 also added some really nice semantic tags like <article>.

If the goal is to step back to something simpler, why not xhtml or HTML 2?

I'd argue that outdated wysiwyg tooling like FrontPage '97, DreamWeaver MX and Bluegriffin/Composer and the like go a long way to approaching that feel, at least for the more "rich" websites.

For the lower-end "web 1.0" feel, you can always use Word '97.

I really agree! This is actually where I started me old webdev explorations from. What I'd love is an old tool like that can still run/is easy to emulate on Win 10 and produces plain HTML output that I could then tweak by hand

I don't suppose you have any tips for a tool like that?

The best, easiest to install/run out of these is probably Composer or KompoZer, they're outdated tools but they should run fine from Windows 10.

Frontpage 97, Word 97 or Frontpage Express shouldn't have any problems on current Windows, either, but it can run in a Windows 95/98 VM and the media is readily available from winworldpc.

Amaya is another open-source option, a bit janky; not sure if it had any builds for Windows.

Finally, I think Libreoffice and the like, most word processors can save to .HTML; you could always just set your document up with Times New Roman and have fun with it :D