Project Organizer

• Select View>Project Organizer.

OR

• Press CTRL+W on your keyboard.

Following are the primary tasks that you can perform in the Project Organizer.

• Browse sequences (add/open) If you have several topics that you think end users should read in order, you can create browse sequences. When users view the compiled online Help system, they can use your browse sequences to "browse" through topics in a particular order. See About Browse Sequences, Adding a Browse Sequence File, and Opening a Browse Sequence.
• Conditional text - tag sets (add/open) A condition tag set is used to hold condition tags you create for your project. Flare provides you with an initial condition tag set, which contains two condition tags (PrintOnly and ScreenOnly) to help get you started. You can create as many additional condition tags as you want for that condition tag set. However, if for some reason you want more condition tag sets to hold even more condition tags, you can easily add them. See Adding Condition Tag Set Files and Opening Condition Tag Sets.
• Context-sensitive Help - alias files (add/open) An alias file is used to populate a header file with the information necessary for producing context-sensitive Help (CSH). In Flare, you can open an alias file and use the Alias Editor to create and assign identifiers for the header file. See About Context-Sensitive Help, Adding Alias Files, and Opening Alias Files.
• Context-sensitive Help - header files (add/open) A header file is a simple text file that contains basic information about connecting the dialogs or windows in a software application to the corresponding topics in the Help system. Both you and the software developer need access to this file. See About Context-Sensitive Help,Adding Header Files, and Opening Header Files.
• FrameMaker - import file (add/open) A FrameMaker import file is used to import FrameMaker documents into a project. See Adding a FrameMaker Import File and Opening a FrameMaker Import File.
• Glossaries (add/open) A glossary is a feature that you can add to your output to help users understand the meaning of individual terms. See About Glossaries, Adding a Glossary File, and Opening a Glossary.
• Indexes- auto-indexes (add/open) An auto-index lets you automatically add words and phrases in your project to a generated index, rather than inserting the index markers manually. In the Project Organizer, you can add and open an auto-index phrase set. See Creating Auto-Indexes.
• Indexes- link sets (add/open) This is an index entry that links to another index entry. There are two kinds of index links: "see" and "see also." In the Project Organizer, you can add and open an index link set. See Creating Index Links.
• Publishing destinations (add/open) A publishing destination is a project file that contains the information needed for publishing output (i.e., copying the files) to another location (such as a website or a directory on your computer). See Adding Destination Files and Opening Destinations.
• Reports - Analyzer (add/open) In Flare, you can generate custom reports based on the information contained in your project. You can create reports for just about any type of information that Analyzer captures. You can also design the look and feel of reports, save them for future access, and open them in a browser window (where you can print them). See About Analyzer. Also see About Reports.
• Reports - error (open) If you save an error report at the end of the process for building a target, you can then open the report to review and address the error messages. See Opening Error Reports.
• Search - filter sets (add/open) A search filter lets users narrow their search based on concepts that you have inserted into topics. Concepts are simply keyword markers that you insert into topics that have some kind of relationship with each other. They are also used for inserting concept links into topics (such as the "See Also" link that you see at the bottom of this topic). See About Search, Adding Search Filter Sets to Projects, and Opening a Search Filter Set.
• Search - synonym files (add/open) A synonym file lets you create synonyms for terms in your project so that users are more likely to find the information they need when performing searches. See About Search, Adding Synonym Files, and Opening Synonym Files.
• Skins (add/open) A skin is a file that contains information about the appearance of the output window. See About Skins, Adding Skins to a Project, and Opening Skins.
• Tables of contents (add/open)In many cases, Flare provides you with an initial table of contents (TOC), which you further "build" (or create) using the TOC Editor. You can use this TOC (or another one) as your primary, or "master," TOC. At some point, you may decide to add another TOC to the project. The extra TOCs that you add can then be linked to the master TOC. See About Tables of Contents, Adding a Table of Contents, and Opening a Table of Contents.
• Targets (add/open) A target is one "instance" of an output type. When you build your final output, you are essentially building one or more of the targets in your project. See Adding Targets and Opening Targets.
• Variables - sets (add/open) A variable set is an element used to hold one or more variables. A variable is a pre-set term or content that you can use in your project over and over. Variables are similar to snippets. Variables are used for brief, non-formatted pieces of content (such as the name of your company's product or your company's phone number). There are different kinds of variables: (1) those you create, (2) system variables (e.g., date and time; Chapter, Section, and Volume numbers), (3) Heading variables, and (4) Running Head variables. Some of these are especially useful for page headers and footers in print-based output. See About Variables, Adding Variable Sets to Projects, and Opening a Variable Set.
• Word - import file (add/open) A Word import file is used to import Microsoft Word documents into a project. See Adding an MS Word Import File and Opening an MS Word Import File.

Button/Section	Description
	Lets you move the window pane from its docked position to another location in the interface. Simply click on this area and drag the window pane to the new location.
	Opens a drop-down menu with commands for moving and resizing the window pane. Dockable If you select the "Dockable" option, the Drag Pane button is shown or hidden accordingly. Auto Hide If you select the "Auto Hide" option, the window pane becomes "pinned" to the side of the interface so that you have more room for your workspace. You can show the window pane by hovering over the thin bar on the side of the interface. If you select this option again, the window pane returns to its previous state (no longer "pinned" to the side of the interface). Floating If you select the "Floating" option, the window pane is no longer "docked" (or "attached") to the application; instead, it becomes a free-floating element in the interface. Expand to 50% If you select the "Expand to 50%" option, the window pane enlarges to 50% of its size. If you select this option again, the window pane returns to its previous size. Send To Main Dock If you select the "Send To Main Dock" option, the window pane is moved to the main area of the interface (in other words, the central section that is normally used by Flare's various editors).
	Enlarges the window pane to 50% of its size. If you select this option again, the window pane returns to its previous size.
	"Pins" the window pane to the side of the interface so that you have more room for your workspace. You can show the window pane by hovering over the thin bar on the side of the interface. If you select this option again, the window pane returns to its previous state (no longer "pinned" to the side of the interface).
	Closes the window pane.

Button/Section	Description
	Toggles between showing or hiding the folders in the Project Organizer.
	Splits the Project Organizer into two halves. The right half shows additional details for the files. When you click a file on the right side, a red circle shows the location in the Project Organizer.
	Expands all of the folders so that you can see all of the files under each one.
	Collapses all of the folders so that you can no longer see all of the files under each one.
	Moves up one folder in the hierarchy. This button becomes enabled if you use the Split View button and select a file or folder on the right side of the split view.
	This indicates that you have the file checked out from source control. You can check in the file when you are ready. See Checking In Source Control Files and Checking Out Source Control Files.
	This indicates that you have a file in your project but have not yet added it to the integrated source control application. This might occur, for example, if you create a new topic and do not add the file to source control during the topic creation process. To resolve this, simply right-click on the file and select Source Control>Add. See Adding Files to Source Control.
	This indicates that the file is added to source control but is not currently checked out, which means that it contains a "Read Only" designation in its properties. In order to edit the file, you must check it out from source control. See Checking Out Source Control Files.
	This indicates that the file is currently checked out to another user. You can send a request to the user, asking that person to check in the file so that you can check it out. See Requesting a User to Check In Source Control Files.
	This indicates that the file is not current (i.e., the local copy of the file is older than the source control copy). This might happen, for example, if another user checks out the file, makes changes to it, and checks it back in to source control. If this occurs, you can check the file out or get the latest version of the file from source control. See Checking Out Source Control Files or Getting the Latest Version of Source Control Files.
	This indicates that the file is deleted from source control, but you still have a copy of the file on your local machine. If necessary, you can add the file to source control. See Adding Files to Source Control.
Advanced	Holds the following files after you add them to the project: alias files, auto-index phrase sets, browse sequences, header files, index link sets, search filter sets, and synonym files.
Conditional Text	Holds the condition tag sets that you add to the project. Flare provides you with an initial condition tag set called "Default."
Destinations	Holds the publishing destinations that you add to the project. Depending on the project template you select, Flare may provide you with an initial destination called "MyDestination."
Glossaries	Holds the glossaries that you add to the project. Flare provides you with an initial glossary called "MyGlossary."
Imports	Holds import files that you add to the project. This can include Flare project files, Microsoft Word files, and Adobe FrameMaker files. The Flare import files have an .flimpfl extension, the Word import files have an .flimp extension, and the FrameMaker import files have an .flimpfm extension.
Reports	Holds Analyzer reports that you create in order to track information in your project. It also holds error reports that you save after building output.
Skins	Holds the skins that you add to the project. Flare provides you with an initial skin called "Default."
Targets	Holds the targets that you add to the project. After you create a new project, you will have only one target in this folder, based on your selection in the wizard. However, you can add as many targets to a project as you need.
TOCs	Holds the tables of contents that you add to the project. Flare provides you with an initial TOC called "Master." It also contains the word "(Master)" after it. This indicates that it is the primary TOC in case you add more TOCs to the project. You can reassign the master TOC as necessary.
Variables	Holds the variable sets that you add to the project. Flare provides you with an initial variable set called "MyVariables."