DTC 07-23-2024

[belsrc]

Determine Structure of Meeting Going Forward

Note

Current cadence/structure is fine. Right now capturing random questions and making those the bullet points for the next meeting.
Maybe start using the github issues as a way to manager longer running questions and issues. So that its linked to work and one person doesn't have to maintain them on their side. Or use the Github wiki setup.
Or discussions

Priority of Items to Move to DevToolkit

(Using the existing Excalidraw work as a jumping off point)

Note

• Need to go through utils and pick out the ones that are truly agnostic.
• Domain base: geospatial, math and validators as an example. Transformer/Converters ??
• Smaller surface area might be beneficial. Smaller Single Responsibility chunks
• Feature-like packages. Arrow deck.gl layers.
• Could stub in folder structure to get an idea of what we really want to bring over. And list out what peer deps we want (below). Also a quick audit of the current peer deps and see if there is a better option.
• Make note for when we use something as a peer-dep. That way it is informed that the user has access to them via peer dep.
• Are we going to make the note that we are ESM only?
• Is there things that we want to split apart the design system like react aria does? Expectation is that we will be pretty tightly focused on delivery of components. Maybe icon package would be a separate thing.

Solidify Documentation Approach

Note

RAN A LITTLE SHORT ON THIS ONE AS TIME RAN OUT
Ladle has consistent URLs with params. Could embed iframes of ladle into docs.
runkit + codemirror seems like a good fit for the utils related things.
There might be a case for multiple domains for the things like the repo docs and for things like on-boarding docs, best practices.
It is unlikely that we want those things accessible to the "outside" world
Possible frameworks: starlight , docusaurus, fumadocs

HOMEWORK

Start a branch off of the standard-toolkit repo and start stubbing in folder structures. To be PR'd/discussed in the next meeting.