Earlier this month in Denver, we synchronously updated Vue DevUI: Vue DevUI has 10 component members ~ π₯³π
The Vue DevUI open source project soon attracted many gold diggers:
Within 3 days
There are more than100 +
Community friends to add a small assistant wechat (devui-official) to contact us, and join our core development group, very welcome to join ~ ππWithin five days
all61
Each component field has been claimed, altogether40 +
Friends become Vue DevUI component kutan ~ ππ- A new PR was submitted the next day,
Within ten days
And everyone added a new Vue DevUI11
New member ~ π₯³π₯³
The latest version of the Vue DevUI component library is currently V0.1.3
β οΈ Note: This version is not yet complete and is not available for production.
Special thanks to the contributions of the following partners ππ₯³ :
- @ half-and-half
- @devin
- @iel
- @kagol
- @LiuSuY
- @lookforwhat
- @lwl
- @mrundef
- @Roading
- @Vergil
- @~zZ.Lucky(This is the second day on the PR of the little sister
Lucky
π)
The new component
This version adds 11 components in four categories.
general
- Icon – @kagol
- Search Search box – @lwl
- Status Status – @liusuy
feedback
- Loading Prompt – @ in half
- Toast global notification – @iel
Data entry
- DatePicker Date selector – @mrundef
- Select drop down Select box – @lookforWhat
The data show
- Card Card – @Vergil
- Carousel – @roading
- Progress Progress bar – @devin
- Rate score – @~ zz.Lucky
To optimize the
- Create DevUI CLI to solve the consistency problem of component directory structure
- Refactor site rendering with VitePress
During the collaborative development process, we found two problems:
- The directory structure of components is not uniform
- Component Export File
vue-devui.ts
There’s always conflict
After discovering this problem, @iel volunteered to optimize it. After a brief communication, it was decided to solve the above two problems by creating a DevUI CLI scaffolding tool, which could:
- The first problem is solved perfectly by quickly creating a new component directory structure using the command line step guide
- Automatically create component export files and in
predev
The phase is automatically executed so that no one has to change the file and the second problem is solved
@iel also wrote an article about this process, which is great! Welcome to give him a thumbs-up support ~ π₯³
The scaffolding I developed for DevUI
@IEL’s spirit of active optimization is very commendable.
Find the problem, and actively solve the problem, so as to make the whole project better, truly make high-quality!
Participating in the open source project, I think, is not only a strong addition to our resume, but also a kind of self-improvement for us:
- Let’s learn to cooperate with others and accomplish one thing together
- Learn from other people’s good practices and experiences by reviewing their code
- Cultivate the awareness of continuous iteration and optimization, and cultivate the spirit of pursuing high-quality products
- A new understanding of self, self closed can never break through, and participation in open source can let us through collaboration with others, a new understanding of self
Here’s a look at the site:
Contribution to guide
Vue DevUI is still in the process of rapid iteration and improvement. Welcome to join us!
- Claim the component or task
- Fork repository for development
- Submit a PR
- Examine the merge
- Continue to optimize
Here is the detailed contribution guide documentation:
Contribution to guide
Contributor roster
Here is the source code for the project:
Gitee.com/devui/vue-d…
Participate in the contribution can be added to the small assistant wechat: Devui-official, pull you into the Vue Devui core members group ~ ππ
Welcome to our DevUI component library and light up our little star π :
Github.com/devcloudfe/…
Also welcome to use DevUI newly released DevUI Admin system, out of the box, 10 minutes to build a beautiful atmosphere of the background management system!
trailer
DevUI Admin 2.0 will also be released on The 17th of this month, providing a magical piece of dark technology, let’s wait and see!