Hey @randy_johnson
I think a lot of it comes down to personal preference & also what you're building along with how secure you need the system to be? If it was for an enterprise setup i would suggest separate login areas and separate user tables.
What are you looking to build? As this will determine most of the answers.
On my current project i'm using the same login form for both admin & users but where they are redirected to and what they have access to is dependant on what user level they are. depending on what you go for, the middleware & the auth files will handle most of the leg work & redirection once setup to how you want it.
Interms of the actual login system, i would suggest checking out "https://scotch.io/tutorials/simple-and-easy-laravel-login-authentication".
Out of the box most of the scaffolding is done by Laravel. from there you can adjust accordingly.
Once the login system has been built, i would suggest separate views & controllers for Admin / User retrospectively as it will be a lot cleaner, easier & scalable. As a general rule of thumb, i suggest using one controller per view page otherwise it all gets a bit messy & confusing when you come back to it later.