You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm a designer, working with a team seeking to adopt the Spectrum components library for a complex/enterprise SAAS application that's being redesigned. 90% of the experience will be desktop-only, and it's an accounting/benefits management tool that uses lots of regular tables, nested tables, editable tables, and form elements.
I've combed through the Spectrum design system's documentation, and while it's more thorough than almost any other public-facing design documentation, it remains scant in many areas—and doesn't much cover interaction patterns (yes, it has started some topical areas). Design principles, yes, but not how the Spectrum designers built the system to handle different use cases and patterns with the created components. Also some biggy questions on Fonts, that I asked in a different thread.
Our team has only one developer, who's new to front-end and is working hard to learn as quickly as possible.
I wanted to see if there's anyone here in this community, experienced working with the Spectrum components that might be available for help. @Westbrook if this could support Adobe's interests for use in a case study once it all gets built, I suspect our team would totally be open to that if it could open a door for some hand-holding.
The table is where I have the most questions, particularly around what options are available with the "Quiet" table for grouping, nested tables, and potentially for editable cells in tables.
If there are FE/freelance developers here already fluent with the Spectrum components library, we may also be open to hiring folks in a freelance capacity to extend our needs with the table. My email is ninavizz at gmail dot com, if folks might be interested in that. Thx!! :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello! I'm a designer, working with a team seeking to adopt the Spectrum components library for a complex/enterprise SAAS application that's being redesigned. 90% of the experience will be desktop-only, and it's an accounting/benefits management tool that uses lots of regular tables, nested tables, editable tables, and form elements.
I've combed through the Spectrum design system's documentation, and while it's more thorough than almost any other public-facing design documentation, it remains scant in many areas—and doesn't much cover interaction patterns (yes, it has started some topical areas). Design principles, yes, but not how the Spectrum designers built the system to handle different use cases and patterns with the created components. Also some biggy questions on Fonts, that I asked in a different thread.
Our team has only one developer, who's new to front-end and is working hard to learn as quickly as possible.
I wanted to see if there's anyone here in this community, experienced working with the Spectrum components that might be available for help. @Westbrook if this could support Adobe's interests for use in a case study once it all gets built, I suspect our team would totally be open to that if it could open a door for some hand-holding.
The table is where I have the most questions, particularly around what options are available with the "Quiet" table for grouping, nested tables, and potentially for editable cells in tables.
If there are FE/freelance developers here already fluent with the Spectrum components library, we may also be open to hiring folks in a freelance capacity to extend our needs with the table. My email is ninavizz at gmail dot com, if folks might be interested in that. Thx!! :)
Beta Was this translation helpful? Give feedback.
All reactions