Closed Frijol closed 5 years ago
+1 Makes sense to do
Porting over discussion from that PR in order to merge without losing the discussion!
@patcon April 24:
Love this idea! Should we think of it like a websites call-to-action? As in, is there a more active or effective framing for call-to-actions that we should use instead? (Channeling our inner Jimmy Wales, perhaps?)
(this is prob mainly worth being pedantic over if we're thinking about putting it in all the readmes :) )
If so, skimming a doc like this: https://www.canadahelps.org/en/charity-life/fundraising-2/how-and-why-to-include-a-call-to-action-in-your-donor-communications/
As mentioned above, some of the most effective online CTAs today exist in the form of buttons.
Double Park Your CTA [...] By this, we mean that you should always place one of your CTAs above the fold, while the other should be located at the closure of the correspondence.
Tracking Your CTAās Performance Itās important to start tracking the effectiveness of your online CTAs, if you havenāt yet.
Google Analytics link tracking? The donation page doesn't seem to have an Google Analytics tracking, but perhaps has other tracking. If not, we could perhaps use bit.ly to track click-throughs? Important that this not be locked away in bit.ly where no one would look, but could keep it in a more accessible spreadsheet using https://dev.bitly.com/spreadsheets.html
Could even allow the spreadsheet to be world-readable if we want to make it simple to see the click-through for anyone (without needed privileged access) -- could "hide" the access token inside a function using the "app script" of the spreadsheet, and include that as a custom formula. So a read-only user would only see the formula in the cell that calls for the token, but the token should be concealed. Could also put the whole "fetch the click-through count" logic totally in the "app script", and that would also work.
Anyhow, lemme know if any of this sounds nifty, and I can help if that's of interest :)
@Mr0grog on April 26
Google Analytics link tracking?
Ha, one of my first thoughts was also āis there a query string or anything we can add to that link that will get tracked?ā Bit.ly seems like a great workaround if thereās nothing built-in. Iām not sure we need the whole spreadsheet setup, though, even if it seems pretty nifty.
My first worry there is that folks who spend any significant amount of time on GitHub have been trained to see these a status indicators rather than calls-to-action. Maybe the popout
style would help it stand out, though. Not sure what iconography would be relevant.
if we're thinking about putting it in all the readmes :)
Thatās probably a good idea, but I feel like the right way to beg for donations in the Readme of a project repo (especially in a software/code-focused one) is probably different than what makes sense in the overview repo, so maybe make a separate issue for it so it doesnāt hold up this?
Double Park Your CTA
Oh, maybe shield at top, same kind of descriptive section with link at bottom?
I'd like to suggest we add, at the bottom of this repo's readme, a footer like:
Thoughts on this? Any hesitations? Suggestions for wording changes?