1. No tags are needed for this one!
2. The user neen not see the "site tag" info. But the GUI must always arrange for the site tag info to be placed into the source file prior to running XeX.jar on the source file.
3. The GUI would automatically generate a directory subbordinate to the working directory into which files for the new site would be placed. Suppose we call it generated "hw". (The user might be asked for a symbol to denote the site. This may be better than randomly generating a meaningless name. The user should also be asked for one to three symbols to be used for the site title. These words would be provided when XeX.jar is run as "command line arguments".)
4. The GUI would prompt the user for "site parameter input". Automatically generate the .xix file and an initial "empty" .xex file. Run XeX.jar on thes files to generate the .html file. Suppose we call them hw.xix, hw.xex, and hw.html.
5. The GUI would provide the user with a view of the (trivial "empty") page for the site.
6. The GUI would provide the user with a buffer into which XeX code can be placed either by mousing or by tying. There is no need to show the user the "init" info.
7. The user would type "Hello world!" and then ask that the system be regenerated. The GUI would save the "source" file, rerun XeX.jar, and present the new "site" for the user to see.
8. The user would indicate that it is "finished" with this site. The GUI would then "close" it -- returning to the "top level" of XeX GUI.