See Step 5: Building and Publishing Output. You can then distribute these files to end users. This holds files that are created when you build the final output for a Flare project. See External Resources and SharePoint Integration. You do not need to do anything with these files.
This holds files that are automatically created when you create mappings between external files and copies in your project (e.g., if you are working with external resources or SharePoint integration). Within this folder, you can create as many custom subfolders as necessary (see Creating Subfolders). These files are stored in the Content Explorer in Flare (see Content Explorer). This holds all content files (e.g., topics, images, stylesheets, snippets) in your project.
A new Analyzer folder will be created when you re-launch Flare. However, if you are experiencing issues in Flare it is sometimes useful to close your project and delete this folder in Windows. They are database files used behind the scenes when you use the analysis tool in Flare. This holds files that are automatically created with each Flare project. See Git and MadCap Central and Flare.Īlso see Adding and Editing an Ignore File. In most cases, you do not need to do anything with the. gitignore file is necessary to make sure that certain folders (e.g., Analyzer, FileSync, Output, Project/Users) are ignored when you push and pull files. The contents of this folder are updated automatically when you perform source control tasks. git folder is the local repository for a Flare project and is included when your project is bound to Git (e.g., via MadCap Central). In addition to those, you might see other folders, depending on the actions you take in your project.
#FOLDERS FACTORY ALTERNATIVE WINDOWS#
When you use Windows to view the location where you project is stored, you will always see Content and Project folders (which hold content and project files, respectively).
0 kommentar(er)
