Add a footer with a link to the site repo on GitHub #462
Conversation
Let's make it easy for potential contributors to know how to contribute to this website by adding a footer and linking to the site repo. Include '/fork' in the URL so it's even easier. Closes git#434
|
In the first paragraph of each edition we already say: "For our goals, the archives, the way we work, and how to contribute or to subscribe, see the Git Rev News page on git.github.io." with a link to: https://git.github.io/rev_news/rev_news/ When we send the edition by email, we also add a footer with links to "unsubscribe", "update subscription preferences" and "add us to your address book" and with the following: " You are receiving this email because you signed up to receive the Git Rev News newsletter. Our mailing address is: On the edition on our web site I would be ok to add a footer with a link to the repo on GitHub, but on the edition we send by email it might be a bit too much. @jnareb, @mjaix and @sivaraam what do you think about such a footer? |
|
Yes I was thinking more of the website. This way if people get to the website by other means (ex. Google search, or from the link at git-scm.com/community), then they have a link back to the repo if they wish to tweak the content. |
Yeah, I believe such a footer would be fine. Though I do wonder if it's adding anything more useful than what we have in the initial paragraphs of each edition. It's likely to be helpful in non-Rev News edition pages e.g., Hacking Git", "General Microproject Information". Given the current suggestion of footer text, I wonder if using a "Fork me" ribbon might also be a possible solution. We could also consider not showing it in Rev News edition pages as it's likely not useful there. Just a suggestion that came up to mind. 🙂 |
|
I also think it's reasonable to keep the email version as short as
possible. Don't like the ribbon that much ...
|
|
👍 |
Let's make it easy for potential contributors to know how to contribute
to this website by adding a footer and linking to the site repo.
Include '/fork' in the URL so it's even easier.
Closes #434