Yes so for those wondering about how this is going - It’s still in the pipeline but we anticipate it’s going to take a long time before it’s production ready.
To address the concerns people have, it will be optional, and perhaps enabled by default for new users. Our current plan is to store the data in markdown format as it is right now, and the WYSIWYG editor is a pure augmentation that works on top of the markdown format.
In terms of development cycle, we developed a separate proof-of-concept to test the waters with current browser technology and it’s mostly working. The difficulty right now lies mostly on merging that into current Dynalist, all without interfering with the regular editor mode that we currently have. The other big project that affects development is a big code cleanup of the editor (which was mostly developed around 2015-2016). Given our current experience with Dynalist, there are many previous design decisions that we think could use some improvement and rethinking. This will give our new WYSIWYG editor a better base to work on, which means we won’t need to write hacky code to make it work, less chance of bugs, and easier to maintain in the future.
We’re doing this slowly and cautiously, given that we’ve seen some examples of how NOT to do WYSIWYG (see Slack). We’re also still spending a significant amount of time improving Dynalist in other ways: fixing bugs and developing other highly requested functionality unrelated to WYSIWYG. This is more of a long term project that we primarily see as making Dynalist more friendly to users (especially new users) who are less familiar with Markdown.