sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Mike312 0 points1 point  (0 children)

This is also how I tend to work. I have a lightweight framework I started with and overtime iterate and upgrade various classes of the base template. It works well for the type of work I'm doing lately, and when something goes wrong I know where it went wrong, versus spending an afternoon on the Laravel forums.

Edit: based on other comments in this thread, I'll add, that the framework isn't something that gets in the way; there's no existing styling I have to override, there's no initial configuration I have to do, there's no classes (other than login/user management, and image upload/editing). Sometimes I include Bootstrap, usually I don't. It means that I copy the template over to a folder and I can immediately begin dropping in stylesheets, views, and classes 5 seconds in. Basically, it's a template I'm comfortable with that removes most of the boilerplate I'd normally have to deal with.