The workflow really depends on preference. There is technically no right or wrong way to do it.
For me, I start first plan out my ideas on a trello board. Then I start off with the basic html structure, basic color scheme, and then work on most important functions to least important functions. Finally I fix for responsiveness and colors. Sometimes steps get altered but that’s my basic workflow.
On another note: browser-sync and gulp are amazing. I was using livereload for a little bit, but then it kept crashing. I figured out that livereload was no longer being updated… loool
Personally, I always start with functionality and put off design until the end. Or, I should say, first I start with the abstract, psuedocode, conceptualizing what needs to be accomplished in what order, and guessing what mechanisms might do that. Then I do a lot of JS, and the bare minimum needed of HTML, until I have the whole app working, meeting all the user stories, but completely unstyled and hideous, black and white. Then I “make it purdy.” I feel like, since I’m not planning per se to be a “designer” so much as an engineer (as far as I know right now), getting the appearance nice is of secondary concern and should claim less of my time.