Update routes.js

[eugkuo]

Added redirect to https://fleetdm.com/guides/automatic-software-install-in-fleet#templates-for-policy-queries for information on how to reinstall apps. May update this with a different anchor link once updated text is live.

[eugkuo]

@eashaw Updated link to relative link. Thanks for suggesting that. I saw that both were done in the past and I wasn't sure which to use. :-)

[iansltx]

Couple quick notes:

1. I missed this (sorry for the back-and-forth) because I didn't notice the PR was open. More descriptive title (e.g. Add redirect for information on how to reinstall apps) would help here. A PR will take the title of the commit it contains if it's only one commit, so if you tweak the commit message then the PR title will follow.
2. You can branch off of other people's branches, including the branch for a PR, and then target that branch in the PR. Then when that PR is merged your PR will repoint to wherever that PR got merged into. That's helpful in cases like this where your work depends on Noah's, and Noah's actually targets the docs branch rather than main. Extra helpful in that case because we can stage both the docs updates and the redirect so they both go live at the same time (when the docs branch gets merged in as part of the 4.63 release).

lmk if the above git-fu would be more helpful in the form of a pairing session and we can do that :)

[eugkuo]

lmk if the above git-fu would be more helpful in the form of a pairing session and we can do that :)

@iansltx A pairing session would be 10000000% helpful :p