-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider renaming blocks and components #58
Comments
@pigeonfresh is the confusion still there? |
In all of my conversations with project managers, UX and design the name component is used for what we call blocks in Muban. So where as I might be used to calling them blocks in Muban I still feel like component would be a better name for blocks. |
Too bad, because among developers "everything" is a component. Same with looking at react or vue. Some are atoms (smaller things), others are molecules or organisms... or blocks, or modules. I'm fine with renaming away from components (e.g. block & element, or module & element), but component itself is too ambiguous. |
That's why 'block' seems to be a catch-all name for what could be components. |
I'd rather not use |
In the last year I've been doing a lot of introductions to Muban for people new on the team. And often I would use the wrong naming for our blocks and components. In many cases I would call our blocks components and components elements. And a lot of the people are confused about the naming too. Is this something we should reconsider and rename them?
The text was updated successfully, but these errors were encountered: