Hi,
A case of an emoji header href in bearblog I found curious enouh to write out for myself:
I have this post I’d like to realize, with a silly conceit. Part of the constraint in the art is, in the post, the headers are not to be composed of words!
A clever solution I find is to use emoji for headers, like this: ### ❄️🌻🩸
An issue: the href emoji headers outputs is in the key of #%E2%9D%84%EF%B8%8F-%F0%9F%8C%BB-%F0%9F%A9%B8 , for the above.
, which refuses to be resolved. A mystery! I take a few guesses at getting to know this mystery on my own:
- is the “hyphen-percent” a difficult syntax for markdown
- I escape the first
%, no dice. - I escape every
%, no dice.
- might the
<a>tag serve for a bypass (can I hardlink to the subsection)
- something injects a slash between the url and the hash symbol (resolving to the 404 that injection can be expected to output); nope:
<a href="https://example.com/page-page#%E2%9D%84%EF%B8%8F-%F0%9F%8C%BB-%F0%9F%A9%B8">body text</a>
outputs to:
<a href="https://example.com/page-page/#%E2%9D%84%EF%B8%8F-%F0%9F%8C%BB-%F0%9F%A9%B8">body text</a>
Happy with my exploration, I proceed to journal about my experience. Mirroring that journal entry here has been a pleasure.
Thanks for visiting me 
Happy posting!
update:
I have additional (fragile) details:
<h3 id=the-basket> 🧺<h3>
Where did I put it? ...Oh!
[Here it is!](#the-basket)
Using <h3> in place of ### does let ne add the id myself in bearblog with no conflict.
Bearblog seems to only generate id when markdown is employed.
Neat!