Component library for UI elements and accompanying style guide #29
Labels
dif/medium
Prior experience is likely helpful
effort/weeks
Estimated to take multiple weeks
kind/discussion
Topical discussion; usually not changes to codebase
need/analysis
Needs further analysis before proceeding
P3
Low: Not priority right now
status/deferred
Conscious decision to pause or backlog
topic/design-front-end
Front-end implementation of UX/UI work
topic/design-ux
UX strategy, research, not solely visual design
topic/design-visual
Visual design ONLY, not part of a larger UX effort
April 2020 update
Let's use this issue as a placeholder for future work on component-izing UI elements (including documenting them, style-guide-wise) in a manner that can easily be reused by all our helper apps as well as anyone else who'd like to build on the core IPFS look and feel.
Note: this should probably end up with its living home in the IPFS UI Style Guide. See issue ipfs-inactive/ipfs-ui-style-guide#2 (closed in favor of this meta-issue).
Original issue text follows:
Over the last week, I opened some issues, PRs and a repository. All about the same thing: reusable components. And I'm opening this issue to get a central point to discuss everything about this and define priorities and goals.
So, first of all, the references:
@akrych published the first Web GUI Kit on #7 yesterday and it is amazing and there are some things I want to get clear before moving more than I've moved.
During the last week, I fixed some stuff on Desktop, but it was on the PR related to the components so this won't get merged soon, but I am proposing the following.
About IPFS Desktop
This will be the priority for now. @akrych will start drawing some wireframes for it and we can start implementing the new UI on it right after. I started using the ipfs-react-components library on the PR I created (ipfs/ipfs-desktop#596) but I'm thinking about moving the components to a directory on IPFS-Desktop or use a Git Submodule.
Why? There is an issue with Electron Forge and it is making it very hard to deploy and develop faster since I can't link the module.
Steps I suggest to do:
ipfs-react-components
components again to IPFS-Desktop repository.About IPFS Companion
Since I'm not really into IPFS Companion, I'd like to ask you what do to next here 😄 /cc @lidel
About IPFS WebUI
After having IPFS Desktop with a nice UI and UX everyone agrees with (as you said @olizilla), we can move to IPFS WebUI. I was taking a look at the OKRs we've got defined for this quarter and saw this:
It was classified with priority 4. My suggestion is to forget the PR I started (ipfs/ipfs-webui#618) and start working on
ipfs-dashboard
using the new elements and the new UI. And, when it gets finished, we can replace IPFS WebUI by IPFS Dashboard.About the Reusable Components
So, as you all probably know, I created a repository called
ipfs-react-components
and I was very happy because it was all working. But now it seems it was slowing me down a bit. My suggestions here are to:ipfs-desktop
.In the meanwhile, all the components we make should be "stupid" components, I mean, they don't need Electron's or the browser APIs to work. They receive information and they just work.
What do you all think? Let's make this clear and move forward fast. 😄 Sorry for not having this clear yet.
The text was updated successfully, but these errors were encountered: