The <Main> option is used to configure the file and folder paths needed by Gigatrees. File and folder paths may be entered as absolute or relative paths. Relative paths are relative to the folder where the application file ( gigatree5.exe ) resides, called the working directory. Examples of an absolute file path are c:\folder\file.ext and http://domain.com/folder/file.ext. Examples of a relative file path are folder\file.ext and ..\folder\file.ext.


In the following example, the GEDCOM file and the output path are both located in the working directory.

  <GedcomFile> export.ged </GedcomFile>
  <OutputPath> web        </OutputPath>
  <UseFolders> true       </UseFolders>
  <HomePerson> I1         </HomePerson>


[ ]
Expects an absolute or relative file path. When no file is provided, a standalone blog or gallery will be created. See blogging for more information on creating a standalone blog using configuration files. See gallery for more information on creating a standalone photo gallery using configuration files.
[ ]
Expects an absolute or relative file path.
[ ]
Normally Gigatrees uses a predefined folder structure to save the files. When disabled, all files will be saved into the output folder and filenames will be prepended with the folder name and a dash (i.e. profiles-i1.html).
[ ]
You can set this to the record id or unique name of a selected individual (generally yourself). When left blank, the first individual found in the GEDCOM file will be assigned to the home person. The Tree item in the menu will link the pedigree chart of the home person. The home person will also be used to create a default ancestor list, collection list, census table, ancestor maps, and origin maps, but only when no other id has been configured for those pages, and when those pages have not been otherwise disabled either manually by you, or automatically due to other configuration limitations, such as having no collections defined, census events or missing a Google Map API key.