-
Notifications
You must be signed in to change notification settings - Fork 80
Conversation
* gh-pages: words link to website instead of twitter Update repo URL Ignore .sass-cache Use design from todogroup.org
I'm a fan of how this was executed. 👍 I'm not a fan, though, of the user's perspective: how this generates URLs that seem to have robot barf in it. URLs with big fragment values that carry important data generally don't fill me with confidence. |
I agree. Here are a few ideas to make this better:
|
I made a few tweaks to the design. It could use a real designer at some point, but this highlights what I was envisioning. |
@mislav I updated this to use this url format: |
Looks great (both design and URL path). Even if query parameters in the URL are human-readable, I think seeing them betrays that this text has been auto-generated and that might make the CoC feel less personalized and less legit. I'm just speaking for myself here. |
Here's how to copy contents of a input.select()
document.execCommand('copy')
window.getSelection().removeAllRanges() |
Alright, I'm pretty happy with where this is at. I would love feedback or suggestions on what else is needed. There are some changes I need to push to the todogroup.org styles to make this work, but I'll get a PR open for that so we can merge both at the same time. |
If you're going to have magic copy behavior, you have to make the users know. Otherwise they probably won't figure it out by themselves. Maybe it's best to have an explicit “Copy to clipboard” button. |
Hell I actually like it! I think it's good enough to start with, we can iterate later and making it a bit fancier. Some people will use this functionality, others will simply copy the index.md |
* origin/gh-pages: Incorporate changes from Amy and the Geek Feminism CoC Fix simple typo in index.md
Make placeholders configurable
@mislav thanks for all your feedback. It's live: http://todogroup.org/opencodeofconduct/ One thing I think we'll want to tweak is the snippet that gets copy and pasted into the project. Since tons of projects will have this, we'll want to make sure it's well-worded:
|
The Code of Conduct will gain more adoption if it's easy for maintainers to adopt it. Some projects may still want to fork it and make more drastic changes, but for a significant portion of the community, the standard template will suffice. This is an attempt to demonstrate what was suggested in #7:
Updated gif, here is the original
If we want to go this route, there's still some more work to do here:
What do you think?
/cc @caniszczyk