🚧 Planning: Iteration 3

(Side note: So far this repository was mainly used for general discussions such as about coding practices, main architectural decisions, some prototyping, etc. From now on we also want to use it for announcements and discussions about our plans, such as roadmap.)

Past Iterations

[Aug 11, 2016] Iteration 2 – Second Developer Preview (v0.2.0)

This intensive initial development period had to lead to many unclosed businesses and a lot of ideas for refactoring. Hence, in iteration 2 (v0.2.0) we were focused on the most important architecture changes and project cleanup. As a result, in iteration 3 we will be able to focus on rapid feature development.
[Jul 8, 2016] Iteration 1 – First Developer Preview (v0.1.0)

The first developer preview of CKEditor 5 was the first demo-able version. Its development took us 2 years and resulted in over 400 closed tickets and, most importantly, the creation of a powerful editing engine, editor architecture and a few basic features.

Iteration 3

We've just finished iteration 2, so it's time to discuss iteration 3.

Iteration 3 will be focused on bringing more features and stability to the exisiting ones, so the editor can be used in real projects (in limitted scope though). Also, to make it possible to actually dive into the project, we'll work on bringing the documentation to life.

Main focus points of iteration 3 are:

Bringing compatibility with more browsers. So far we're testing in Chrome only. We need to bring compatibility with at least latest versions of Safari, Firefox, Opera and Edge.
Fixing the most important issues.
Adding new basic feature: link and list.
If other things go well, start working on the clipboard feature.
Pushing forward (preferably – releasing) the work on documentation. We've got all the API docs, but no guides that would be up to date. See the summary of ideas for the CKEditor 5 documentation.

ckeditor / ckeditor5-design

🚧 Planning: Iteration 3 #157

Past Iterations

Iteration 3