Considerations for Using Markdown Writing Apps on Static Sites
If you run or have lately switched to a static website online generator, it’s possible you’ll in finding your self writing numerous Markdown. And the extra you write it, the extra you wish to have the tooling enjoy to vanish in order that the content material takes center of attention. I’m going to provide you with some choices (together with my favourite), however extra importantly, I’ll stroll regardless that options that those apps be offering which can be particularly related when opting for. Here are some key issues for Markdown modifying apps to assist the phrases drift. Consideration #1: Separate writing and studying modes UX rules let us know that modes are problematic. But in all probability there’s an exception for textual content modifying instrument. From vi(m) to Google Docs, separate modes for writing and studying appear to attraction to writers. Similarly, many Markdown editors have separate modes or perspectives for writing, modifying and studying. I occur to love Markdown editors that offer a side-by-side or paned design the place I will be able to see each immediately. Writing Markdown isn’t the similar as writing code. What it seems like issues, and having a preview can provide you with a really feel for that. It’s roughly like static website online turbines that auto-refresh so as to see your adjustments as you’re making them. Having each edit and preview mode lively immediately mean you can really feel extra hooked up to the completed product. In distinction, I’m no longer partial to the one-mode-to-rule-them-all design the place Markdown formatting robotically converts to styled textual content, hiding the formatted code (carried out in some shape via Dropbox Paper, Typora, Ulysses, and Bear). I will be able to’t stand the paintings of futzing with the app to switch a heading stage, for instance. Do I click on it, double-click, triple-click? What if I’m simply the usage of the keyboard? It’s no longer such a lot that those options aren’t helpful, it’s that they damage my drift. I wish to see all of the Markdown that I’ve written, although the tip consumer received’t. That’s something that I do need a Markdown editor to borrow from code editors. Consideration #2: Good issues Some Markdown editors permit complete customization of editor issues, whilst others send with great ones out of the field. Regardless, I believe a just right editor will have to have simply the correct amount of styling to distinguish simple textual content from formatted textual content, however no longer such a lot that it distracts you from having the ability to learn it and center of attention on the content material. Even with the preview pane open, I generally spend maximum of my time taking a look on the modifying view. Different colours for every taste Since lots of the textual content within the editor isn’t going to be rendered as it could within the browser, it’s great to temporarily see which textual content you’ve formatted the usage of Markdown. This is helping you decide, for instance, whether or not a URL is if truth be told written out within the textual content or is used within a link. So, I love to have a unique colour for every Markdown taste (headings, hyperlinks, daring, italic, quotes, pictures, code, bullets, and so forth.) Colors let you know which textual content has Markdown formatting implemented. Apply daring and italics types too I want to make use of asterisks for Markdown formatting all over I’m ready to (e.g., daring, italics, and unordered lists), so I in finding it useful to have further styling past colour to differentiate daring,…
Like to keep reading?
This article first appeared on css-tricks.com. If you'd like to keep reading, follow the white rabbit.