Margaret on the Author-it User Forum list wanted to know whether to use the auto-generated HTML filenames for her output (e.g. 1234.htm where 1234 is the Author-it object code ID number), or add her own ‘logical’ filenames to each Author-it topic object so that she gets filenames like printing_a_page.htm. She particularly wanted to know whether it matters if there are both in the Publishing folder, and whether it affects the way the Help works.
My response:
For HTML output, you’ll get <object_code.htm> unless you have explicitly entered a file name on the topic’s Web tab.
Having the filenames or object codes (or both) is neither here nor there as far as Author-it is concerned. However, you might want to consider your users, your deliverables, and your time!
USERS
If your output is going on to the Web (not internal), then a named file may be more readable. That said, if the output has a TOC/navigation pane the user tends to only ever see index.htm anyway, no matter which topic they’re reading.
DELIVERABLES
CHMs don’t care about filenames—everything is compiled into one file anyway. Other HTML outputs—see the info for ‘Users’ above.
YOUR TIME
To use filenames you have to manually decide on and add a filename to every new topic. There are a few issues to consider with this:
- Filenames should not contain any spaces, unless you are ABSOLUTELY certain that the HTML files will only ever live on a Windows machine/host server.
- Filenames must be unique.
- If you duplicate a topic, you must remember to delete the duplicated filename and replace it with another, unique one. Otherwise you will get at least one topic that’s published as a blank topic where two or more with the same filename exist in the same book.
MY EXPERIENCE
When I first started using Author-it I was still hung up on unique file names for topics. I liked the look of them in a folder list, they had meaning to me, etc. However, the overhead of maintenance became something I didn’t want to continue, so I went back to using the default object codes. And you know what? It really didn’t make any difference at all—except free up a lot of ongoing maintenance time for me. Not one user ever noticed or complained.