On Tue, Feb 02, 2016 at 02:36:19PM +0000, Michel, Stephen J. wrote: > >- The top priority user story is someone coming to the site and > understanding what it is. > >- Introductory material is still up for discussion -- making sure the > introduction is as effective as possible is (now and always) a very > high priority. > > I'm currently working on *organizing* the material that's currently > on the wiki. My work is currently local but if anyone's interested > in helping out I can make it available online. I have some thoughts > on how we should organize the material, but I'll wait on hashing > them out; there are a couple unresolved questions on my mind.
This sounds great. Maybe to give yourself space to keep working, but to not feel like you're keeping people "in the dark", want to plan to give a report in X days? A week maybe? > <snip> > Given some sources that suggest a wiki may actually discourage > participation (because people feel they're not knowledgeable enough > and are afraid to overwrite old content), I'm a fan of providing two > ways to edit an informational page: > > 1. Pull request to git.gnu.io, or wherever we end up permanently > hosting our site code > 2. A "suggest edits" button on each page which functions like a > wiki-style edit button, but instead creates a pull request from > their edits. That way even those unfamiliar with git can > contribute and become involved. I'll leave it to the design team for final decisions, but this sounds pretty cool to me. I might suggest against creating literal pull requests, though. That would require tossing all the html at the user. In the short term, it might be better to let them have a textentry to describe suggestions in free-form.
signature.asc
Description: Digital signature
_______________________________________________ Design mailing list Design@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/design
