Component Extending Best Practices

This probably goes hand in hand with Kyle's "[Managing App state between components](https://github.com/bitovi/training/issues/1#issuecomment-122892997)".

When creating a component, are there any best practices people follow for making their component as robust and extensible as possible.

For example, you have a grid, but you want to reuse it to build a calendar view. In order to do so, you have to pass in custom row or cell templates. How do you work with this constraint?

Another example, let's say you have a grid and need to add adjustable columns. Would you do some sort of plugin that adds functionality or do you extend the grid somehow?

Start by reading the linked discussion on managing app state between components and the examples in this issue about reusable grids, custom templates, and adjustable columns. Done would be a decided set of best practices that addresses these extension scenarios in the training material; no file or test is identified.

Written by the indexing model from the issue text.