For example, the actual post was saved as BBCode in the database. This meant that the post had to be converted into BBCode before saving and then converted back into HTML before editing or showing the post. This lead to some frustrating due to inconsistencies with this process.
Happily, the underpinnings to our editor have now been completely rewritten to increase stability and to remove these inconsistencies. Now, the post is actually saved as cleaned HTML (via the excellent HTMLPurify) which means it does not have to be converted between states. You can still edit the BBCode manually if you wish, but this is handled by a single BBCode plug-in for CKEditor. This is very exciting because it frees up IP.Board from having to deal with BBCode manually saving hundreds of lines of code.
TL:DR version: you should see less goofy inconsistencies in the editor when working with advanced content.
We'll probably toy with this--as most threads tend to evolve over time as new issues or new iterations come out, it sometimes does and sometimes does not make sense for a post to be marked as "Answered". We'll likely roll this out on a per-forum, pilot basis--expect to see this pop up first in the Evernote Business forum.
Any questions or concerns, feel free to let me know below.