You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 6, 2024. It is now read-only.
I saw one of the feature that appsmith is that it lacks tooling to build components (A design system builder part of appsmith). I wanted to share a demo how it can be done, however I'm not able to find directions for frontend build. could you please direct me.
Alternatively I think isolating frontend from the backend will allow for more collaboration from contributors. For local development it is not necessary that appsmith needs backend, its a UI tool, use client side for persistence.
Why should this be worked on?
Appsmith has a good grip since it already has user base and developers use it. In the road map or the final place the vision could be is in the direction of design to code. There are huge solutions available for design to code, but most of them lacks the code readability of the generated content from the designs, very hard to grasp.
An alternative approach is to build a lite version of design tool, with code generation based on component architecture. A catch is that, component philosophy mentioned here scales to generate code targeting any framework that supports component based development.
Targeted user base - Designers, frontend developers
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Summary
Hi,
I saw one of the feature that appsmith is that it lacks tooling to build components (A design system builder part of appsmith). I wanted to share a demo how it can be done, however I'm not able to find directions for frontend build. could you please direct me.
Alternatively I think isolating frontend from the backend will allow for more collaboration from contributors. For local development it is not necessary that appsmith needs backend, its a UI tool, use client side for persistence.
Why should this be worked on?
Appsmith has a good grip since it already has user base and developers use it. In the road map or the final place the vision could be is in the direction of design to code. There are huge solutions available for design to code, but most of them lacks the code readability of the generated content from the designs, very hard to grasp.
An alternative approach is to build a lite version of design tool, with code generation based on component architecture. A catch is that, component philosophy mentioned here scales to generate code targeting any framework that supports component based development.
Targeted user base - Designers, frontend developers
The text was updated successfully, but these errors were encountered: