Move the help button?
post by Vaniver · 2010-12-28T11:42:45.512Z · LW · GW · Legacy · 14 commentsContents
14 comments
It took me a while to find the "help" button for comments, and we seem to have a steady stream of people who have trouble finding it on their own. I suspect that's because it's floating off in a corner you don't have much reason to look at. Would it be difficult to move it to the immediate right of the "cancel" button, instead of the far right, and possibly rename it "formatting help"?
(I don't know enough python to look at the site's code, or I would check this out myself.)
14 comments
Comments sorted by top scores.
comment by NancyLebovitz · 2010-12-28T17:21:35.239Z · LW(p) · GW(p)
I think relabeling it would help more than moving it, but moving it might help.
Replies from: pjeby, wedrifid↑ comment by wedrifid · 2010-12-28T19:52:07.871Z · LW(p) · GW(p)
I think relabeling it would help more than moving it, but moving it might help.
Change it to "How To Quote".
Replies from: NancyLebovitz↑ comment by NancyLebovitz · 2010-12-28T20:07:52.383Z · LW(p) · GW(p)
No, I'm voting for "formatting help".
Unfortunately, "We don't think html is cool enough" is too long. Actually, I think markdown has some improvements over html, but I'm not sure having two sets of habits is worth it.
Replies from: jimrandomh, nhamann↑ comment by jimrandomh · 2010-12-29T06:38:37.606Z · LW(p) · GW(p)
It's not a matter of coolness, but resistance to abuse. Unrestricted HTML is not an option for comments, because it can contain Javascript, or formatting that breaks the entire page. A restricted subset of HTML could be allowed, but it would be about as complicated to support as Markdown is. Support for Markdown came free with the Reddit code base, but adding restricted HTML as an option would be a nontrivial project.
↑ comment by nhamann · 2010-12-29T02:47:05.226Z · LW(p) · GW(p)
Agreed on "formatting help" as the link name, but HTML is bad news for making up content. It's way more verbose than Markdown, and I would much prefer not to manually insert paragraph tags. Besides, Github uses Markdown for readmes now, so I can see it becoming something of a standard (if it isn't already).
comment by Raemon · 2010-12-28T23:04:11.742Z · LW(p) · GW(p)
I would never have known this feature existed if this post hadn't pointed it out to me. Put it next to to the "comment" button, and preferably make it bright red or something. (Ideally, it would be bright red UNTIL you'd clicked on it, and then it'd turn a less obtrusive color).
comment by artsyhonker · 2010-12-29T20:40:01.095Z · LW(p) · GW(p)
I certainly hadn't realised it was for formatting and might have had a look had I known.
comment by jimrandomh · 2010-12-28T16:53:54.417Z · LW(p) · GW(p)
This change is trivially easy, if people agree that it's desirable. Just change the float:right to float:left of the .commentreply .help-toggle node, at static/lesswrong.css:226.
Replies from: Vanivercomment by Normal_Anomaly · 2011-01-03T01:39:15.079Z · LW(p) · GW(p)
There's probably more people who support this than are willing to make a comment saying "me too". Upvote this post and downvote the attached karma dump if you support a move and/or rename and haven't commented yet.
Replies from: Normal_Anomaly↑ comment by Normal_Anomaly · 2011-01-03T01:39:30.493Z · LW(p) · GW(p)
Karma dump for the poll in the parent.
comment by Normal_Anomaly · 2011-01-03T01:37:12.290Z · LW(p) · GW(p)
Definitely move it next to the comment button. I've used it a dozen times and it still takes me a bit to find it, though that's probably the fault of me being scatterbrained as much as anything else. Moving it would be a big help to newbies, who are most likely to need it and least likely to know where/what it is.
Relabeling is probably a good idea too, and I'd suggest "formatting help".
comment by David_Gerard · 2010-12-28T16:55:47.443Z · LW(p) · GW(p)
+1