Same Content, New Design - Best Practices

This forum is for all Flare issues related to using Source Control.
Post Reply
kwag_myers
Propellus Maximus
Posts: 810
Joined: Wed Jul 25, 2012 11:36 am
Location: Ann Arbor, MI

Same Content, New Design - Best Practices

Post by kwag_myers »

For the first time in my career, I'm working with a Design Team. Why a company would not want the Help to look like the application it's supporting is beyond me, but the money's good. Anyway, this Design Team gets a new inspiration about the time I finish implementing the last inspiration. My question is, with source control (and in this case GitHub), what is the best way to implement these changes. I feel like I need to create a new project for each design change, then import the content files. But then how do I get this new project into the repository, say as a branch?

I should also mention that this involves a suite of products and I'm not using Flare's integration. My current process attempts have been to create a project template of the new design, and do the following:

1. Branch in Github.
2. Clone branch to hard drive.
3. Deleted all Flare files.
4. Create new Flare project in local repository.
5. Import content.
6. Upload to branch.

Is there a better way?
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard
Post Reply