pharos
pharos copied to clipboard
ithaka
JSTOR's design system
**This change:** (check at least one) - [x] Adds a new feature - [ ] Fixes a bug - [ ] Improves maintainability - [ ] Improves documentation - [...
**This change:** (check at least one) - [ ] Adds a new feature - [ ] Fixes a bug - [ ] Improves maintainability - [x] Improves documentation - [...
**The problem** On mobile screens, tab controls can be challenging. Stacking may push content off the screen, and hiding them in a menu might create the need to tap a...
**The problem** It takes a lot of keyboard tabs to get through an image card which can be very frustrating when navigating the site. On the image search results: 1....
**The problem** I am frustrated with how the sidenav component tries to control its own state when not knowing the context in which a user will be using it. It...
**Expected behavior** Focus is not lost when the contents of a button are updated **Actual behavior** Focus is lost and sent to the document body **Steps to reproduce the issue**...
**The problem** We want the DX and the consumer experience for Pharos to be as fast and cheap as possible. **The solution** Enabling story store v7 and babel v7 will...
**The problem** Type safety is generally a productivity tool to aid in writing new code and avoiding regressions in existing code. Storybook is compatible with TypeScript and it would be...
**The problem** In a non-Webpack context such as Rollup/Vite/esbuild, it can be quite difficult to get the pathing working properly so that [the code that resolves icon](https://github.com/ithaka/pharos/blob/develop/packages/pharos/src/components/icon/pharos-icon.ts#L47) works properly, often...
**The problem** Webpack 5 module federation dependency sharing works best with imports from a package's root entry file. Currently to share Pharos, folks would need to list the individual components...
