What about auto detection of tags like p/button?

[Code-Dict]

Please tell me, is it possible to make the plugin automatically detect tags like p/button? So far I see endless divs. Using Tailwind (HTML) transformation. Thank you in advance!

[bernaferrari]

The issue is, what is a button? Maybe with the new figma website, it would be possible, but figma has no button api. If you tell me what makes a button a button, sure, I can get that working.

…

On Sat, Jul 5, 2025, 08:47 CodeDict ***@***.***> wrote: Please tell me, is it possible to make the plugin automatically detect tags like p/button? So far I see endless divs. Using Tailwind (HTML) transformation. Thank you in advance! — Reply to this email directly, view it on GitHub <#226>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACVXFLBOCNEW6RB3G7YG2D3G63ODAVCNFSM6AAAAACA24X6FGVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGUZTQOJWG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Code-Dict]

For example, by the name of the layer, containing "button" (translating the name to lower case). Similarly, you can highlight the tags header, nav, main, section, article, footer and others.

Or you can even apply these tags only if the layer name begins with "them" (by case). This would be simple and convenient. And also bring the design to better and more neat (systematized) naming.

I'm interested in such functionality (and I think I'm not the only one). So, I would greatly appreciate it if the plugin received such changes (at least for HTML/Tailwind, as I'm not familiar with the rest).

I can offer assistance in creating a list of tags that will be prioritized over divs in a similar manner. Additionally, I can provide assistance in creating trigger phrases in the layer name for these tags.

[Code-Dict]

Moreover, defining, for example, header, main, and footer, in addition to improving the synsemantics of the generated HTML, would also open up an interesting opportunity for out-of-the-box adaptability, namely, they could be "attached" (as is often done) to the top/bottom of the page (and between them, respectively). Even through the same Flexbox.

And I'm sure this is just an example of the many new possibilities.