Organization of templates

[alvincrespo]

I was thinking that PR templates should be organized based on their respective code base purpose, e.g. backend, frontend, etc...

Although I supposed you could also have PR templates that might be specific to a community. For example, the elixir community might want different information in the description of a PR than the Golang community.

We're not at the point were we need to think through this, but maybe something to keep in mind.

[cball]

Totally agree. I'd like to go with a standard frontend and backend PR template regardless of the language. If/when we come to a point where we have different needs we can start making them language specific.