Legend: ✅ Definitely keep 🔶 Not sure yet ❌ Likely Remove
Relevant discussions
Which existing HTML features are you unable to use?
These are features (elements, attributes, attribute values etc) that you need and are part of HTML, but due to various reasons (e.g. browser incompatibilities, limited styling, different functionality) you have to instead use custom components that recreate them.
If key-value template
Enter e.g. <foo> for entire elements, or <foo bar="yolo"> for attributes.
Answer UI wireframe (though can be if no time): If freeform list
Please enter one feature per box, and prefix any comments with the corresponding opening tag (e.g. <element> or <element foo="bar"> for attributes).
Which components do you find yourself using across 3+ projects?
If you use any component technologies (Web Components, Vue, React etc), which are the components you reach for most frequently across multiple different projects? You can just type tag names, we’ll figure it out! If a component involves child components too, you can just list the parent component name.
Answer UI wireframe (though can be if no time): If you could add 3 elements to HTML, which would you add?
(Randomized order, checkboxes become disabled after 3 have been selected, , ideally with 3 pre-expanded) 🚫 None, HTML is fine as-is Rating (e.g. 5 star rating) Do you write tools for other developers?
If your tool is on npm, that may be a good indicator for usage.
Yes, internal tools within my organization Yes, publicly released tools with a few hundred users Yes, publicly released tools with a few thousand users Yes, publicly released tools with > 1M users Any other pain points around using HTML and related technologies?