Per 
This would have been an example of how to create an expandable read more button that previewed any text greater than X height long. Unfortunately wikidot doesn't allow JavaScript to be run on the main wikidot website and insists on everything being run in an iframe (which is a smart move security wise). Though I could do an Ajax call to the given page and read the content into the iframe. That is a rather expensive way to retrieve information. And at that point, it would be the same amount of work to just create a whole new website specifically designed with the SCP Foundation in mind.
The closest I could come to creating an expandable preview was the following: I would use the CSS elements to track the state of the user. The user would click a button, like a checkbox or a wiki created element. Then I would use the CSS element selector to determine what state the user put the element into.
If you think I missed something that could make this work. Then here are the resources I used to get this far:
https://caniuse.com/#feat=css-has - The css class has would allow me to determine if an element has a certain property assigned to it. Allowing me to see if the collapsible element had display:none set.
https://stackoverflow.com/a/45530/3257830 - If i would have been able to use an ascending selector I could have used the wikidot collapsible element to track the state of the element to see if the child element had been set to display:none.
https://jsfiddle.net/v5jfm042/1/ - this is a working example of using pure CSS to show and hide elements. If I was able to drop in a random checkbox and label I would have been able to use this method. But wikidot prevents me from dropping in form elements.
https://www.wikidot.com/doc-data-forms:checkbox-field - the wikidot documentation says that we're able to use checkboxes, but I have yet to figure out a way to plant a checkbox down.
This is a failed checkbox
This is a fixed height blue box that would have been expanded if wikidot had implemented their website differently.
testing
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!Lorem ipsum dolor sit amet, consectetur adipisicing elit. Libero fuga facilis vel consectetur quos sapiente deleniti eveniet dolores tempore eos deserunt officia quis ab? Excepturi vero tempore minus beatae voluptatem!
This would have been a label
This is the working example of how the preview would have worked. But since this uses the HTML tag, its out the the question.
Sorting newest to oldest forum posts can be done using an ajax call, reading all the forum posts on all of the pages, indexing and caching them locally, then reading the timestamps and sorting by them. Then reintroducing them into the UI. And that is a whole lot of NOPE DONT DO THAT.
But if we do want to do that, we just have to parse the rss feed into objects and create a UI around that. Unfortunately we can't do that because the RSS feed is across another domain. Which means we'd need to have a custom phone app or chrome extension to read the wiki. We could also have the customer RSS feed give us notifications as well. Maybe a RSS SCP chrome extension is in order. That would allow users to get notifications on forum updates.
