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

Ant Design Refactor #531

Closed
12 of 17 tasks
EDsCODE opened this issue Apr 9, 2020 · 3 comments
Closed
12 of 17 tasks

Ant Design Refactor #531

EDsCODE opened this issue Apr 9, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@EDsCODE
Copy link
Member

EDsCODE commented Apr 9, 2020

RE: @mariusandra's suggestion on better design system and overall UI improvements.

Why:

Posthog could use a makeover to reach parity in UI and UX with currently existing tools. At the moment, many of the components and layouts are initial renderings that we should standardize to give a more coherent experience to both developers and product owners.

How:

As suggested by Marius, Ant Design is a fully-featured and well-supported design system that has an extensive React library. They also have a full set of design elements for Figma/Sketch that can be used. We don't need to mockup elements from ground zero especially for initial parity. Ant Design will allow us to standardize the layout very quickly.

Process:

Features are being built and deployed on a daily basis therefore it's difficult to adhere to a full-length process of wireframing → mocking → interviewing → implementing. For the time being, we should modulate our process of designing to implementation. We can proceed as follows:

  1. Scope a page or component on a page that can be rebuilt with antd components
  2. Do a quick mockup of the chosen component using as much of the antd standards as possible. Match the current implemented design as much as possible and focus on complementing style from other refactored components. Emphasis on quick as the mockups don't have to be pixel perfect. Leaving negative space is ok because of possible reorientation and addition of new components. Fast drafts of alternative designs would be preferred too.
  3. Create an issue with redesign components for validation/discussion
  4. Implement

Extent:

Key Components:

Pages:

@EDsCODE EDsCODE added enhancement New feature or request Design/UX labels Apr 9, 2020
@timgl timgl added this to In progress in Parity (Roadmap phase 1) Apr 10, 2020
@timgl timgl closed this as completed Apr 13, 2020
Parity (Roadmap phase 1) automation moved this from In progress to Done Apr 13, 2020
@timgl timgl reopened this Apr 13, 2020
Parity (Roadmap phase 1) automation moved this from Done to In progress Apr 13, 2020
@SanketDG
Copy link
Contributor

Can I take up refactoring the setup page with Ant components? Do I need to open a separate tracking issue for that?

@timgl
Copy link
Collaborator

timgl commented Apr 16, 2020 via email

@EDsCODE
Copy link
Member Author

EDsCODE commented Jun 22, 2020

This is virtually done. Anything that still needs conversions are minor. Closing this

@EDsCODE EDsCODE closed this as completed Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants