Markdown Formatting Help: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
Markdown supports rich text editing.<br><br> | Markdown supports rich text editing.<br><br> | ||
Markdown in CommitCRM follows the popular markdown syntax suggested by by | Markdown in CommitCRM follows the popular markdown syntax suggested by by [https://daringfireball.net/projects/markdown John Gruber’s Daring Fireball].<br><br> | ||
Markdown is intended to be as easy-to-read and easy-to-write as is feasible.<br> | Markdown is intended to be as easy-to-read and easy-to-write as is feasible.<br> |
Revision as of 10:51, 27 November 2019
CommitCRM version 24 and up.
Markdown can be used when writing knowledge base articles.
Markdown supports rich text editing.
Markdown in CommitCRM follows the popular markdown syntax suggested by by John Gruber’s Daring Fireball.
Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
Markdown consists of characters like asterisks, apostrophes, space and other which have a special function.
It also supports inline images, embed external links (URLs), link to your other knowledge base articles and more.
Below is a short summary of Markdown options.
For more detailed syntax please refer to Daring Fireball Markdown (opens in new window).