# Framework Presentation Guidelines

Just a guide, use any or none of these.
At least do #9

Things to consider when vetting frameworks.
We care about:

- **how are the docs???**
- is there an abundance of resources, support and active contributors?
- what we can do with it (or is made much easier by it)?
- what we cannot do with it (or is harder than not using it)?
- how to set up a project (easy > cumbersome)
- organization of code (for maintainability)

1. Is this a server side or client side framework?
2. Elevator Pitch (what is this framework in 15 seconds)
3. Who are some competitors (that do the same, similar thing)?
4. List the Features that are highlighted in your research (even if you don't know what it means).
5. Have you identified any recognizable patterns? (OOP, data-binding, monad, event handling, callbacks, promises)
6. Go over how to set up the framework
7. Sample app or demonstration of using this framework (can be yours, or online demos)
8. Sample code, show things that you like, don't like, and don't get.
9. When would you use this? Why?
10. Your experience researching and testing
11. List of good resources that others can use