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

DISCUSSION: Possible work areas for the 1.0 release #1043

Closed
dimaip opened this issue Sep 27, 2017 · 3 comments
Closed

DISCUSSION: Possible work areas for the 1.0 release #1043

dimaip opened this issue Sep 27, 2017 · 3 comments

Comments

@dimaip
Copy link
Contributor

dimaip commented Sep 27, 2017

Decision to go into the following direction:

BUDGET (as of 16. October 2016)

  • spent: 206 h / 26 days
  • 22 days to go
    • Polish the styling. Take into account both the old UI and the various drafts that we had, e.g. awesome suggestions bug Christopher Ono. As Sebastian says, Flo can help with it. -- 3-4 Days (Flo)
    • 4 PT Sebastian - for 1&1 "specials" / extensibility examples
    • 2 PT Performance Performance optimisation of inline editing #887
    • 2 PT Keyboard Handling -> Max
    • 1 PT speed up loading of UI -> Wilhelm
    • 1 PT Max/Sebastian -- Update to React 16
    • 4 PT try out Structured Editing / Create Concept -> Sebastian Try out Structured Editing / Create Concept #1146
    • 2 PT Drag/Drop in content canvas Drag-n-Drop in content canvas #1147
    • Flo check End-user issues
    • 5 PT extra time/bugfixes as they come in / communication / post-1.0 bugfixes

Done

Won't do before 1.0

@dimaip
Copy link
Contributor Author

dimaip commented Oct 16, 2017

A few corrections:

Integrate all the editors in the creating dialog

Actually I'll do it during the Vienna sprint on personal time, since it's kind of my personal itch.

Migrate Google Analytics views

This will be done by porting data views, that's exactly what I'm doing right now.

@dfeyer
Copy link
Contributor

dfeyer commented Oct 17, 2017

As said in Slack: Some many ideas now that the UI is a thing again 😉 but please for the v1, focus on what we have, we need to have a better overview of the futur UI kit, before starting to build stuff here and here. And even without big UI improvement, we can provide a 1.0 that is really valuable for our users.

@dimaip
Copy link
Contributor Author

dimaip commented Oct 17, 2017

@dfeyer I can assure you that bug fixing and implementing missing features is our strict priority, but the "problem" is that we don't have enough bugs left, so we can afford to give some efforts to do technical implementation of some directions of development we all agree on, like structured editing 😄

Once UX guild gets together and comes up with a unified concept of visual UX improvements, we will be able to easily apply them on top of the technical foundations we are laying down now.

@dimaip dimaip closed this as completed Dec 22, 2017
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