Whoever made Jira’s markup syntax: Straight to jail.
The thing I dislike most about Atlassian products is that each of them has a completely different formatting engine and markup syntax. You’d think they’d be consistent but noooo
Atlassian doesn’t even have consistency within single products! I’m using Jira Cloud at work, and while most fields support markdown (e.g. three backticks to start a code block) there are a few that only support Jira’s own notation (e.g.
{code}
to start a code block). It’s always infuriating when I type some markdown in one of the fields that doesn’t support it for some inexplicable reason.
Jira Developers: for the love of god can we PLEASE stop trying to shoehorn literally fucking everything into our platform?
Jira PMs: slaps roof this bad boy can fit so much scope creep
Discovering obsidian has been a blessing for my sanity and made me less lazy for taking notes.
Plus I can use latex to transform md into docx and there’s decent pdf support so I don’t need to play with the circus of WYSIWYG pain that’s MS Word.
Pandoc is also great!
Definitely, I said latex but I wanted to mean Pandoc.
The only thing is that applying a docx theme format to Pandoc was very challenging, although I would blame docx, not pandoc.
I keep meaning to check out Obsidian, but I’m like you said, lazy.
Be lazier! I believe in you.
Markdown is good. I use it when working in the company since the format is ubiquitous. I do writing my blog posts with Markdown (Hugo for the curious).
But personally, or working with a bit more niche team, for writing personal documentation I prefer Asciidoc [0]. It has better syntax and have some nice functionalities like Table of Contents.
For personal notes, nothing can surpass Org Mode [1].
doesn’t Markdown have a TOC function if you have at least 2 headings?
I was looking for a journaling app that didn’t have vendor locking, or required some weird export dump that messed your formatting and folders up. That lead me to Markdown and Obsidian. I love it. And when I die, that shit will still be readable by any basic text editor.
Could we convert this meme to markdown?
This is the way.
Almost completely pure way of storing ideas. With this I mean that you don’t store unnecessary data such as “background should be white” or “left page margin is 1.3cm”. It’s just text. What’s important is what it says + minimal markup.
Presentation is left to the reader’s client. Do you want dark mode? Get a markdown editor/reader that supports it. Do you want serif font? Again, that’s client’s choice and not part of the document.
I wish browsers would support markdown out of the box, so you could open https://example.com/some-post.md
Old fart warning!
Presentation is left to the reader’s client. Do you want dark mode? Get a markdown editor/reader that supports it. Do you want serif font? Again, that’s client’s choice and not part of the document.
I remember when that is how the web worked. All that markup was to define the structure of the document and the client rendered it as set by the user.
Some clients were better than others. My favourite was the default browser in OS/2 Warp, which allowed me to easily set the display characteristics of every tag. The end result was that every site looked (approximately) the same, which made browsing so much nicer, in my opinion.
Then someone decided that website creation should be part of the desktop publishing class (at least at the school I taught at). The world (wide web) has never recovered.