web-components-sandbox VS localize

In October, I have a chance to contribute to Hacktoberfest, this is my first time ever joining to other's source code. Finding a first issue to work on might take me a few days. I finally comes up with this issue for my beginning.

, , , , , , … Enter fullscreen mode Exit fullscreen mode When developing more complex components, you need to use a set of simpler ones. Like primitive components, more complex components can have 2 versions. It’s not necessary to create a wrapper component: if you can wrap only a declarative template from simpler components into a standard component (without code to manage it). And then you can just use the inner content when customization is needed. In theory, everything is fine. How are things in practice? You can see this right now in the example of the localization widget. There are tabs, switching between you can see the difference. Sources: Github. Also, I am currently preparing a smaller project for publication and it is fully Open Source. There you can clearly see all the advantages of CDD. The project will be extremely useful for those who often work with complex and custom HTML forms with dynamic fields and validations. I would like to talk about it in more detail, but this is a topic for another article. In conclusion, I would like to recall the project of customizable mobile phones Project Ara. Using this example, you can see that not everyone and not always needs customization. And few people want to overpay for the possibility of customization. But the few who really need customization are willing to experiment and try different approaches to get exactly the result that meets their expectations. I will be glad to read your comments and opinions on this technique and feel free to write me a personal message. Thank you!

Uni Localization is an Open Source project under the MIT license. And if, for example, you need additional country flags, then you can add them yourself to the @uiwebkit/flags repository.