A Short Guide to Component Naming

1. Brevity is Key

Time is scarce, don't waste it typing out long, descriptive component names. One approach is to give them short, cryptic names that only you will understand.

2. Be Abstract

In order to maximize code reuse, your component names should be extremely generic. If it's a form, name it Form. If it's a button, name it Button.

3. Mix Languages

If you work remotely, it's likely you are on a global team and yet all your components have English names. This slows down your non-english colleagues considerably so you should allow them to use their native tongue when naming components.

You can create an index file that maps all the different languages within your repo. Need a dropdown? Look for 'Desplegable'. A form? Search 'Форма'. You'll learn multiple new languages while being more inclusive to your colleagues.