Background
- I’m building a web application for a client.
- This app will be accessible to the world and will be placed in a directory (e.g.,
/my-app) in web-root. A subdomain isn’t an option as they don’t want to cough up the dough for another SSL cert. /my-appis the only directory that I’m allowed to touch (unreasonable IT guys).- I’m using an icon set which requires attribution.
- I’ve contacted the original author of the icon set and have gotten permission to link back to his work in the
THANKSsection of ahumans.txtfile. - I also feel like I should mention some other people’s work. This information combined with the above will probably take up a good 20 lines, so a separate file like
humans.txtseems like an ideal place to put this considering that I’ll be serving minified markup, CSS, and script files.
Questions
-
Since I’m not allowed to place a
humans.txtfile in web-root, (and even if I was, it wouldn’t really make much sense to put it there as it only applies to the/my-appportion of the site) is it acceptable to do the following:- Create:
/my-app/humans.txt - Place:
<link rel="author" href="//example.com/my-app/humans.txt">in my markup
- Create:
-
I’ll be serving strict HTML 4.01 and the
authorvalue for therelattribute doesn’t seem to be a recognized link type in that specification. Do I need to do anything extra to define theauthorlink type, or is the act of using it enough?
I don’t even know if there are any non-spider tools that actually use this file at the moment, but I’d like to minimize the chance of this not working in the future when something does come along.
I think it is ok to put the file in the applications own directory, since it clarifies that it is specific to the content inside the directory and not all the other stuff you might find in the root directory.
Of course it would be nice if there are 0 errors in HTML strict mode. However this is one situation where you have to decide if you want to
However I can not make this decision for you 😉