YellowGrass

Encourage users to use verbatim tags for code in issues (1)

How about a line that says:

Use <verbatim> for code fragments and markdown syntax for styling.

under the text box of the create issue page? Doesn’t seem that obtrusive to me, and it would be very helpful. I keep having to fix other people’s posts…

(related issue: WebDSL/136)

Submitted by Lennart Kats on 7 April 2010 at 13:34

Issue Log

On 7 April 2010 at 13:57 Sander Vermolen commented:

Indeed. When a manual is needed to use a page, this should be a smell that the page is not user friendly. Adding a manual to the bottom of a page makes the situation worse by cluttering the user’s view. I know that using such a manual (or cheatsheet) at the bottom of an editing page is normal for wikis, but then again, I believe we should only use wikis for deciding how NOT to design a user interface. Furthermore, it is doubtful whether users will actually read the manual.

IMO, the best solution would be a graphical editor. Yet this may take time to become available in WebDSL.

On 7 April 2010 at 13:58 Lennart Kats commented:

We sort of had this discussion offline already, but for the sake of completeness, I’ll reply here again. I’m not asking for a manual. I definitely don’t want a complete list of all markdown features down there. Just tell people they can use verbatim for code, stacktraces, logs, etc. And link to another page for general, non-essential formatting/styling.

On 7 April 2010 at 14:17 Sander Vermolen commented:

Currently, I link to the syntax explanation. I can change this to also mention verbatim blocks. Sooner or later, people want to use verbatim words in text, so I’ll explain verbatim in text, verbatim blocks and link to the syntax. Next, people want to use numbered lists as well, so I’ll explain numbered lists, verbatim in text, verbatim blocks and link to the syntax. Next, people want to ….

My point being that we will end up with the Wiki cheatsheets/manuals. These are undesirable. I understand you would just like to mention verbatim and a syntax link now. But since this is in no way complete (not theoretically, but also not practically and not even for an issue tracker), we will end up extending the list and constructing our very own cheatsheet.

On 4 May 2010 at 12:26 Nathan Bruning commented:

You might want to mention somewhere that the input boxes are actually “Markdown-enabled”.

On 4 May 2010 at 12:32 Sander Vermolen commented:

Indeed that is not quite clear. Will fix this as well.

On 19 May 2010 at 14:44 Lennart Kats commented:

Similar issue: department/25 “Answers without verbatim can become completely unreadable”. For the department, a verbatimize button would make sense. Maybe also something to consider for YellowGrass?

On 17 December 2010 at 13:12 Sander Vermolen removed tag 1.00
On 17 December 2010 at 13:12 Sander Vermolen tagged 1.01
On 9 February 2011 at 15:52 Sander Vermolen removed tag 1.01
On 9 February 2011 at 15:52 Sander Vermolen tagged 1.02
On 15 February 2011 at 16:05 Sander Vermolen removed tag 1.02
On 15 February 2011 at 16:05 Sander Vermolen tagged 1.10
On 20 April 2011 at 14:59 Sander Vermolen tagged 1.14
On 20 April 2011 at 14:59 Sander Vermolen removed tag 1.10
On 21 April 2011 at 10:57 Sander Vermolen commented:

Hopefully the live preview for issues (and the markdown manual link) solves this problem.

On 21 April 2011 at 10:57 Sander Vermolen closed this issue.
On 4 May 2011 at 09:17 Sander Vermolen tagged 1.13
On 4 May 2011 at 09:17 Sander Vermolen removed tag 1.14

Log in to post comments