This is a known issue and I'm working on it! I'll try to push a "responsive" version today or tomorrow.