Amaze UI is an open-sourced responsive front-end framework.
Amaze UI believes in Mobile First. Beginning with mobile phone screens, Amaze UI is extending the adaption to larger screens such as tablet and PC.
Amaze UI contains almost 20 CSS components, 10 JS components and 17 other web components which include 60 different themes. All these components are designed to help you develop more efficiently and create responsive pages with awesome user interface and excellent user experience.
Compared with existing front-end frameworks, Amaze UI focuses on optimizing page layout in Chinese by adjusting font to different operating systems automatically. Amaze UI provides better compatibility for currently popular browsers and browsers built in Apps, saving you a lot of time for compatibility debugging.
Amaze UI puts a lot of efforts on performance. Using CSS 3 for animation makes it more interactive, smooth, efficient and suitable for mobile devices, and allows your web app to load fast.
Users can download packed templates from the Amaze UI official site.
All documents are saved in the directory of
docs/. To view the demo more conveniently, we suggest you check the documents by visiting the official website.
Developers can build extensions on top of Amaze UI.
Amaze UI use gulp.js to build files。
The following shows the steps:
npm install -g gulp git clone https://github.com/allmobilize/amazeui.git npm install gulp
You are welcome to submit bug report to the Amaze UI team.
To explain your problems clearly, we suggest that you provide a demonstration when you give us feedback.
The following links are pages we have built with online debugging tools, using Amaze UI layouts and scripts. You can fork and send a bug report, linking to example pages.
User can submit your requests through Issue system or leave us message on our official website. Any request that match our product concepts will be considered.
You are welcome to join our debugging team! You are also very welcome to share the Web components you explored by “Fork” this item and submit request afterwards.
All the development documents are saved in the directory of
docs/rules. You can also check those documents on our official website.
There might be some missing and we will keep updating.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.