just silently shipped markdown h1, h2,h3 support in cards (use with # text)
This uses the font (recoleta) from the about/help pages. Overall in a space with both h1s and h2s this adds 80kb which isn’t the best but no way around that with current technology, and I think it’s a net win (especially because it caches between reloads).
as always, let me know how it goes
love this
This small addition is going to bring an explosion of expression. This typeface is much more readable, and I will def be using that when dealing with longer prose passages. Look how beautiful this is:
I can’t wait to see how others use these headers…people have been asking for a while 
I found two classes of bugs. The first is that tags are not in the font, nor any characters after the tag:
I would love for tags in headers to also use recoleta. Especially if you have a tag between other text, I’d think you’d have to, unless you didn’t allow tags at all 
Secondly, no other formatting works in headers:
According to gruber’s dingus and the GitHub one I found, the formatting “should” be there. For example
# Hello [world](kinopio.club) should become <h1>Hello <a href="kinopio.club">world</a></h1>.
et cetera.
cheers!
The kinopio markdown parser is custom , it’s much faster but also isn’t deeply recursive. So not supporting code blocks in an h1 is just gonna have to be a known limitation for now.
Will think about h1 in tags but the special sizing complicates a lot
Re h1 after a tag. The ‘#’ for the h1 has to be the first character in the line
That’s not exactly what I was saying. I meant, if you have a tag in a header line, all the text after the tag is not styled properly.
# h1 [[line]] no longer h1
Setting aside tag rendering, I would expect “h1” and “no longer h1” to all be recoleta. but it’s not:
It’s not just code blocks, but any kind of formatting (bold, italics, links, strikethrough). But I understand the limitation, and I’m okay with it.
Maybe for now, tags shouldn’t be activated in headers at all so that the formatting is not weird. In other words:
instead of
Until you decide to do otherwise?
I get the logic but I think typing [[ in some contexts not generating tags would be net confusing. Irl I wonder how many ppl want to put tags in the middle of a header. Certainly it’s not something I’ve seen ppl often do on other platforms w md
Yeah, it’s not common on other platforms, and maybe not here either. Although since tags are one way you can emphasize text, I think it might be slightly more common.
The main thing I wanted to avoid is this:
which looks really bad. Maybe people will see that and then remove the tag so it’s not something to prevent?
Firstly, I love it! As you may remember, I love the usage of this font on the help page.
Secondly, I have a beef with Azure DevOps wiki editor because when you embed inline code in a heading, it does this (makes the inline code tiny compared to the heading):
So I tested the similar thing in Kinopio and you got away with it by ignoring backticks in headings:
And I’m happy with this! 
I think, all respect to Ben, tags in headings are probably more niche?
I think so too
maybe when this gets implemented.
Agreed. Still would it be possible to not allow this?
And instead,
Ideally , but I think the work to benefit ratio doesn’t justify it at this pt (it’s a surprising amt of work based on how the parser works )
