(Change st link to include blogs) |
|||
Line 31: | Line 31: | ||
| One-page release notes || op | | One-page release notes || op | ||
|- | |- | ||
| Status links (Identi.ca, Twitter, Facebook, etc.) || st | | Status links (Identi.ca, Twitter, Facebook, etc.),<br/>blog posts, other social networking || st | ||
|} | |} | ||
Revision as of 15:16, 9 March 2010
Using link tracking is an easy way for us to find out how people are getting to our download page. People might click over to our download page from any of a number of areas, and knowing the relative usage of those links can help us understand what materials we're producing are more effective than others.
Adding links
Each link should be constructed by adding ? to the URL, followed by a short code that includes:
- an indicator for the link source (such as the wiki release notes)
- an indicator for the Fedora release in specific (such as F41 for the final, or F41a for the Alpha test release)
So a link to get.fp.o from the one-page release notes would become http://get.fedoraproject.org/?opF41.
Link source | Code |
---|---|
Email announcements | an |
Wiki announcements | wkan |
Front page | fp |
Front page of wiki | wkfp |
The press release Red Hat makes | rhpr |
http://redhat.com/fedora | rhf |
Test phase release notes on wiki | wkrn |
Official release notes | rn |
Official installation guide | ig |
One-page release notes | op |
Status links (Identi.ca, Twitter, Facebook, etc.), blog posts, other social networking |
st |