![]() Rich Text: “In the Confluence rich content editor, adding tables and managing tabular content is a breeze. Tables are only supported by inline HTML, which you can write whenever a markup element isn’t covered by Markdown’s syntax.” Rich Text: “I can do code examples and script listings too! Sure, you’ll need to wrap Confluence’s Code Block macro around them – but once that’s done, you can define proper syntax highlighting for your programming/scripting language, line numbering, and more.” Round #5: Inserting Tables A no-brainer, right?” Absolutely – code is automatically indented in any development environment. Markdown: “Just indent your lines of code with a tab or at least four spaces so they’re recognized as code. To add line breaks within a list item, simply press Shift+Return in the Confluence editor instead of pressing the Return key.” Round #4: Embedding Code and Block Quotes That just looks like a workaround, not a real solution. If you don’t want the problem in the above tweet to happen to you, you’ll need to enter a tab (or four spaces) before you begin to write paragraphs within a list. Markdown: “Choose your favorite list item ( */ +/ -) to create bullet points, or just start numbering your ordered list items ( 1., 2., etc.).” Round #3: Using Bulleted and Numbered Lists Instead, write a heading or paragraph, and assign the corresponding paragraph format.” Using the rich text approach, writers need only to select the desired heading level or paragraph format from the toolbar once. Rich Text: “I don’t like blank lines, useless spaces or hashes. ![]() ![]() Mark recommends: “Write consecutive lines of text followed by a blank line to create a paragraph.” # This is a H1 for a first-class heading, or # This is a H2 for a subheading.” Creating a paragraph is even easier. Markdown: “Enter 1 to 6 hash characters before your headers, e.g. Round #2: Defining Headings and Paragraphs Today, rich text authoring is done collaboratively in a web browser, using a content collaboration platform such as Atlassian Confluence. Just create a new document, give it a title and away you go.” Before the web arrived, using a desktop text processor to format rich text was the norm. Markdown: “Oh, this one’s easy – open a new document in the text editor and start typing.” Or use an online markdown editor such as dillinger.io that supports synchronization with Dropbox, Google Drive and Github. Mark and Rich will flex their muscles to see who can create and publish content faster and easier. Supported by: the Atlassian Confluence collaboration platform and wiki, and other cloud-based content creation tools such as Google Docs. Rich’s strengths: advanced content formatting skills, editor shortcuts (and he’s not afraid to use them), and immediate availability of the resulting document. Rich doesn’t see many advantages in separating editing from viewing: “Juggling markup syntax? What is this, the ‘90s?” In the right corner: Richard “Rich Text” Formatting – used by millions of casual writers who want to see their results instantly. Emacs), and file repositories such as Github. Supported by: Jekyll, your favorite text editor (e.g. Mark’s strengths: code handling, offline availability, minimalism and something he likes to call “bringing it down.” md, but you don’t need an MD to understand it – the syntax is so simple that any developer in the world can adapt to it with ease. You can recognize Markdown easily by his file extension. Mark “Markdown” Down, lightweight champion of the world for writing web content into plain text files. Today, we’re going to settle the question once and for all – which is superior? Documentation in a plain-text editor using Markdown, or creating content in a rich-text editor the WYSIWYG (what you see is what you get) way? How will it be decided, you ask? A good, clean head-to-head fight! Mr.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |