ShaneCurcuru
commented
4 years ago Separately: consider adding a link to submit GitHub PRs against content pages. This encourages anyone with GitHub experience to just dive in with their suggestion. Obviously, this may not fit your workflow, but with the number of tech workers looking for ways to help, this is an easy way to hint to them you're looking for contributions. You can also use a Pull Request Template to standardize how they look, including pointing to your "FTC Editorial Guidelines" (which made me think of the US FTC 😸 )
Example code (for another site, pathing needs to be adjusted) for _includes/footer.html
<i class="fa fa-edit" aria-hidden="true"></i> <a href="{{ site.github.repository_url }}/blob/{{ site.branch }}/{{ page.path }}" title="View Code {{ page.path }}">See the code under this page</a>, or <a href="{{ site.github.repository_url }}/edit/{{ site.branch }}/{{ page.path }}" title="Open GitHub Issue on {{ page.path }}">Propose change on GitHub</a>
People keep on asking how to add new resource to the site. This indicates that our current way (link to the google form on the resource page) is not sufficiently discoverable. We may want to consider exposing more prominent "add more resources" button somewhere more visible.