Comment and post text fields default to “LessWrong Docs [beta]” for me, I assume because I have “Opt into experimental features” checked in my user settings. I wonder if the “Activate Markdown Editor” setting should take precedence?—no one who prefers Markdown over the Draft.js WYSIWYG editor is going to switch because our WYSIWYG editor is just that much better, right? (Why are you guys writing an editor, anyway? Like, it looks fun, but I don’t understand why you’d do it other than, “It looks fun!”)
Just to clarify, I wouldn’t really say that “we are building our own editor”. We are just customizing the CKEditor 5 framework. It is definitely a bunch of work, but we aren’t touching any low-level abstractions (and we’ve spent overall more time than that trying to fix bugs and inconsistencies in the current editor framework we are using, so hopefully it will save us time in the long-run).
Ah, yeah that makes sense, just an oversight. I’ll try to fix that next week.
We’re using CkEditor5 as a base to build some new features. There are a number of reasons for this (in the immediate future, it means you can finally have tables), but the most important (later on down the line) reason is that it provides Google Docs style collaborative editing. In addition to being a generally nice set of features for coauthors, I’m hoping that it dovetails significantly with the LW 2019 review in December, allowing people to suggest changes for nominated posts.
Comment and post text fields default to “LessWrong Docs [beta]” for me, I assume because I have “Opt into experimental features” checked in my user settings. I wonder if the “Activate Markdown Editor” setting should take precedence?—no one who prefers Markdown over the Draft.js WYSIWYG editor is going to switch because our WYSIWYG editor is just that much better, right? (Why are you guys writing an editor, anyway? Like, it looks fun, but I don’t understand why you’d do it other than, “It looks fun!”)
Just to clarify, I wouldn’t really say that “we are building our own editor”. We are just customizing the CKEditor 5 framework. It is definitely a bunch of work, but we aren’t touching any low-level abstractions (and we’ve spent overall more time than that trying to fix bugs and inconsistencies in the current editor framework we are using, so hopefully it will save us time in the long-run).
Ah, yeah that makes sense, just an oversight. I’ll try to fix that next week.
We’re using CkEditor5 as a base to build some new features. There are a number of reasons for this (in the immediate future, it means you can finally have tables), but the most important (later on down the line) reason is that it provides Google Docs style collaborative editing. In addition to being a generally nice set of features for coauthors, I’m hoping that it dovetails significantly with the LW 2019 review in December, allowing people to suggest changes for nominated posts.