When to start new project within established one?

[ccardimon]

I am taking meeting minutes and converting them to a Flare project. Now I'm attending another meeting during which I will be taking minutes, too. Should I start a new project for the new meeting minutes within the established project, or should I create a new project altogether?

[GregStenhouse]

Same project (pros): you can easily reuse styles, master pages, skins etc.
(cons): you have to use conditions to exclude irrelevant content.

My 2c - the pros outweigh the slight overhead of topic or folder conditions, so I would definitely use the same project.

Cheers
Greg

[ccardimon]

Thanks for the input, Greg.

[Nita Beck]

Why not create a global project to hold a common stylesheet, common content, etc., turn the original meeting notes project into a child project that pulls in the global stuff, and create a second child meeting note project for the new meeting? This approach still gets you all the advantages of reusing common stuff, but eliminates the overhead of conditions. And if you ever start taking notes for a third meeting, just create another child project. Furthermore, another person (who knows Flare of course) could be responsible for one of the child projects, and you wouldn't be setting yourself up as the defacto recordkeeper for all meetings forevermore.

This seems to me to be a very clean and easily managed approach.