Feature Requests

We have been considering creating a library of extended/composite/specialized Forge components that essentially would be a separate library from the core library that use components from the core library to build out more specialized components. Is this something others would be interested in contributing to and/or utilizing? This extended library would be great for composite components and pre-built recipes to make implementing Forge easier, while still maintaining separation from the lower-level building blocks in the core library itself.

As a developer I would like for there to be a full width parameter so that when developing for mobile web applications and progressive web apps, the buttons take full width of it's container and is easier for the end user to press. Attached a visual for reference

Buttons The current set of buttons are extensive, but somewhat confusing as there’s not much guidance of when to use which button. Propose we go with a more semantic naming of button variants to give inherent meaning and make it easier for team members when designing; removes some cognitive load. Heavily influenced by IBM Carbon, but, it makes sense. * Primary * Secondary * Tertiary * Danger * Ghost Typography Similar to buttons. Update the type system scale and specs to be more robust/flexible, but also clear in its use. Adopting a size scale using numbers, starting with 01. Bigger number = bigger size. label-01 label-02 helper-text-01 helper-text-02 body-01 body-02 body-03 body-04

Expansion panel accessibility is broken right now. There are ways to fix it, but first we need to decide what the component is actually responsible for in terms of design, accessibility, and functionality.