Bringing more UI utilities to specs

[marcoscaceres]

Session description

When used in Editor's drafts, Respec and Bikeshed provide very powerful/useful JS controls that provide a lot o value to the community. For example, both Respec and Bikeshed allow clicking on variables in algorithms, which get highlighted to show where they are used. ReSpec adds a copy button to WebIDL, letting readers copy WebIDL with a single click, etc.

Other useful things are the definition boxes, MDN annotations, etc.

Unfortunately, these are inconsistently presented across specs/tools providing different experiences and capabilities.. as a community, we should look to align on the design of the above things, and expose these JS tools to all specs that need then.

It would be great to have a session where we look the great feature both Bikeshed and Respec provide, and see where we have overlapping features, and start looking at how we can harmonize the JS libraries into a single codebase.

It would be great if we could find a UI designer to help us make these tools even better... and, as a bonus, it would be cool if we could start using popup and other modern web features to achieve these things.

Hi @tabatkins, @sideshowbarker, @sidvishnoi, @fantasai, @dontcallmedom, @tidoust, @deniak 👋

Session goal

Shared JS libraries for spec goodies

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#we-love-specs

Other sessions where we should avoid scheduling conflicts (Optional)

#10, #11

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

• Demo what Bikeshed has
• Demo what Respec has
• Compare differences
• Talk about convergence
• Talk about other neat things we could develop that would help users
• Talk about what we can bring to TR and maybe let TR/ design handle

Links to calendar

• 2024-09-25, 16:00 - 16:45

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[tabatkins]

Nice, this would be a good discussion.