Great concept, but if it’s limited to static screengrabs it’s unfortunately not worth much to UX engineers. Take Nicelydone’s “Accordion” page for example http

Great concept, but if it’s limited to static screengrabs it’s unfortunately not worth much to UX engineers. Take Nicelydone’s “Accordion” page for example https://nicelydone.club/components/accordion https://nicelydone.club/components/accordion Compare it to a couple of component library pages for accordions, Ant Design https://ant.design/components/collapse https://ant.design/components/collapse Hope UI https://hope-ui.com/docs/data-display/accordion https://hope-ui.com/docs/data-display/accordion Tailwind Elements https://tailwind-elements.com/docs/standard/components/accordion/ https://tailwind-elements.com/docs/standard/components/accor... They all have interactivity, you can play around with how it feels to use the element. That is critical. Ideally you would embed their element directly on the page (IANAL but for publicly served webpages there should be no issue with reproducing their html and css for the element in question as long as there’s clear attribution, an element library is very clearly not attempting to misrepresent itself as the website). At the very least, clicking the image should take you to an instance of the UI element on their site, or as close as feasibly possible to one.