Considering I had to teach myself markdown AND HTML to post on this site, I don’t really care what they use, but it would be nice if they stuck to one.
Odd question, but how would one go about getting access to the source of LessWrong, and/or submitting proposed changes? I’ve seen a few feature request, and I’d expect it’s probably within my skill range, or reasonably learnable.
how would one go about getting access to the source of LessWrong,
I just followed my general protocol for such matters. I googled ‘lesswrong source code’ and saw it as a publicly accessible project on github. If you fork the repository and commit changes I believe you can issue a ‘pull request’.
I would also suggest creating a thread in the discussion section describing your newly implemented feature so that people can express their enthusiasm. If people particularly approve I expect it would be easier to get someone to take a look at your implementation.
… >_<
It needs a notice: “THIS EDITOR DOES NOT USE MARKDOWN.” Or, better, it needs to have a markdown mode.
Yes!
I’d love it if the editor also used markdown.
Considering I had to teach myself markdown AND HTML to post on this site, I don’t really care what they use, but it would be nice if they stuck to one.
I suspect this is in the class of problems that require someone annoyed by it to sit down and code the fix.
Odd question, but how would one go about getting access to the source of LessWrong, and/or submitting proposed changes? I’ve seen a few feature request, and I’d expect it’s probably within my skill range, or reasonably learnable.
I just followed my general protocol for such matters. I googled ‘lesswrong source code’ and saw it as a publicly accessible project on github. If you fork the repository and commit changes I believe you can issue a ‘pull request’.
I would also suggest creating a thread in the discussion section describing your newly implemented feature so that people can express their enthusiasm. If people particularly approve I expect it would be easier to get someone to take a look at your implementation.
See the last paragraph of About Less Wrong.