Core editor

This section follows a predictable structure. For every feature, first the value for the user is outlined, then a proposed solution is detailed. The third section is arguably the most important, detailing how the current implementation deviates from the planned behavior.

When testing for bugs, it's expected to test for the current behavior rather than the planned behavior. Differences in current vs planned are usually due to resource constraints and are not considered bugs, just uncompleted work.

Last updated