🇺🇸United States @jldust

jldust → made their first commit to this issue’s fork.

This has been merged in and will be include in the next tagged release.

Thanks for a great meeting all, closing this issue.

jldust → created an issue.

Great job! This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been addressed in issue 3495195 → . Marking this completed.

This has been addressed in issue 3495195 → . Marking this completed.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This needs some additional review.

This has been merged in and will be included in the next tagged release.

Great meeting all, marking this closed.

jldust → created an issue. See original summary → .

Fantastic work, thanks for putting this together. This has been merged in and will be included in the next tagged release.

jldust → made their first commit to this issue’s fork.

This has been merged in and will be included in the next tagged release.

jldust → created an issue.

This has been merged in and will be included in the next tagged release.

jldust → created an issue.

This has been merged and will be included in the next tagged release.

We intentionally leave the container full width for developers to adjust and control as they see fit on a per theme basis.

jldust → created an issue.

Marking this fixed with the most recent tagged relase.

jldust → created an issue.

@pixelwhip → Please review this update and the function changes, currently we are just suppressing the JS API warning.

jldust → created an issue.

This has been merged in and will be included in the next tagged release.

jldust → created an issue.

We had a working meeting getting the component updates pulled in.

jldust → made their first commit to this issue’s fork.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

Looks great! This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

This has been merged and will be included in the next tagged release.

This has been merged in and will be included in the next tagged release.

Thanks for your help and for opening an MR, this has been merged into the 5.x branch and will be included in the next tagged release.

jldust → created an issue.

Closing this in favor of component specific tickets to keep this scoped better.

The current blockers for stable are updating our changelong & project readme in addition we have decided to standardize our prop names within components.

Remaining tasks

• Clean up codebase & formating

We have decided to move away from supporting a mixin and instead will leverage utility classes by adding buttons.scss to 01-elements In addition we will duplicate styles for inputs into forms.scss

We have determined this as a blocker for our stable release.

We have determined this as a blocker for our stable release.

We have decided to postpone this development, with the update to build tools this past year this is not an immediate need.

We have decided to remove component prefixes on prop names and have created dedicated issues to address this change.

jldust → created an issue.

jldust → created an issue.

jldust → created an issue.

jldust → created an issue.