I have done several different reverse engineering projects for file formats I was interested in over the years. I am converting my old pages to Google Sites, and will add links and information as time allows. I find that Google Sites mangles my pages a bit when I upload them, and provide some comments on recovering the original pages if you are interested.
I recently did some work on the Iomega 1-Step Backup file format.
I started using what they call the 'classic' version in the late summer of 2016. I seem to have a workable system now after a significant amount of trial and error. If you read the help files on using the built in HTML editor it tells you that some standard HTML key words are not allowed. In particular the following which most of my original pages contained are not allowed:
<!-- comment --> <html> </html> <body> </body> <title> </title>If you try to paste in any of the above it will be ignored and you get a warning messge.
What is not so clear is that files with a *.htm or *.html extension are not treated the same way most other files are treated. Most pages (apparently /home is an exception) allow one to add pages from your local computer. Most files, ie *.jpg, *.lzh, *.tar, can then be accessed normally with a web browser. I expected to be able to add a *.htm file to a page and then open it in my browser of choice. This does not seem to be the case, instead there is an extra step where my browser, firefox in these trials, asks what I want to do with this file. It does offer the option of using the browser to open the file, but first copies it to my local drive and then opens it there. It appears the only way to get an HTML page to display normally in my broswer is to use the google sites 'create' tab to make a new page on their site, select html editing, and then paste in the desired HTML code. Note during page creation you specify the url for the page, but this url may not contain '*.htm' or '*.html' at the end. This is slightly cumbersome, but managable.
If you are part of a select group who downloads and saves documentation you find useful for offline use you may find the 230 kb overhead painful. In all the files I have created to date my original HTML source code has been sandwiched between <tbody> and </tbody> tags near the end of the material downloaded from google sites. Its easy to use a text editor to extract the original page, although a slight nuisance. I am attempting to save my original documentation pages with the source code distribution of the programs discussed in this file format section of my pages so you can avoid this hassel.