How to Design / Maintain Multiple Pages Using Resin Starter Kit

I recently started working on a set of polymer starters. I can see that index.html is being used as a site hosted at localhost: 3000. It is a single page application that handles multiple client side routes. I am trying to create a multi-page site using polymer. Pages will share some resources (toolbars, custom elements), but they are all single page applications.

You can either:

• Work and serve multiple pages on different routes from the gulp server itself. Vulcanize can embed / pack resources efficiently.
• Work on separate pages as separate projects. When deploying, I take my resources and combine manually.

The second option doesn't sound like a good idea. How can I extend the starter kit to create / maintain multiple pages.

Update

I found that the starter kit uses browser-sync which handles routing, but it is minimal. The workflow doesn't work for me (anyone who knows better please suggest). You can build an interface without routes, but when you need to take it to production, you want to integrate it with your server that has routes. Thus, integration and testing and end-to-end testing are difficult and painful.

The lack of routing hurts me more than not restarting my browser. By routing, I mean mapping a url to files on disk. I would like to control it and change routes easily. I decided to disable the browser and use the following workflow:

• Gulp to rebuild UI on file change
• Express server for routing and servicing assembly reloads on route change and above

Can anyone tell me how to integrate both.