Add data about each component

[samreid]

Related to #5, the style guide show this information which is not presented in the binder view at the moment:

Here is additional information from the Style Guide that we should add to the document:

• Number of published sims with component: [number]
• Sims with component (not necessarily published): [list of all sim repos]
• Published sims with component: [list of sim links]
• Published sims with element a11y enabled: [list of sim links]

@zepumph can you work on that part? You should be able to leverage the existing data for the first two bullets, and I think you referred to some metadata service that would help with the latter two.

[zepumph]

In a meeting today, it was decided to let @mbarlow12 take over this repo, here seems to be the next step in terms of content generation. Let me know if there is anything else I can do.

[terracoda]

Also discussed at the meeting was the list of generated content. It looks very similar to what @samreid posted above, with a couple of additions. I have checked off the ones that I think are already working in the prototype that @samreid created.

Name: ComboBox

• Repo: sun/js/ComboBox.js
• Number of published sims with component: [number]
• Sims with component (not necessarily published): [list of all sim repos]
• Published sims with component: [list of sim links]
• Published sims with element a11y enabled: [list of sim links]
• Snapshots of all uses on Master: [Link to Sam’s magical snapshot document at the relevant anchor]
• Instructions on how to find options in a js file.

[mbarlow12]

In Tuesday a11y meeting, it was noted that having issues that correspond to each of the common components might be useful. Each of the items below will need to present the info outlined in #6 (comment).

Some of these components will not make it into the style guide, and we're free to remove them from this issue as that becomes apparent.

General

• ABSwitch - registered
• AccordionBox - registered
• AquaRadioButton - registered
• BooleanToggleNode
• Carousel
• Checkbox - registered
• ComboBox - registered
• Dialog
• ExpandCollapseBar
• ExpandCollapseButton - registered
• FontAwesomeNode
• HSeparator
• HSlider - registered
• HSliderThumb
• HSliderTrack
• MenuItem
• NumberSpinner
• OnOffSwitch
• PageControl
• Panel
• ToggleNode
• UIComponent
• VerticalAquaRadioButtonGroup
• VerticalCheckboxGroup

Buttons

• CarouselButton
• HTMLPushButton
• NodesPushButton
• RadioButtonGroup - registered
• RadioButtonGroupMember
• RectangularButtonView
• RectangularMomentaryButton
• RectangularPushButton
• RectangularStickyToggleButton
• RectangularToggleButton
• RoundButtonView
• RoundMomentaryButton
• RoundPushButton
• RoundStickyToggleButton
• RoundToggleButton
• TextPushButton

Accessibility

• AccessibleNumberTweaker
• AccessibleSlider

[mbarlow12]

Further notes:

• when a View type is present, do we include both the button and its associated view or select one or the other?
• if the info presented is more inclusive than just accessibility, should we include the nodes in scenery/js/nodes?

[terracoda]

@mbarlow12, re #6 (comment), @zepumph had made a much shorter (perhaps more realistic list).

Also, md files are in sun, so I thought the issues for MD files would be created there. Perhaps this list is for other purposes?

There are 2 issues related to Radio Button Group (phetsims/sun#364 and phetsims/sun#361)

Should these issues be noted in the list?

[mbarlow12]

@terracoda I wanted to make an exhaustive list, and I noted in my comment

Some of these components will not make it into the style guide, and we're free to remove them from this issue as that becomes apparent.

So I do not anticipate the list to remain this length (I already removed several since this AM).

We can always link issues in commits and comments, and I agree that the issues associated with specific files/components should live in their respective directories. My hope was to have a central location to quickly track progress...and checklists are SOOO satisfying :)

[terracoda]

Ok, sounds great.