` if it doesn't provide more value \nthan a simple ``.\n\n### Component dependency\nYour component should be **as _dumb_ as possible**. Complex data should always be passed via prop. \nDon't assume there will be a `router` or `store`.\n\n> Every developer wants to be in charge of his own data and state management, let them!\n\nDon't rely on external resources (CDN content or APIs).\n\n> Components that rely on external resources can not be used offline or in a local intranet.\n> Developers also cannot choose if and when an application 'goes online' and exposes data.\n\nSometimes there might be a good reason for exceptions. If you provide a component that **has** to be tightly coupled \nto an API because of the intrinsic nature of the component, it might be ok. But first ask yourself if it's possible \nto use the component with any external data source via prop.\n\n### Component composability\nReuse other components inside your component. Design yours, so that other components can reuse it and create \nricher compositions.\n\ne.g:\n\n#### good example\n```vue\n\n \n
\n \n \n \n \n
\n \n \n \n \n