Closed nottrobin closed 6 years ago
From @barrymcgee on September 23, 2016 14:58
@caldav Can you confirm the copy change here? Perhaps this should go in the site-wide footer?
From @caldav on November 22, 2016 17:43
I don't think reporting bugs for snapd itself should go in the site-wide footer. We have 4 bug reporting links we ideally want:
For #2 I think we should follow what we are doing on docs.ubuntu.com (last item in the left nav)
From @matthewpaulthomas on November 6, 2017 10:59
In a design review recently, I suggested that the footer contain something like
You can contribute to snapd, snapcraft, or this Web site.
Spec updated with text similar to my proposal above: “You can contribute to, or report problems with, snapd, snapcraft, or this Web site.”
(I drew the line at three links. That we currently consider “the documentation” as a separate Web site is an implementation detail; the “this Web site” link could go to the appropriate place depending on which page you were on.)
On https://snapcraft.io/ it says "Fork snapd on GitHub". This should be updated to more generically point users at the snapd codebase, from where they can do many things - fork, file bugs, file PRs etc.
Action: Tweak the wording.
From @nottrobin on August 30, 2016 7:11
Nowhere on the site (that I could find) directs users to the correct place to file bugs with
snap
the application. The correct place is on Launchpad.Process
Go to the community page. Behold that it doesn't mention the Launchpad bugs list.
I'm not sure whether this should be as a section within the community page or as an item in the footer, or both.
I've also created a PR to mention this bugs list in the README for the
snapd
project.Copied from original issue: canonical-webteam-archive/snapcraft.io-static-pages#191