Investigate the feasibility of the card-based UI and the reuse of cards across apps
Description
blocks
Activity
Mike Taylor July 9, 2019 at 10:18 AM
Well, the discussion of where the source-code should live seems to have stalled for now. I am going to close the present issue as complete, and open a new one for the move to a different source location as and when we reach consensus on where that should be.
Mike Taylor July 2, 2019 at 10:13 AM
Mike Taylor July 2, 2019 at 10:04 AM
Re-opened, since I want to move the cards to their own little NPM package.
I will try keeping that package in ui-rs for now: not necessarily because that's a good place for it to live, more because we want to experiment with different ways or organizing code. The key point is not where the code lives (which git repo it's in) but how it's distributed (which NPM package it's in).
Mike Taylor July 1, 2019 at 2:51 PM
I consider this research issue complete with the creation of the code at https://github.com/openlibraryenvironment/ui-rs/tree/master/src/components/cards/user and its use in the present versions of the Resource Sharing/Request/Supply trio of ReShare apps.
Mike Taylor June 18, 2019 at 2:29 PM
The display component now exists, by the way — has done for a while. See https://github.com/folio-org/stripes-components/tree/master/lib/Card
The UX prototypes for ReShare use a card-based approach to the UI, where cards show particular categories of information like an item, a user, or a library. Some cards appear in multiple apps. For example, the item card appears in the Request and Supply apps. We need to determine whether it's feasible to display these types of cards within the Stripes framework and whether it's possible to reuse the code for a card in multiple apps.