In the Markdown editor, surround your text with :::spoiler at the beginning, and ::: at the end.
This (or at least my interpretation of it) seems to not work.
I read it as anywhere inline (i.e. surrounded by other text) putting :::spoiler (without the backticks), followed by your text to be spoilered, followed by ::: (no space required and again without backticks.)
That ended up producing the unspoilered text surrounded by the :::spoiler ... ::: construction and making me slightly sad. Here is a :::spoiler not really ::: spoilered example of the failure.
It seems that it has to be used as a standalone block instead, i.e. you put an empty line, :::spoiler on a line by itself, then your paragraph (probably must not include empty lines, but didn’t check), then :::.
So this works.
This should probably be clarified?
Is (or will there be) an inline form as well? Discord uses ||spoiler|| and I think I’ve seen the same in other places too.
This (or at least my interpretation of it) seems to not work.
I read it as anywhere inline (i.e. surrounded by other text) putting
:::spoiler(without the backticks), followed by your text to be spoilered, followed by:::(no space required and again without backticks.)That ended up producing the unspoilered text surrounded by the
:::spoiler ... :::construction and making me slightly sad. Here is a :::spoiler not really ::: spoilered example of the failure.It seems that it has to be used as a standalone block instead, i.e. you put an empty line,
:::spoileron a line by itself, then your paragraph (probably must not include empty lines, but didn’t check), then:::.So this works.
This should probably be clarified?
Is (or will there be) an inline form as well? Discord uses ||spoiler|| and I think I’ve seen the same in other places too.
Test spoiler:
Test
That syntax is for the Markdown editor (enabled through your user settings). For the LW Docs editor, use >! to start your paragraph.