| | | |
---|
15 min | File uploader | @Jon F | Notes: Use case: redesign of video block user selects a video to add to a course, select existing video, or upload a new video file uploader UI where content is customizable
Upload is current proposed name
Shouldn’t need to be full screen all the time, to make it usable for other use cases Error state with alert (e.g., issue uploading the file). Probably something we can reuse in other places Looking for feedback on: BenW: dropzone probably makes sense (Adam +1) Loading state? Momentary spinner instead of a full progress bar Right when you add that it changes to a different page to edit while video is still processing Currently only really solving for this one case
(BenW) custom elements: error text hint text active content Header confirm text on success action
Jeff on a11y: “Browse files” same functionality a drag and drop should suffice May need to clarity on outline requirements around dropzones Noticeability for low vision users Touch tablets and need to know what’s touchable “Is the entire dropzone surface area known in advance?”
Is there an affirmative action?
(Adam) How could this look like in other use cases, like inside of a modal, etc.? (Jeff) Same file upload for mobile (small viewports) vs. desktop? (Adam) Have we referred to any examples of drop zones from other design systems?
|
15 min
| Text Editor
| @Connor Haugh (Deactivated)
| |
15 min | Design Handoff process | @Ben Warzeski (Deactivated) | Working on issues with communication of designs to engineering, around design system components and responsive behavior. Notes How do we communicate designs in Figma that are based on Paragon that devs can actually replicate the designers? Increased clarity on Figma “inspect” Everything we build is responsive 2 top of mind things Content bodies (e.g. modals) that are responsive, keep figuring out from scratch how these things interact Could we create a base set of variants that define/describe most of the responsive scenarios we use?
Designers are given designs in lo-fi, but causes devs a lot of back-and-forth to align lo-fi to Paragon components. How do we handle responsive columns, etc.? Need more guidelines or just a few predefined presets. Looking for a more formalized responsive content rules. Controlled vs. non-controlled for responsive behavior Non-controlled might make more sense. “The less the dev has to tell the code how to be responsive, the better we are” How do we take arbitrary Figma widths and make it into an actual responsive app?
|
| | | |