If it does, then maybe we need only one branch and GP will compile static html/css for us
If it doesn't then we need at least two branches, one for source jekyll and one for compiled html/css
Based on all above we should be able to decide on a number of branches and what role each should play.
It may change later, once we start implementing, we may discover new information or better ways. But we should be one the same page about our starting idea of what branches play which roles
Two factors drive our choice of branches:
1. content separation needs
2. assessment of whether Github Pages supports all required gems
Based on all above we should be able to decide on a number of branches and what role each should play.
It may change later, once we start implementing, we may discover new information or better ways. But we should be one the same page about our starting idea of what branches play which roles