Does separating content into separate Flare projects ever make sense? (A webinar I watched recommended putting all files in the same project; I'm wondering if there are times when this would/would not apply).
Our company has three separate brands (each brand has a completely separate dealer audience) and very little shared content, and I'm wondering whether we need to separate content into separate projects or not.
To make a better decision about how to chunk my content, how are the following things affected when content "lives" in several projects as opposed to a single project?
• Search results. If search results for different brands shouldn’t mix, would it make sense to separate that content into separate projects? How does MCFlare’s built in search work across projects?
• Separate landing pages. We need the ability to separate content for each of our Brand's dealer portals (so that each portal displays relevant content). Can we do that without creating a new project?
• Build times. My understanding is that the smallest unit you can build in Flare is a project. Is that correct? Do large projects (with 100s and 1000s of files) take a long time to build (over an hour)?
• Cross reference links. Cross reference links don’t automatically update if you try to link across projects, right?
• Keeping track of files. We have several writers, and we'll need a convention for organizing our file structure. I've seen several posts about using naming conventions to make files easier to find; is this a reason for separating content into separate projects?
Are there any other pros and cons to consider when making decisions about lumping content into a single project or not?
Thanks so much for your help!