[Suggestion] Collapsed text formatting

I suggested this feature back when the boards were still in beta, but didn't receive much feedback from it.

I would appreciate a formatting option for collapsing text under a thesis statement. It would allow discussion writers to expound on details of their topic while not presenting an impenetrable wall of text for the reader -- since these boards have a clear bias towards pithy, easily digested topics.

It would also help Rioters (who are often the ones making longer, multi-point discussions) by letting them create a sort of "Table of Contents" which directly expands into the topics they wish to discuss.

Allowing nested content within the parent post would make patch notes:

Patch 5.3 "blurb about the philosophy of the larger changes in the patch" New Content Champions Items Bug Fixes Et al

Clicking on "Champions" would give you:

Azir Ahri Diana Fiddlesticks Etc.

Clicking on "Azir" would give you:

"blurb about the philosophy of the champion changes" Q - Conquering Sands: BASE DAMAGE 75/105/135/165/195 magic damage ⇒ 65/85/105/125/145 magic damage W - Arise!: SOLDIER STAB RANGE ~400 ⇒ ~325 (we're marking them as approximate values because they get very complicated) TOWER BOMB DAMAGE The tooltip values were incorrectly saying +0.6 ability power (it's actually 0.7). 90 + (15 x level) (0.7 ability power) ⇒ 50 + (10 x level) (0.4 ability power)

The patch notes would have all the same content; however, the presentation would be more crisp, giving the reader the option of what to read as it pertains to them.

The same works with player built discussions. Having nested content would allow writers talking about balance to include dense math or statistical evidence for their claims without turning off the layman reader -- whom they need to upvote in order to get rioter attention.

It doesn't (shouldn't) have any technical, storage issues, as it doesn't have to increase the number of characters usable in a post.

Something like: could work as the string to format it, though that's entirely up to whoever is coding.