Hsc is not a tool for beginners. It does not make HTML easier. It only makes it a bit less painful and brain-damaged — that's all. Therefore, these documents assume that you are already familiar with HTML. There exist several sources for beginners, and this won't be page #1876545 to list these sources.
The user is expected to have already worked with some macro language before.
If you want to utilize the project management capabilities, you should also know how to work with make and write your own Makefiles. As it does not make much sense to use hsc without it, this probably is a must.
For several other advanced topics, it is required to have some experiences with any programming language. Rexx is fully sufficient for these task, and most examples and some supporting stuff is written in this language.
As hsc is a commandline tool, any knowledge of how to work with mouse and icons is not required.
Please note that I'm quite serious about all that. As I don't get paid for every new user, there is no need for me to have as many people as possible using this program. Actually I do not care if you try to use it, find out you can not cope with it, scream out ``Dammit, I'm a loser!'' and jump out of the window from the 27th floor. But I start caring about it as soon as you do not jump out of the window but send me bloody emails with silly questions instead.
So those who now say ``Fine, I always wanted to learn how to write Makefiles'' should consider looking for some other tool or be prepared for jumping out of the window — just in case.
Memory: Well, this mostly depends on your input data. Almost every Unixish system in existence today should run hsc just fine. hsc was developed on AmigaOS and is thus not very resource hungry; the absolute minimum is around 500 KB of free RAM, so an unexpanded A1200 should do. Using the included macro library increases memory requirements to a few megabytes.
Stack: On AmigaOS, the default stack size is 4 KB, this is too little for hsc. The binaries are not linked against any stack-checking or -expansion code, so you should have at least 12 KB of stack, better make it 20 KB. Users of other OS don't have to waste a thought on stack size.
OS and CPU:The AmigaOS binaries require at least OS 2.04 and a 68020 CPU, but a 68040 or higher ist strongly recommended. The binaries in the Linux RPM were compiled for i386 and should run on any x86 system. The kernel version is not critical, but the program was liked against glibc V2.4. Linking against a replacement such as dietlibc is not a problem, but glibc is usually found on development systems anyway. If you run Linux or *BSD on a non-x86 CPU, or HP-UX, Solaris, RiscOS etc., you probably know how to compile your own software anyway.