Closed
Bug 1059685
Opened 10 years ago
Closed 10 years ago
Add user help for Markdown
Categories
(Bugzilla :: Documentation, enhancement)
Bugzilla
Documentation
Tracking
()
RESOLVED
FIXED
Bugzilla 6.0
People
(Reporter: glob, Assigned: koosha.khajeh)
References
Details
Attachments
(1 file)
9.12 KB,
patch
|
dkl
:
review+
|
Details | Diff | Splinter Review |
help within the current markdown implementation (bug 330707) links to a number of external sources. this is problematic because we have no control over the content on these pages nor their availability, and in some cases isn't completely accurate (for example it states that we support github flavoured fenced code blocks, however we don't support language specific syntax highlighting). all our supported markdown syntax should be documented on a bugzilla template page, and a 'help' link to this page should be added near the markdown checkbox.
Updated•10 years ago
|
Whiteboard: [roadmap: 5.0]
Comment 1•10 years ago
|
||
Since it is related, on show_bug.cgi (and anywhere else the "Use Markdown for this comment" text appears), we should provide a link on the word 'Markdown' to the help text. 90% of users to Bugzilla won't know what Markdown is and the common syntax for it.
(In reply to sgreen from comment #1) > Since it is related, on show_bug.cgi (and anywhere else the "Use Markdown > for this comment" text appears), we should provide a link on the word > 'Markdown' to the help text. 90% of users to Bugzilla won't know what > Markdown is and the common syntax for it. i agree, except i think it should be a separate 'help' link instead of linking the word 'markdown' (see comment 0).
How elaborate should it be? I believe something like the help on Github [1] with its concise format is good enough. [1]: https://help.github.com/articles/markdown-basics
Comment 4•10 years ago
|
||
That github page is probably about perfect for our page.
Updated•10 years ago
|
Whiteboard: [roadmap: 5.0]
Comment 5•10 years ago
|
||
Koosha. I would like to get this in right before we branch for 5.0. What does your workload look like and do you feel like you will be able to work on this soon? If not I do not mind taking it over . Just let me know. Thanks! dkl
Flags: needinfo?(koosha.khajeh)
(In reply to David Lawrence [:dkl] from comment #5) > Koosha. I would like to get this in right before we branch for 5.0. What > does your workload look like and do you feel like you will be able to work > on this soon? If not I do not mind taking it over . Just let me know. > > Thanks! > dkl I can start working on it very soon. I just wanted to first double check the code and make sure that everything works as expected, then write the user doc based on the rules followed by the markdown processor. I think we are now at a good stage to start writing it. One question: should I write the doc under the same section of documentation or move it to somewhere else?
Flags: needinfo?(koosha.khajeh)
Comment 7•10 years ago
|
||
(In reply to Koosha KM from comment #6) > I can start working on it very soon. I just wanted to first double check the > code and make sure that everything works as expected, then write the user > doc based on the rules followed by the markdown processor. I think we are > now at a good stage to start writing it. Cool. Just wasn't sure if you were back on a full load at school or not :) > One question: should I write the doc under the same section of documentation > or move it to somewhere else? We want it to be a page.cgi page so we can link to it from the markdown checkbox (help) link from the show_bug.cgi page. We should also mention the help page from the rST docs as well but no need to duplicate it. Use template/en/default/pages/quicksearch.html.tmpl as an example (page.cgi?id=quicksearch.html) dkl
Attachment #8493191 -
Flags: review?(dkl)
Severity: normal → enhancement
Summary: markdown help shouldn't link to external sources → Add user help for Markdown
Comment 9•10 years ago
|
||
Comment on attachment 8493191 [details] [diff] [review] patch_1059685_1 Review of attachment 8493191 [details] [diff] [review]: ----------------------------------------------------------------- Looks good! r=dkl ::: docs/en/rst/using.rst @@ +798,5 @@ > have your comments generated as HTML. For example, you may use Markdown for > making a part of your comment look italic or bold in the generated HTML. Bugzilla > supports most of the structures defined by `standard Markdown <http://daringfireball.net/projects/markdown/basics>`_. > +but does NOT support inline images and inline HTML. For a complete reference on > +supported Markdown structures, please see its syntax guide available at ``page.cgi?id=markdown.html``. For a complete reference on supported Markdown structures, please see the `syntax help <../../../page.cgi?id=markdown.html>`_ link next to the markdown checkbox for new comments.
Attachment #8493191 -
Flags: review?(dkl) → review+
Updated•10 years ago
|
Flags: approval?
Updated•10 years ago
|
Flags: approval? → approval+
Comment 10•10 years ago
|
||
Thanks Koosha! To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git 1488a58..d416aab master -> master
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
Fixed error from t/008filter.t To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git d416aab..e877bb3 master -> master
Updated•10 years ago
|
Target Milestone: Bugzilla 5.0 → Bugzilla 6.0
You need to log in
before you can comment on or make changes to this bug.
Description
•