-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Road to 1.0 -- 1.0 Must-Haves #687
Comments
Basically almost every part of UI needs more detailed work and testing. From styling, to behavior, keyboard navigation etc etc. Also, you keep on adding target workspace selector. :) What's wrong with the current implementation? |
I'm closing this meta-issue, as 1.0.0 is released! |
In this post, I am trying to sketch out the Road to Neos React UI 1.0.0, give estimates, and try to collect everything together.
Definition: Must Have for 1.0.0
How do we decide whether a feature is must-have or not for 1.0.0? Especially for 1.0.0 releases, we often try to cram as much as possible in. That's why for the React UI, we apply the following guidelines.
Issues are a must-have for 1.0.0, iff:
Issues are NO must-have for 1.0.0, if:
Main Areas of Work
The following areas are the main areas where work is still needed.
Each point links to the respective issue; where a concept for the
corresponding component is explained:
to validate / retest
If you want to help, you can pick one of these bugs, try to reproduce it, and add some comments/screenshots.
Confirmed Bugs
These bugs don't carry big conceptual TODOs; they can just be solved.
If you want to help, pick one of these bugs, and try to fix it.
Dimension Handling
Rich Text Editor
General UI
Done, Reviewed, Merged
<p></p>
in placeholdersdiv
(e.g. span) cause an infinite loop in CKeditor #668: Editables with tagName other thandiv
(e.g. span) cause an infinite loop in CKeditor (Difficult!)Meta: Issue Management Methodology
to the React Rewrite 1.0.0 release.
have a link back on top like <- must-have for 1.0.0
This embeds the full diagram source code into the URL, making it self-contained in the issue.
The text was updated successfully, but these errors were encountered: