[LillyIsaacson]

You are correct, but you’re being very specific. In general, erik’s definition is very accurate: front end is what the user see’s, back end is what makes it all work.

The language(s) to use depend on the project, hosting specifications and desired audience. If you’re familiar with php, it makes sense that your back end would be done in php to generate the dynamic content, and then HTML/javascript used on the front end to show what the php had generated.

If you’re into C#, you could consider doing the back end in C#.net using Visual Studio, but you’ll need a server that has Windows in order to reliably host it (due to needing IIS/.net).

There’s really no reason to try to focus on how you can put as many languages as possible into the site. This is one of those things where typically less is more. Use what you need to accomplish the project and make those work as well as possible.