MadCap Software Forums

I've completed my first Flare project, which involved importing a user guide from FrameMaker and setting up the WebHelp and PDF targets. My plan is to use this project as the basis for setting up a global project, so I can reuse the style sheets, skin, page layouts, and so on in other projects. The global project will also contain content that will be reused with other projects.

What I'm trying to figure out is the best way of creating my global project, and then linking the existing project to it.

Should I start by creating a new, empty project and importing the elements and topics to be shared? Or should I make a copy of the project, rename it, and delete anything that I don't I want to share?

I have several more FrameMaker books that I need to convert to Flare projects - I assume that I would then use the global project as the basis for the import.

Any advice would be appreciated.

Regards
Keith

ksoltys wrote:Or should I make a copy of the project, rename it, and delete anything that I don't I want to share?

That's what I did with mine; I had about 6 projects all using the same 'template', and wanted to use project linking so that common files (stylesheets, master pages, glossary, etc) were linked to a master project.

I made a copy of one project, and then trimmed it down to be a 'skeleton' working project. Then I set up an import file in one of my projects, and chose the files to include/exclude. Then I just copied that project import file to my other projects and repeated the import.

I've done the same as Dave.

I did too, but I do not need always everything from the global project.
So, I started thinking about how to organize and preceded all topics for a certain category.
For instance I have something with a subject 'Columns maintenance' and preceded this ones with col_
If I don't need them in a certain project, I exclude them in the import file.

Get the picture?
In fact I am saying not only to decide what to put in the global project but also how.