• Taylor PalmerTaylor Palmer, over 4 years ago

    Hey Xavier,

    We've avoided this problem by having a hosted "master" prototype that a designer downloads when they need to make a new prototype. It's the most recent version of the prototype.

    Once the designer has downloaded the prototype, they can refactor and break the code as much as they want because they're working in isolation. Each of those branched prototypes is hosted in a separate folder than can all be reached at domain.com/folder/index.html.

    If one of the new prototype features gets approved and implemented, we'll move it over into the master prototype.

    This isn't the purest way to branch prototypes (obviously), but we're also dealing with designers that are less code savvy then others so they: 1. Don't have to learn git, and 2. Can't mess anything up for anyone else.

    0 points
    • Xavier BertelsXavier Bertels, over 4 years ago

      Seems like a good solution but in our case it's okay to be a bit more advanced. We're all designers but pretty tech savvy at the same time. If we see a chance and benefit to automate something, we'll do so!

      1 point