Best practise - controllers

[eluser]stuffradio[/eluser]
I've separated my Controller files and functions to something that makes sense.

So, say you want to login, "Members/login". I'm working on my admin panel section right now. This is a module using HMVC.

I agree with Stilly and "speaking urls" in mind. Some controller names I have are Contests, Ranks, Settings. If I wanted to add a Rank, it'd be "Ranks/add" or "Settings/view".

Just try and be as user friendly as you can. You can add security using MY_Controller so people can't just guess a URL and be at a place accidentally.

I hope I didn't ramble too much, but yeah that's what I do.