I can't comment on all the development aspects, but I really like the idea of bringing some visualizations into Evergreen. Yes, we can do all this with external tools, but it is really nice to have a simple dashboard built in.
I also really appreciate the focus on accessibility. With that in mind, I wanted to point out something that I found confusing: the circulation summary becomes hard to interpret on small screens. There are a few issues: 1. There is no semantic html here, just divs 2. What is presumably meant to be the label (total circulation, top library, most popular format, digital adoption) is placed between the two related values it labels and is displayed in a small light colored font. The convention would be for the label to come first, and for it to be in a larger and bolder font than the content it is labeling. 3. There is no visible demarcation between the sections, so the all blend together visually on a small screen (lower down are some more data points that use the convention of putting the label in the middle, but they are less unclear because they are each in their own visual box and stay distinct at all screen sizes) My favorite part is definitely the part just above Library Performance Details. There the labels are always on top, the values are below, and it's clear that everything is month to date. It's still all divs without any semantic html, but from a visual perspective it is very clear at all screen sizes. Benjamin Kalish Cataloger / Technology Librarian Forbes Library Technical Services [email protected] 413-587-1011 Support Forbes Library: - Consider giving a gift <https://forbeslibrary.org/giving/donate-online/> to Forbes Library - Vote for the Friends of Forbes in the Florence Bank Community Grant Program <https://www.florencebank.com/vote>. - Join the Friends of Forbes today <https://forbeslibrary.org/friends/>! Currently reading: *A Memory Called Empire* by Arkady Martine For information about accessibility at the library, please see: http://forbeslibrary.org/accessibility/ On Thu, Sep 4, 2025 at 4:36 PM Scott Angel via Evergreen-dev < [email protected]> wrote: > Hey Developers! > > > I've been working on this dashboard idea (LP #1770289) and wanted some > feedback on the charting library itself. This is a custom library that uses > d3.js for generating the charts that we call eg-charts. I spent a lot of > time on the accessibility portion and I believe we should be WCAG 2.2 > compliant with features like hidden data tables for screen readers, full > keyboard navigation, visual patterns for color-blind users and ARIA labels > throughout. > > > I shopped around and looked at quite a few charting libraries including > the Visa charts listed in the LP bug. I seemed to fight with Visa charts > and just getting it to fill out the divs properly. I just could never get > them to feel like part of the page. Visa also uses d3.js. I did steal some > ideas from that library like the hidden table for screen readers to tab > through along with some visual patterns to break up the colors. > > > Second to accessibility, the next main thing I wanted out of a charting > library was the least amount of dependencies. The only dependency for this > library is d3.js itself (almost all charting libraries use d3 it seems). We > all know how troublesome it can be upgrading Angular to a newer version and > having some 3rd party dependency issues. > > > Technical Benefits: > > - CSS-first responsive design that works seamlessly with Bootstrap > > - Dynamic aspect ratios for optimal chart readability across all devices > > - Clean Angular architecture with Template Method pattern > > - TypeScript interfaces for type safety and better development experience > > - Minimal bundle size impact (just d3.js dependency) > > - Component-based architecture (line-chart, bar-chart, pie-chart > components) > > > It currently has line, bar and pie charts. Down the road we could add > scatter plots, area charts or really anything that d3 can do. > > > We have a demo here > https://egdashboard.mobiusconsortium.org/eg2/en-US/staff/sandbox > > username: admin > > password: demo123 > > > I really want the community to decide on this direction. > > Some specific questions for feedback: > > 1. Does this charting approach feel right for Evergreen's needs? > > 2. Are there specific chart types or features you'd find most valuable? > > 3. How important is the minimal dependency approach vs having more > features? > > 4. Any concerns about maintenance or long-term viability? > > 5. Should we move forward with this for the dashboard project? > > > Will this charting library work for Evergreen? Does it suck or is it > awesome? Should we try something else? Your input will help determine if we > continue developing eg-charts or explore alternatives. Please test the demo > and share your thoughts! > > > Feel free to reach out with questions or detailed feedback on this mailing > list thread or LP #1770289 for technical discussion. > > > Thanks everyone! I appreciate all your feedback. > > -- > Scott Angel - Full Stack Developer > [email protected] > _______________________________________________ > Evergreen-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Evergreen-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
