It's 1997, how do you build a website?

CAUTION: if you put 1997-era software on the public-facing internet then you have 25 years of known security bugs to worry about.

In 1997 I worked on a commercial/intranet web app using Perl 5, with CGI.pm, behind Apache httpd, on a Unix box. I think we supported Dec Alpha, Solaris, and IRIX?

These all (well, not really the OSes) still exist in modern forms, mostly unchanged, so if you really want to make it public, at least have a modern Apache facing the world. If you use a late 1990s Linux distro like https://archive.org/details/debian_1.3.1 you'll be using effectively the same environment.

What I did in 1997 was to implement my own template language, so I could have Perl process it to add the header/footer. It was something like "$$ insert filename.html $$" or something else dead simple like that.

I used xemacs as my development environment, though of course many used vi back then too, and I used NEdit for a while in the mid-1990s, which is more like Notepad.

We used CVS for version control.

To publish content now, using your home computer, get your router to forward external connections for a given port to the M1 Mac. Then use a dynamic DNS service so others can connect to your machine by name.

I haven't done this last step for about 12 years and don't know how it's done these days. Back then I could set it up with DynDNS but they stopped free hostname services back in 2014. Also back then I could use the built-in Dynamic DNS tooling in my router.

Well, I started out using Microsoft FrontPage at one point, but once I knew enough about HTML I migrated over to Notepad, driven in part by it being the fashion among some percentage of the developer community at the time (there was an attitude where the less tools you needed, the more you were taken seriously as a developer, with WYSIWYG ones getting the least respect).

I know I used FTP to upload the pages, though I'm not sure which program I used.

And I usually used free hosting providers too. More like Tripod and my ISP than Geocities, but it was all usually the same anyway. No (or very little) support for anything beyond HTML, CSS and JavaScript, and the ever present ads all over the place.

If you want to simulate this setup with an M1 Mac, then probably TextEdit and the FTP program of your choice along with Neocities.

When I did my first webdev in 1997 I would use Geocities' file manager (think it looked like this, although it wasn't affiliated with yahoo at the time: http://ibcomp.fis.edu/graphics/tech/geocities.htm) and probably used WS_FTP as well for publishing content. Didn't use CSS, although it existed (center tags were nice) or much javascript (maybe just alerts).

BTW, this text on the site is false: "Geocities has one big advantage - it has been around a long time, and will probably continue, so it won't suddenly disappear and take your web-site with it"

Also used to use a bigfoot.com "Email forwarding for life" which I assume stopped working at some point.

I was the entire Tech Staff, for a 200 user dial-up ISP back then, our servers were running Windows NT 3.51 with IIS, and I used Windows Notepad to edit html.

I used:

Developed and served from Macintosh: macOS, BBEdit, WebStar (the most popular Mac HTTP server), Frontier (for programming, app integrations via AppleEvents, and object DB), FileMaker for integration to business data.

Developed on Macintosh, servers by Solaris or Linux: BBEdit, MacPerl, (MacPython but that may have come in 1998), Apache with CGI to Perl/Python. I think I started this to use Postgres about then.

I worked for a hosting company so I had free or discounted hosting. I used HomeSite to write the HTML and then some kind of FTP app (I can't remember which) to upload the changes. Then I would test the results in Netscape Navigator.

I played around with Microsoft FrontPage and NetObjects Fusion but always found my way back to HomeSite.

This was all running on Windows 95 on a home-built PC.

8MB RAM! would be a luxury in 1997.

I would likely use Hotdog[1] for the website. It came in a CD with a Magazine and that is how I learnt what HTML was (before I ever got connected to the Internet).

1. https://en.wikipedia.org/wiki/HotDog

For web serving, IIS, Apache, and NCSA HTTPd were available and in use at that time frame. They would have run on Windows NT 3.5/4 (IIS), or some sort of real unix (AIX, Solaris, etc) but OpenBSD, NetBSD, FreeBSD, BSDi, and Linux were also available. Oh, and NeXT, where it all began.

Microsoft FrontPage (Express?), Clearly. I recall setting up the webdav stuff and php3 configs so you could use the % tags to write PHP, and push to the webserver all from inside FrontPage. Although that was circa 1999; I'm not sure when all the open source support came.

For publishing: vanilla FTP it (or transfer via SMB) to the `public_html` directory your ISP or university provides in your user directory on their servers. It then becomes available at `/~username/` under their hostname.

Served via Apache on Solaris. `.htaccess` for fun and profit.

Oracle VirtualBox to emulate Windows 95 (which you can get at https://archive.org/details/win-95-osr-2). It already comes with Internet Explorer. Good luck with setting up tcp/ip networking.

I'd use Notepad to write code. The webpages should obviously be designed as complex nested tables, with valid HTML 4 tags from the era (https://www.w3.org/TR/html4/index/elements.html). Throw in non-standard MS tags like .

To get that "rounded corners" look on your borders without CSS, create the rounded corner gifs using pirated Photoshop 4 from this warez disk (https://archive.org/details/twilight-cd08).

For hosting, I recommend getting a "Shell Account" (here is a list https://lowendtalk.com/discussion/160534/free-linux-shell-ac...). You might want to make sure it supports FTP without SSH. Might need to manually transfer files from Windows using Telnet (http://webfaq.halcyon.com/ftp/ftp-win95/index.htm)

Godspeed.

---

👤 tmaly

Assuming you have a small machine at some host running RedHat

Setup Apache with cgi enabled. Use Vim to write your html and Matt's Script archive to get you started with some CGI.

This is what I did back in 1997 to build sites for businesses.

---

👤 rrr_oh_man

AOLpress or Macromedia Dreamweaver! And Notepad.

Your PC feels a bit underpowered, tbh.

IIRC, the typical off-the-shelf system (in my locale, at least) end of 1997 was more like 166 MHz MMX with 16MB RAM and up to 1GB or so of HDD space.

---

👤 thesmileyone

basic html, some frames (remember these?) a few pics, exact match domain name, add content and build some backlinks... rinse and repeat ready for google adsense in 2003 for your $100k a day profit.. back when it was really easy to make bank online.

---

👤 nprateem

Image editing with paintshop Pro and use eudora to reply to any emails to the webmaster

---

👤 zoenolan

Lots and lots of tables for layout

---

👤 hnthrowaway0328

Win 95 and Dreamweaver? Or Frontpage.

---

👤 solardev

1. Anything that can emulate Windows 95

2. HotDog, Dreamweaver, and/or Frontpage for HTML editing. They each have their strengths & weaknesses and work relatively well together. Normally I'd lay out pages in Dreamweaver or Frontpage and then clean up the HTML with HotDog. https://en.wikipedia.org/wiki/HotDog. Upload them with BulletproofFTP (http://www.bpftp.com/), an ancient predecessor of Filezilla.

3. Not sure if any of the old hosts are still around. Maybe Neocities.org comes close to the Geocities of old, or else you can get barebones and very cheap but reliable web hosting from https://www.nearlyfreespeech.net/

Get AOL dialup: https://getonline.aol.com/dialup and a 56k modem off eBay, no cheating with megabit connections.

You can emulate old browsers online: https://oldweb.today/

People generally weren't self-hosting their websites back then because phone lines weren't very reliable, and the dialup modems of the day (like today's cable modems) generally had faster download than upload speeds. After the BBS era, commercial internet hosts started becoming pretty common, but they usually used expensive ISDN or T1 lines.

Apache was still in its infancy then, and Microsoft IIS was common.

---------

Overall, I don't think the network stack is really THAT far removed from what we have today. The basics of HTTP were pretty fleshed out already (it was more the HTTPS and DNS security extensions that really evolved), along with better compression and parallelization protocols in HTTP2/3. And of there's been a huge amount of backend server optimizations, caching, reverse proxies, etc. But the old network stack would still work today and you can still run a basic barebones http daemon and firewall the same way you could back then, open up port 80, and watch your box get pwned by the bots. Hell, there are probably still zombie bots leftover from that era running on someone's basement PC, just casually scanning the internet day in and day out, waiting for its chance...

What's changed a lot more (IMO) is more the language of the web itself. HTML was very basic then, as was JS and CSS. Making websites without modern CSS, in particular, is very painful... requiring a lot of nested tables, frames (remember those? they're different from iframes!), etc. A lot of the pain was abstracted away to backend scripting languages (Perl, ASP, Coldfusion) or frontend extensions (Java, Shockwave, ActiveX, Flash) and people didn't really work in vanilla HTML/JS very often (because they were so weak by then). Plain HTML is for your basic Astro Marmalade site with a bunch of animated gifs and whatever, but probably real ecommerce sites (such as it were) wouldn't be written in plain HTML :)

---

👤 dopheide

pico

---