Feasibility of combing several similar projects into one

[ccardimon]

Is it possible, and even advisable, to import several similarly themed projects into one project?

When I first began using Flare, I did a series of small tasks for IT. They all centered around one theme, but for some reason I started a new project for each task.

I was thinking about trying to combine each of these separate but related projects in one project, just to make keeping track of these easier.

Should I even attempt this, or should I let sleeping dogs lay where they are?

I ask because IT has asked me to resurrect an old task, but I really had to search to find the right project, because I have a handful of old, similarly named projects in Flare.

[ChoccieMuffin]

One potential difficulty is having topic files with the same name all in the Contents folder. If you make a separate folder in Content Explorer this prevents the problem.

[ccardimon]

One potential difficulty is having topic files with the same name all in the Contents folder. If you make a separate folder in Content Explorer this prevents the problem.

Does the import process allow for this? Or, if I proceed, would it be better for me to copy and paste instead of import?

[ChoccieMuffin]

We use global product linking quite extensively, which uses imports. The way to do it is in the SOURCE project put your topics and graphics in a named folder first, THEN import it into the target project. Your target project then contains the named folders.

I wouldn't just copy and paste because you run the risk of losing all your links - cross-refs, hyperlinks and even links to graphics.

[ccardimon]

We use global product linking quite extensively, which uses imports. The way to do it is in the SOURCE project put your topics and graphics in a named folder first, THEN import it into the target project. Your target project then contains the named folders.

I wouldn't just copy and paste because you run the risk of losing all your links - cross-refs, hyperlinks and even links to graphics.

Okay. Sounds doable.

[phebert]

Hello,

To jump on this topic, I have a similar situation and need some guidance. I currently have three separate Flare projects for applications that are almost stand-alones but are related. We will be moving to web-based help in the first quarter of 2015 and I'm wondering if I should use a global linking project or go to using a CMS. The applications are somewhat related, meaning, I use one application to create a purchase order but another to pay the vendor. Eventually there will be five web based Help projects. Again, for some clients, it's possible they would be using all five applications so Help ideally should be in one place. I am a huge fan of what Overdrive has accomplished but their webinar indicated they've got a lot more resources then I will have. I have investigated using WordPress as a CMS but I have no experience with this. I've also looked at a global linked project with a HTML5 web target. I am just at the planning stages now but don't feel I have enough experience or currently, education, to make the best decision long term. Any guidance or suggestions are greatly appreciated.

[ccardimon]

We use global product linking quite extensively, which uses imports. The way to do it is in the SOURCE project put your topics and graphics in a named folder first, THEN import it into the target project. Your target project then contains the named folders.

Move (copy?) the topics and graphics into the SAME named folder?

Or into different named folders, such as ImagesFolder and TopicsFolder?

[ChoccieMuffin]

We use global product linking quite extensively, which uses imports. The way to do it is in the SOURCE project put your topics and graphics in a named folder first, THEN import it into the target project. Your target project then contains the named folders.

Move (copy?) the topics and graphics into the SAME named folder?

Or into different named folders, such as ImagesFolder and TopicsFolder?

Imagine the following structure:
The default for the location of topics is to put them directly in the \Content folder, and to put images in the \Content\Resources\Images folder. (At least, I think that's the default.)

Rather than having a topic (for example Overview.html) sitting in the \Content folder, I have created sub-folders inside \Content, so my folder structure in the source Flare projects looks a bit like this:

\Content
\ \Module A topics
\ \Module A images

So if you have, say, two modules imported into your target project for your product, the folder structure would look a bit like this:

\Content
\ \Module A topics
\ \Module A images
\ \Module B topics
\ \Module B images

This way, you can have Overview.html in Module A and Overview.html in Module B and they can both happily exist inside their own folders.

Does that help?

[ccardimon]

Does that help?

Yes, thanks! Now I have to think this through.

[ChoccieMuffin]

When you move your files in your source project, make sure you do it inside Flare so it can update the links. Otherwise you'll be in tears.

[ccardimon]

When you move your files in your source project, make sure you do it inside Flare so it can update the links. Otherwise you'll be in tears.

If I have learned only one thing about Flare, it is to move files within its own Content Explorer. Never use Windows Explorer (unless you enjoy migraines and heartburn!).