-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📃 Iteration 36 roadmap 📃 #8017
Comments
@mlewand - Is there any more info on the |
@ejwill04 The pagination feature allows you to see where page breaks would be if the document would be exported to PDF or Word. It also respects page breaks inserted by the user with the page break feature. It's almost ready and should be released very soon - next week probably, independently from the CKEditor 5 release. So stay tuned for an update here! |
The pagination feature is now officially released: https://ckeditor.com/blog/How-to-create-ready-to-print-documents-with-page-structure-in-WYSIWYG-editor---CKEditor-5-pagination-feature/ See the documentation here: https://ckeditor.com/docs/ckeditor5/latest/features/pagination.html |
The release has been published on npm and GitHub yesterday 🎉 Social followup of the release will be handled next week. Be sure to subscribe next iteration roadmap for updates on the upcoming release. |
This post outlines our targets for the upcoming iteration. The goal is to provide a summary of where we are going.
In this iteration we plan to focus on paying some development debt and bug fixes. That being said we still plan to include a few improvements.
New features / enhancements
Bug fixes
Finally, there are some more bug fixes and minor improvements planned for the 36th iteration. See the list of issues assigned to the current iteration for more details.
Dates
The code freeze is planned on September the 24th, followed by releasing npm packages on September the 30th.
Please keep in mind that these plans are subject to change and even though we put all our energy to deliver all the items mentioned above, the iteration plan may change at any point.
The text was updated successfully, but these errors were encountered: