Aaron Shekey

We don't quite support the following markup: ``` html Full Stack Developer Backend Developer ```

Stacks should support a bulletproof auto-complete component. A spec for an MVP using searching has been created. 1. [Spec](https://docs.google.com/document/d/10gEKwJffcXFX-_pwpt-hEkpU6_Rtdj7-TkUIePQXrNg/edit) 2. [Figma](https://www.figma.com/file/40Tk6s5j9nVGz9mumtC81F/Autocomplete?node-id=128%3A1429)

When using our grid spacing classes responsively, they force a horizontal scroll when wrapping. This is the smallest example that will trigger this. ``` This cell has dynamic content that...

Notices should have a corresponding stimulus component to show them as toasts with various configuration options.

I could see us splitting the typography section into more atomic groupings. Specifically, these can be their own sections: - Lists - Colors (can be moved back into the color...

We should introduce a new section to `product` that includes larger page layout patterns. We have some prior art in the [email section](https://stackoverflow.design/email/patterns/columns). For example, we can add best practice...

Now that Stacks has matured and adoption has grown, I find myself visiting the documentation _most_ for our type size. I just can't seem to internalize if something is a...

Wrap publishing into a single command

1

There are quite a few steps for publishing a new version of Stacks. We ought to consider wrapping those into a custom script that runs the proper commands for us.

An example: In our search, it can be difficult to find something like `background-color`. In our documentation, any time a class is referenced, we ought to make sure it's showing...

- [ ] Find the canonical color for icons and render them - [ ] Allow them to be downloadable in our docs