penpot feature: export to .html files would be great option to have

Is your feature request related to a problem? Please describe.

Currently as our UI designers are creating the projects again the Developers have to create in their own versions like HTML or Flutter or any other

Describe the solution you'd like.

As Figma already have this option, It will be a great option to have if export option is there with each board having their seperate HTML files.

Describe alternatives you've considered.

No response

Additional context

No response

Oct 31 '22 14:10 dnsoumik

Hi, this is already in our plans. We have a story (still without specifications) to which we've linked this issue.

Thanks!

Nov 02 '22 14:11 myfunnyandy

Actually this would be really neat and has a lot of potential. I imaging that the export as HTML could/should even include semantics helping developers and designers to increase accessibility. The resulting HTML should include information about the kind of an element to use a corresponding semantic HTML tag.

In my Opinion designers should be able (or even be encouraged) to choose between different the type of an element based on the wide variety of semantic HTML elements. The decision influences the generated markup in order du help developers to choose the right elment to increase the semantics of the document and help increasing the degree of accessibility.

For example:

Designers mark a Component as "Dialog": a <dialog> Element is shown in the export / source code view.
Designers changes the element to be an article: a <article> Element is shown in the export / source code view.
Designers adding a headline to the Element and defines the content underneath the element should be collapsible by changing it's type to behave like an accordion element: a <details>/<summary> Element is shown in the export / source code view.

Feb 05 '23 22:02 d-koppenhagen

Actually this would be really neat and has a lot of potential. I imaging that the export as HTML could/should even include semantics helping developers and designers to increase accessibility. The resulting HTML should include information about the kind of an element to use a corresponding semantic HTML tag.

In my Opinion designers should be able (or even be encouraged) to choose between different the type of an element based on the wide variety of semantic HTML elements. The decision influences the generated markup in order du help developers to choose the right elment to increase the semantics of the document and help increasing the degree of accessibility.

For example:

Designers mark a Component as "Dialog": a <dialog> Element is shown in the export / source code view.

Designers changes the element to be an article: a <article> Element is shown in the export / source code view.

Designers adding a headline to the Element and defines the content underneath the element should be collapsible by changing it's type to behave like an accordion element: a <details>/<summary> Element is shown in the export / source code view.

Plus in case that we would be using HTML for rendering in the browser to maintain the elements themselves, this could be the basis even also for automatic accessibility testing within the penpot tool itself (with e.g. axe or pa11y).