<scripttype=application/ld+json>{"@context":"https://schema.org","@type":"BlogPosting","articleSection":"Documentation","name":"Configuration","headline":"Configuration","description":"All the configuration variables available in Congo.","inLanguage":"en-AU","author":{"@type":"Person","name":"Congo"},"creator":{"@type":"Person","name":"Congo"},"copyrightHolder":"Congo","copyrightYear":"2020","dateCreated":"2020-08-14T00:00:00\u002b00:00","datePublished":"2020-08-14T00:00:00\u002b00:00","dateModified":"2020-08-14T00:00:00\u002b00:00","url":"https:\/\/jpanther.github.io\/Congo\/docs\/configuration\/","wordCount":"989","keywords":["config","docs"]}</script>
<p>Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.</p>
<p>The theme ships with a default configuration that gets you up and running with a basic blog or static website.</p>
<blockquote>
<p>Configuration files bundled with the theme are provided in TOML format as this is the default Hugo syntax. Feel free to convert your config to YAML or JSON if you wish.</p>
</blockquote>
<p>The default theme configuration is documented in each file so you can freely adjust the settings to meet your needs.</p>
<spanclass="no-prose dark:text-gray-300">As outlined in the <ahref=../../docs/installation/#set-up-your-configuration-files>installation instructions</a>, you should adjust your theme configuration by modifying the files in the <code>config/_default/</code> folder of your Hugo project and delete the <code>config.toml</code> file in your project root.</span>
<p>Standard Hugo configuration variables are respected throughout the theme, however there are some specific things that should be configured for the best experience.</p>
<p>The site configuration is managed through the <code>config/_default/config.toml</code> file. The table below outlines all the settings that the Congo takes advantage of.</p>
<p>Note that the variable names provided in this table use dot notation to simplify the TOML data structure (ie. <code>author.name</code> refers to <code>[author] name</code>).</p>
<table>
<thead>
<tr>
<th>Name</th>
<th>Type</th>
<th>Default</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>theme</code></td>
<td>string</td>
<td><code>"congo"</code></td>
<td>This must be set to <code>"congo"</code> for the theme to function.</td>
</tr>
<tr>
<td><code>baseURL</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The URL to the root of the website.</td>
</tr>
<tr>
<td><code>languageCode</code></td>
<td>string</td>
<td><code>"en"</code></td>
<td>The language of the website for site metadata purposes. It can be a top-level language (ie. <code>"en"</code>) or a sub-variant (ie. <code>"en-AU"</code>)."</td>
</tr>
<tr>
<td><code>defaultContentLanguage</code></td>
<td>string</td>
<td><code>"en"</code></td>
<td>This value determines the language of theme components."</td>
</tr>
<tr>
<td><code>title</code></td>
<td>string</td>
<td><code>"Congo"</code></td>
<td>The title of the website. This will be displayed in the site header and footer.</td>
</tr>
<tr>
<td><code>copyright</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>A Markdown string containing the copyright message to be displayed in the site footer. If none is provided, Congo will automatically generate a copyright string using the site <code>title</code>.</td>
</tr>
<tr>
<td><code>enableEmoji</code></td>
<td>boolean</td>
<td><code>true</code></td>
<td>Whether emoji strings in content should be converted to emoji symbols.</td>
</tr>
<tr>
<td><code>enableRobotsTXT</code></td>
<td>boolean</td>
<td><code>true</code></td>
<td>When enabled a <code>robots.txt</code> file will be created in the site root that allows search engines to crawl the entire site. Set to <code>false</code> if you wish to provide your own file.</td>
</tr>
<tr>
<td><code>author.name</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The author’s name. This will be displayed in article footers, and on the homepage when the profile layout is used.</td>
</tr>
<tr>
<td><code>author.image</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>Path to the image file of the author. The image should be a 1:1 aspect ratio and placed in the site’s <code>static/</code> folder.</td>
</tr>
<tr>
<td><code>author.links</code></td>
<td>array of objects</td>
<td><em>Not set</em></td>
<td>The links to display alongside the author’s details. The config file contains example links which can simply be uncommented to enable. The order that the links are displayed is determined by the order they appear in the array. Custom links can be added by providing corresponding SVG icon assets in <code>assets/icons/</code>.</td>
</tr>
<tr>
<td><code>[permalinks]</code></td>
<td></td>
<td><em>Not set</em></td>
<td>Refer to the <ahref=https://gohugo.io/content-management/urls/#permalinks>Hugo docs</a> for permalink configuration.</td>
</tr>
<tr>
<td><code>[taxonomies]</code></td>
<td></td>
<td><em>Not set</em></td>
<td>Refer to the <ahref=https://gohugo.io/content-management/taxonomies/>Hugo docs</a> for taxonomy configuration.</td>
<p>Congo provides a large number of configuration parameters that control how the theme functions. The table below outlines every available parameter in the <code>config/_default/params.toml</code> file.</p>
<p>Many of the article defaults here can be overridden on a per article basis by specifying it in the front matter. Refer to the <ahref=../../docs/front-matter/>Front Matter</a> section for further details.</p>
<td>The layout of the homepage. Valid values are <code>page</code>, <code>profile</code> or <code>custom</code>. When set to <code>custom</code>, you must provide your own layout by creating a <code>/layouts/partials/home/custom.html</code> file. Refer to the <ahref=../../docs/homepage-layout/>Homepage Layout</a> section for more details.</td>
<td>Whether or not article dates are displayed.</td>
</tr>
<tr>
<td><code>article.dateFormat</code></td>
<td>string</td>
<td><code>"2 January 2006"</code></td>
<td>How article dates are formatted. Refer to the <ahref=https://gohugo.io/functions/format/#gos-layout-string>Hugo docs</a> for acceptable formats.</td>
</tr>
<tr>
<td><code>article.showAuthor</code></td>
<td>boolean</td>
<td><code>true</code></td>
<td>Whether or not the author box is displayed in the article footer.</td>
<td>Kinds of content that should be excluded from the generated <code>/sitemap.xml</code> file. Refer to the <ahref=https://gohugo.io/templates/section-templates/#page-kinds>Hugo docs</a> for acceptable values.</td>
</tr>
<tr>
<td><code>taxonomy.showTermCount</code></td>
<td>boolean</td>
<td><code>true</code></td>
<td>Whether or not the number of articles within a taxonomy term is displayed on the taxonomy listing.</td>
</tr>
<tr>
<td><code>fathomAnalytics.site</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The site code generated by Fathom Analytics for the website. Refer to the <ahref=#analyticshtml>Analytics docs</a> below for more details.</td>
</tr>
<tr>
<td><code>fathomAnalytics.domain</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>If using a custom domain with Fathom Analytics, provide it here to serve <code>script.js</code> from the custom domain.</td>
</tr>
<tr>
<td><code>verification.google</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The site verification string provided by Google to be included in the site metadata.</td>
</tr>
<tr>
<td><code>verification.bing</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The site verification string provided by Bing to be included in the site metadata.</td>
</tr>
<tr>
<td><code>verification.pinterest</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The site verification string provided by Pinterest to be included in the site metadata.</td>
</tr>
<tr>
<td><code>verification.yandex</code></td>
<td>string</td>
<td><em>Not set</em></td>
<td>The site verification string provided by Yandex to be included in the site metadata.</td>
