I have tried various methods in the past, including a Notes layer in the design.
Here is something seemingly bullet-proof.
Somewhere accessible on your local device, save a file called log with a txt extension (log.txt) or as I do log.xara.
If your default text editor is Notepad, use log.txt.
If in my case it is Notepad++, use log.xara and associate Notepad to .xara files (not XAR, do note).
Open your log file and add .LOG and save and close it.
This is a Notepad feature that admins have always used to record the date and time every re-opening of the file. Notepad++ does not have it.
I use this when I am working on the clock.
Otherwise, omit the .LOG or, as I do, create log.md, for posher Markdown-formatted documenting.
Back to Xara.
Off the design page, create a line of text, labelled LOG and in Web Properties > > Link > Link to file > Browse to your log.txt/md/xara file > OK.
Save your design file. What you now get is <design file>.xar and a new folder <design file>_xara_files. In the folder is your log file.
When working, select LOG and in the pop-up click on Link to file: log.txt/md/xara
The text editor kicks in.
Add your update and Save and Close.
When you Export or Publish, the log.txt/md/xara file is put in the index_htm_files folder.
log.txt is viewable through URL/index_htm_files/log.txt.
Other extensions are downloadable: URL/index_htm_files/log.md & URL/index_htm_files/log.xara.
If you don't want the log to be published, rename the <design file>_xara_files folder or move the <design file>.
You could put the above LOG link(s) on the design page and when rendered, they will show or download as above.
tl;dr:
All you are doing is linking to an empty file (or with .LOG) in it and Xara does the rest.
Acorn
Bookmarks