Sunmao chooses a responsive solution that is easy to understand and has excellent performance, making Sunmao intuitive and quick to use.
Sunmao has a built-in GUI editor, which almost includes all the capabilities that a complete low-code editor should have.
Both the UI component library itself and the low-code editor support custom extensions. Developers can register various components to cover application requirements and continue to use the existing visual design system.
You are in type safety both when developing Sunmao components and when using the Sunmao editor. Sunmao heavily uses Typescript and JSON schema for a great type system.
Sunmao is a monorepo project that includes the following packages:
| Name | Description |
|---|---|
| core | Spec type definition of Sunmao |
| runtime | Sunmao's runtime |
| editor | Sunmao's GUI editor |
| editor-sdk | sdk for Sunmao Editor |
| shared | Types and utility functions shared by each package of the Sunmao project |
| chakra-ui-lib | chakra-ui component library packaged by Sunmao |
| arco-lib | arco-design component library packaged by Sunmao (recommend to use) |
yarn
cd packages/editor
yarn devyarn test:ciyarnWhen you run the runtime or editor locally, if you modify the code of other packages, you must rebuild the modified package, otherwise, the runtime and editor will still run the old code.
Sunmao users are divided into two roles, one is a developer and the other is a user.
The responsibilities of developers are similar to those of common front-end developers. They are responsible for developing UI components and encapsulating common UI components to Sunmao components. Developers need to write code to implement the logic of the component.
The user's responsibility is to use the Sunmao components encapsulated by developers to build front-end applications in the Sunmao low-code editor. Users do not need front-end knowledge and programming skills. They can complete application construction only through UI interaction.
We have prepared two tutorials for different roles. The user only needs to read the user's tutorial, but the developer has to read both.
MIT