[review summary] one month after joining wangEditor

It has been a month since I joined the wangEditor team. Take a quick summary of what you’ve heard and thought about this month.

This article will be narrated from three aspects:

  • My original intention to join the wangEditor team
  • What you learned
  • What was produced

Why join wangEditor

First of all, I would like to introduce myself. I am in my third year of undergraduate study. From front-end SanBanFu to front-end engineering, to the community of some popular framework touched after learning, came to a bottleneck of its own area, is simply don’t know what should go on studying the (smelly shameless, I learn from drive sex is very strong, without something to learn to find something to learn, not a little idle down). I suddenly realized that my vision was a little narrow, just like a frog in a well, unable to see the outside world. I could only passively follow the trend of learning, just like a body without soul.

By chance, my friend recommended to me the wangEditor open source team (he is also a member of the team) and suggested that I join the open source team, which might help me a little. I realized that it was time to break through the bottleneck, because lack of project experience is common for many college students, and I was no exception. Therefore, WITH the attitude of learning and trying, I participated in wangEditor’s team examination.

Fortunately, I successfully passed the team examination and joined the wangEditor family. During the one month joining the team, I learned a lot of knowledge. Here I would like to thank a few people: the boss for giving me the opportunity to join the wangEditor team and for accepting some of my proposals; I would like to thank my team leader for taking care of me in this month, reviewing the code for me and putting forward many suggestions. Thank my good brother to accompany me through the first development process; Thanks to all the members of wangEditor, the conversations in fishing for fish enrich my knowledge all the time

What did I learn

Complete development process

This is the one I feel the most. After joining the wangEditor team, the first thing I have to do is to get familiar with the whole development process, which is quite novel for a “kid” who has never taken part in a project. Unlike their usual prank some toy items, want to change the change, change to the warehouse push. In fact, the real development process is much more complex and perfect. For example, our development will be divided into several processes, such as issue distribution, development self-testing, cross-testing and so on. Before pushing your code, be aware that you have any extra Commits and merge them.

All kinds of excellent technical solutions

In our team, there is a knowledge base of technical solutions, in which many predecessors have carefully investigated, summarized and deposited the technical solutions after encountering problems. Each one is a real business scenario with a good solution. Here, I learned a lot about the cutting edge of rich text editors.

Excellent software design

This has to flatter our boss, our project at the beginning seems to be built by the boss alone. The code structure is very clear and the expansibility is very strong, which is most reflected when I modify the bug/ extension function after receiving the issue. Often, only one or two lines of code need to be modified/added to complete a task. Interested partners can check our team warehouse by themselves. There are many aspects of the source code that are worth learning. For one thing, a clear code structure can give me a quick insight into the architecture design of wangEditor from a global perspective.

What did I produce

Taking knowledge from the project and giving it back as much as you can is what an open source team developer should be all about. After processing several issues, I gradually understood the source code architecture and realized the challenges facing our team project at present.

As can be seen from our team’s issue-project on Github, the issue to be assigned can never be empty, which means we have countless requirements and bugs. Of course, this is a good thing for us, because with user feedback, we can make better open source projects. The biggest problem was not that, but that our project was becoming a “monolith project” as it increased in functionality — the complexity of the code was increasing and different features were being mixed together, making the whole project harder to maintain.

To this end, the boss put forward a plug-in scheme, which divided the project into three parts: wangEditor = core + menu + plugin.

On this basis, I put forward my own plug-in ideas and actual implementation. Unlike my boss, I came up with the idea of wangEditor = core core + plugin (core + anything = everything). Besides, I simulated the entire wangEditor lifecycle chain. Finally added how to extend to support different embed schemes.

The plan was approved by the boss and other team members, and I was promised that after finishing the plug-in design, I would become one of the core members of the team from the internship.

Write in the last

WangEditor is a great open source project, which you can see is now in version V4. Star on Github and Baowan, CDN downloads millions per month. We are at the forefront of rich text editors. At present, our team is still working hard. We believe that wangEditor will become better after the plug-in is completed.

Finally, if you are interested in rich text editors and open source projects, please join us. If you’re not sure where you’re headed, joining us could be a turning point for you.

If you have any questions, you can also contact me, add my QQ or private wechat, and I will try my best to help you answer them within my ability:

  • QQ: 1272698173
  • WeChat-ID: YM_coke