However for the generated files that are published, it seems a bit ugly and unexpected. And after the experience with implementing blog posts in GUISE-108, it should be simple enough to simply remove the underscore prefix for the target filename. This will allow us the convenience of designating artifacts as "private", but still have their filenames look "normal" on the actual site. In other words, the prefix _ would be like a flag set in the filename itself. Before this might have seemed like a hack, but now it appropriate to say that we have certain filename patterns (such as for blog posts) to indicate certain types or attributes of artifacts.
This ticket would be a good place to add a configuration for the veiled artifact prefix, already mentioned in GUISE-42. Adding a way to disable it altogether would be nice as well.