Skip to content
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

Closed
45 of 58 tasks
skurfuerst opened this issue Apr 13, 2017 · 2 comments
Closed
45 of 58 tasks

Road to 1.0 -- 1.0 Must-Haves #687

skurfuerst opened this issue Apr 13, 2017 · 2 comments

Comments

@skurfuerst
Copy link
Member

skurfuerst commented Apr 13, 2017

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:

  • they are a core feature of the old UI and haven't been ported yet, especially in the area of inspectors & content editing.
  • they are an issue appearing on many websites (e.g. if editing broke when applied on inline elements)
  • they are a performance problem for larger websites

Issues are NO must-have for 1.0.0, if:

  • they just appear anecdotically
  • there exist workarounds which are understandable to the normal editor
  • minor styling polishing

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.

Done, Reviewed, Merged

Meta: Issue Management Methodology

  • The issue Road to 1.0 -- 1.0 Must-Haves #687 is the main meta-issue tracking everything
    to the React Rewrite 1.0.0 release.
  • Every issue which is on the must-have list for 1.0.0 must
    have a link back on top like <- must-have for 1.0.0
  • All must-haves must be in the milestone must-have for 1.0.0
  • We're using Draw.io for diagrams, using "File -> Export as -> URL" and linking the resulting URL.
    This embeds the full diagram source code into the URL, making it self-contained in the issue.
@skurfuerst skurfuerst self-assigned this Apr 13, 2017
@skurfuerst skurfuerst changed the title Road to 1.0 WIP: Road to 1.0 Apr 13, 2017
@skurfuerst skurfuerst changed the title WIP: Road to 1.0 WIP: Road to 1.0 -- 1.0 Must-Haves Apr 13, 2017
@skurfuerst skurfuerst modified the milestone: 1.0.0 must haves Apr 13, 2017
@dimaip
Copy link
Contributor

dimaip commented Apr 13, 2017

Basically almost every part of UI needs more detailed work and testing. From styling, to behavior, keyboard navigation etc etc.
Content tree needs to be more synced to the canvas, e.g. scroll to focused node and scroll canvas the other way. Anyways, no need to get too detailed here, we have issues for it.

Also, you keep on adding target workspace selector. :) What's wrong with the current implementation?

@skurfuerst skurfuerst added this to the 1.0.0 must haves milestone Apr 13, 2017
@skurfuerst
Copy link
Member Author

I'm closing this meta-issue, as 1.0.0 is released!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants