You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following markup constructs are recognized by BGG forums (those that ended up being handled are checked):
[u]underline[/u]: does not exist in GitHub Flavored Markdown, and is usually avoided so as to not confuse it with links ⇒ will not implement now.
[-]strikethrough[/-] (exists in GitHub Flavored Markdown)
[c]monospace/code[/c] (should be standard backpacks).
[o]spoiler[/o]
[color=blue]Blue text[/color] (maybe convert some standard HTML?)
Can some of them can be reasonably implemented? Ideally, any existing Markdown convention should be favored (for example that of GitHub Flavored Markup).
The text was updated successfully, but these errors were encountered:
What Markdown syntax do you propose for spoilers? I'm not aware of anything official (well, except maybe foldable callouts like in Obsidian, but BoardGameGeek's spoilers are more general).
I'd be happy to iterate with you on a Pull Request!
The following markup constructs are recognized by BGG forums (those that ended up being handled are checked):
[u]underline[/u]
: does not exist in GitHub Flavored Markdown, and is usually avoided so as to not confuse it with links ⇒ will not implement now.[-]strikethrough[/-]
(exists in GitHub Flavored Markdown)[c]monospace/code[/c]
(should be standard backpacks).[o]spoiler[/o]
[color=blue]Blue text[/color]
(maybe convert some standard HTML?)Can some of them can be reasonably implemented? Ideally, any existing Markdown convention should be favored (for example that of GitHub Flavored Markup).
The text was updated successfully, but these errors were encountered: