diff --git a/docs/404.html b/docs/404.html index e1a14ac7..40f536aa 100644 --- a/docs/404.html +++ b/docs/404.html @@ -1,14 +1,21 @@ 404 Page not found · Blowfish - + - - + + -
↓Skip to main content
Blowfish +
Blowfish Blowfish

Page Not Found 😕

Error 404

It seems that the page you've requested does not exist.

Page Not Found 😕

Error 404

It seems that the page you've requested does not exist.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/about/index.html b/docs/about/index.html index 70518603..593fc704 100644 --- a/docs/about/index.html +++ b/docs/about/index.html @@ -1,14 +1,21 @@ About · Blowfish - + - - + + -
↓Skip to main content
Blowfish +
Blowfish Blowfish

About

0 views

I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.

I’ve worked for several years in big companies and recently decided to trade that for the opportunity of working in smaller teams. Definitely prefer the latter where one can succeed/fail faster, learn faster, and overall have a way bigger impact.

Currently, I am focused on improving the lives of developers worldwide. I’m trying to write more about my previous experiences / random thoughts and would love to gather your feedback on it. I also love to dedicate my time to helping and mentoring other PMs or people that want to get into product.

Recently I’ve also joined AWS Loft to help Startups and their founders with their product strategy.

Feel free to reach out.

Blowfish
Author
Blowfish

About

0 views

I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.

I’ve worked for several years in big companies and recently decided to trade that for the opportunity of working in smaller teams. Definitely prefer the latter where one can succeed/fail faster, learn faster, and overall have a way bigger impact.

Currently, I am focused on improving the lives of developers worldwide. I’m trying to write more about my previous experiences / random thoughts and would love to gather your feedback on it. I also love to dedicate my time to helping and mentoring other PMs or people that want to get into product.

Recently I’ve also joined AWS Loft to help Startups and their founders with their product strategy.

Feel free to reach out.

Blowfish
Author
Blowfish
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/categories/index.html b/docs/categories/index.html index 935405d3..b9f58b29 100644 --- a/docs/categories/index.html +++ b/docs/categories/index.html @@ -1,28 +1,21 @@ Categories · Blowfish - + - - + + -
↓Skip to main content
Blowfish +
Blowfish Blowfish

Categories

Categories

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/categories/index.xml b/docs/categories/index.xml index 070285a4..9d5adcf8 100644 --- a/docs/categories/index.xml +++ b/docs/categories/index.xml @@ -1 +1 @@ -Categories on Blowfishhttps://nunocoracao.github.io/blowfish/categories/Recent content in Categories on BlowfishHugo -- gohugo.ioenSun, 04 Sep 2022 00:00:00 +0000Producthttps://nunocoracao.github.io/blowfish/categories/product/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/product/Strategyhttps://nunocoracao.github.io/blowfish/categories/strategy/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/strategy/Dockerhttps://nunocoracao.github.io/blowfish/categories/docker/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/docker/Developmenthttps://nunocoracao.github.io/blowfish/categories/development/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/development/Tutorialhttps://nunocoracao.github.io/blowfish/categories/tutorial/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/tutorial/Interviewhttps://nunocoracao.github.io/blowfish/categories/interview/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/interview/Mentorshiphttps://nunocoracao.github.io/blowfish/categories/mentorship/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/categories/mentorship/ \ No newline at end of file +Categories on Blowfishhttps://nunocoracao.github.io/blowfish/categories/Recent content in Categories on BlowfishHugo -- gohugo.ioen \ No newline at end of file diff --git a/docs/docs/advanced-customisation/index.html b/docs/docs/advanced-customisation/index.html index 85488b88..55a06232 100644 --- a/docs/docs/advanced-customisation/index.html +++ b/docs/docs/advanced-customisation/index.html @@ -1,16 +1,22 @@ Advanced Customisation · Blowfish - + - - + + -
↓Skip to main content
Blowfish +
Blowfish Blowfish
  1. Documentation/

Advanced Customisation

1519 words·8 mins·0 views· -
Table of Contents

There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.

If you need further advice, post your questions on GitHub Discussions.

Hugo project structure #

Before leaping into it, first a quick note about Hugo project structure and best practices for managing your content and theme customisations.

In summary: Never directly edit the theme files. Only make customisations in your Hugo project’s sub-directories, not in the themes directory itself.

Congo is built to take advantage of all the standard Hugo practices. It is designed to allow all aspects of the theme to be customised and overriden without changing any of the core theme files. This allows for a seamless upgrade experience while giving you total control over the look and feel of your website.

In order to achieve this, you should never manually adjust any of the theme files directly. Whether you install using Hugo modules, as a git submodule or manually include the theme in your themes/ directory, you should always leave these files intact.

The correct way to adjust any theme behaviour is by overriding files using Hugo’s powerful file lookup order. In summary, the lookup order ensures any files you include in your project directory will automatically take precedence over any theme files.

For example, if you wanted to override the main article template in Congo, you can simply create your own layouts/_default/single.html file and place it in the root of your project. This file will then override the single.html from the theme without ever changing the theme itself. This works for any theme files - HTML templates, partials, shortcodes, config files, data, assets, etc.

As long as you follow this simple practice, you will always be able to update the theme (or test different theme versions) without worrying that you will lose any of your custom changes.

Colour schemes #

Congo ships with a number of colour schemes out of the box. To change the basic colour scheme, you can set the colorScheme theme parameter. Refer to the Getting Started section to learn more about the built-in schemes.

In addition to the default schemes, you can also create your own and re-style the entire website to your liking. Schemes are created by by placing a <scheme-name>.css file in the assets/css/schemes/ folder. Once the file is created, simply refer to it by name in the theme configuration.

Congo defines a three-colour palette that is used throughout the theme. The three colours are defined as neutral, primary and secondary variants, each containing ten shades of colour.

Due to the way Tailwind CSS 3.0 calculates colour values with opacity, the colours specified in the scheme need to conform to a particular format by providing the red, green and blue colour values.

:root {
+
+
+ +
  1. Documentation/

Advanced Customisation

1519 words·8 mins·0 views· +
Table of Contents

There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.

If you need further advice, post your questions on GitHub Discussions.

Hugo project structure #

Before leaping into it, first a quick note about Hugo project structure and best practices for managing your content and theme customisations.

In summary: Never directly edit the theme files. Only make customisations in your Hugo project’s sub-directories, not in the themes directory itself.

Congo is built to take advantage of all the standard Hugo practices. It is designed to allow all aspects of the theme to be customised and overriden without changing any of the core theme files. This allows for a seamless upgrade experience while giving you total control over the look and feel of your website.

In order to achieve this, you should never manually adjust any of the theme files directly. Whether you install using Hugo modules, as a git submodule or manually include the theme in your themes/ directory, you should always leave these files intact.

The correct way to adjust any theme behaviour is by overriding files using Hugo’s powerful file lookup order. In summary, the lookup order ensures any files you include in your project directory will automatically take precedence over any theme files.

For example, if you wanted to override the main article template in Congo, you can simply create your own layouts/_default/single.html file and place it in the root of your project. This file will then override the single.html from the theme without ever changing the theme itself. This works for any theme files - HTML templates, partials, shortcodes, config files, data, assets, etc.

As long as you follow this simple practice, you will always be able to update the theme (or test different theme versions) without worrying that you will lose any of your custom changes.

Colour schemes #

Congo ships with a number of colour schemes out of the box. To change the basic colour scheme, you can set the colorScheme theme parameter. Refer to the Getting Started section to learn more about the built-in schemes.

In addition to the default schemes, you can also create your own and re-style the entire website to your liking. Schemes are created by by placing a <scheme-name>.css file in the assets/css/schemes/ folder. Once the file is created, simply refer to it by name in the theme configuration.

Congo defines a three-colour palette that is used throughout the theme. The three colours are defined as neutral, primary and secondary variants, each containing ten shades of colour.

Due to the way Tailwind CSS 3.0 calculates colour values with opacity, the colours specified in the scheme need to conform to a particular format by providing the red, green and blue colour values.

:root {
   --color-primary-500: 139, 92, 246;
 }

This example defines a CSS variable for the primary-500 colour with a red value of 139, green value of 92 and blue value of 246.

Use one of the existing theme stylesheets as a template. You are free to define your own colours, but for some inspiration, check out the official Tailwind colour palette reference.

Overriding the stylesheet #

Sometimes you need to add a custom style to style your own HTML elements. Congo provides for this scenario by allowing you to override the default styles in your own CSS stylesheet. Simply create a custom.css file in your project’s assets/css/ folder.

The custom.css file will be minified by Hugo and loaded automatically after all the other theme styles which means anything in your custom file will take precedence over the defaults.

Adjusting the font size #

Changing the font size of your website is one example of overriding the default stylesheet. Congo makes this simple as it uses scaled font sizes throughout the theme which are derived from the base HTML font size. By default, Tailwind sets the default size to 12pt, but it can be changed to whatever value you prefer.

Create a custom.css file using the instructions above and add the following CSS declaration:

/* Increase the default font size */
@@ -75,4 +81,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/configuration/index.html b/docs/docs/configuration/index.html index 85ddb00e..f66e2033 100644 --- a/docs/docs/configuration/index.html +++ b/docs/docs/configuration/index.html @@ -1,20 +1,27 @@ Configuration · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Configuration

2127 words·10 mins·0 views· -
Table of Contents

Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.

The theme ships with a default configuration that gets you up and running with a basic blog or static website.

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.

The default theme configuration is documented in each file so you can freely adjust the settings to meet your needs.

As outlined in the installation instructions, you should adjust your theme configuration by modifying the files in the config/_default/ folder of your Hugo project and delete the config.toml file in your project root.

Site configuration #

Standard Hugo configuration variables are respected throughout the theme, however there are some specific things that should be configured for the best experience.

The site configuration is managed through the config/_default/config.toml file. The table below outlines all the settings that the Congo takes advantage of.

Note that the variable names provided in this table use dot notation to simplify the TOML data structure (ie. outputs.home refers to [outputs] home).

NameDefaultDescription
theme"congo"When using Hugo Modules this config value should be removed. For all other installation types, this must be set to congo for the theme to function.
baseURLNot setThe URL to the root of the website.
defaultContentLanguage"en"This value determines the default language of theme components and content. Refer to the language and i18n section below for supported language codes.
enableRobotsTXTtrueWhen enabled, a robots.txt file will be created in the site root that allows search engines to crawl the entire site. If you prefer to provide your own pre-made robots.txt, set to false and place your file in the static directory. For complete control, you may provide a custom layout to generate this file.
paginate10The number of articles listed on each page of the article listing.
summaryLength0The number of words that are used to generate the article summary when one is not provided in the front matter. A value of 0 will use the first sentence. This value has no effect when summaries are hidden.
outputs.home["HTML", "RSS", "JSON"]The output formats that are generated for the site. Congo requires HTML, RSS and JSON for all theme components to work correctly.
permalinksNot setRefer to the Hugo docs for permalink configuration.
taxonomiesNot setRefer to the Organising content section for taxonomy configuration.

Language and i18n #

Congo is optimised for full multilingual websites and theme assets are translated into several languages out of the box. The language configuration allows you to generate multiple versions of your content to provide a customised experience to your visitors in their native language.

The theme currently supports the following languages by default:

LanguageCode
🇬🇧 Englishen
🇧🇩 Bengalibn
🇨🇳 Simplified Chinese (China)zh-cn
🇹🇼 Traditional Chinese (Taiwan)zh-tw
🇫🇮 Finnishfi
🇫🇷 Frenchfr
🇩🇪 Germande
🇮🇱 Hebrewhe
🇭🇺 Hungarianhu
🇮🇹 Italianit
🇯🇵 Japaneseja
🇧🇷 Portuguese (Brazil)pt-br
🇵🇹 Portuguese (Portugal)pt-pt
🇷🇴 Romanianro
🇪🇸 Spanish (Spain)es
🇹🇷 Turkishtr

The default translations can be overridden by creating a custom file in i18n/[code].yaml that contains the translation strings. You can also use this method to add new languages. If you’d like to share a new translation with the community, please open a pull request.

Configuration #

In order to be as flexible as possible, a language configuration file needs to be created for each language on the website. By default Congo includes an English language configuration at config/_default/languages.en.toml.

The default file can be used as a template to create additional languages, or renamed if you wish to author your website in a language other than English. Simply name the file using the format languages.[language-code].toml.

Note: Ensure the defaultContentLanguage parameter in the site configuration matches the language code in your language config filename.
NameDefaultDescription
languageCode"en"The Hugo language code for this file. It can be a top-level language (ie. en) or a sub-variant (ie. en-au) and should match the language code in the filename. Hugo expects this value to always be in lowercase. For proper HTML compliance, set the isoCode parameter which is case-sensitive.
languageName"English"The name of the language.
displayName"EN"The name used when the language appears on the website.
isoCode"en"The ISO language code for HTML metadata purposes. It can be a top-level language (ie. en) or a sub-variant (ie. en-AU).
weight1The weight determines the order of languages when building multilingual sites.
rtlfalseWhether or not this is a RTL language. Set to true to reflow content from right-to-left. Congo fully supports using RTL and LTR languages at the same time and will dynamically adjust to both.
dateFormat"2 January 2006"How dates are formatted in this language. Refer to the Hugo docs for acceptable formats.
title"Congo"The title of the website. This will be displayed in the site header and footer.
descriptionNot setThe website description. This will be used in the site metadata.
copyrightNot setA 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 title.
author.nameNot setThe author’s name. This will be displayed in article footers, and on the homepage when the profile layout is used.
author.imageNot setPath to the image file of the author. The image should be a 1:1 aspect ratio and placed in the site’s assets/ folder.
author.headlineNot setA Markdown string containing the author’s headline. It will be displayed on the profile homepage under the author’s name.
author.bioNot setA Markdown string containing the author’s bio. It will be displayed in article footers.
author.linksNot setThe 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 assets/icons/.

Congo also supports language-specific menu configurations. Menu config files follow the same naming format as the languages file. Simply provide the language code in the file name to tell Hugo which language the file relates to.

Menu config files are named with the format menus.[language-code].toml. Always ensure that the language code used in the menus configuration matches the languages configuration.

The Getting Started section explains more about the structure of this file. You can also refer to the Hugo menu docs for more configuration examples.

Theme parameters #

Congo provides a large number of configuration parameters that control how the theme functions. The table below outlines every available parameter in the config/_default/params.toml file.

Many of the article defaults here can be overridden on a per article basis by specifying it in the front matter. Refer to the Front Matter section for further details.

NameDefaultDescription
colorScheme"congo"The theme colour scheme to use. Valid values are congo (default), avocado, ocean, fire and slate. Refer to the Colour Schemes section for more details.
defaultAppearance"light"The default theme appearance, either light or dark.
autoSwitchAppearancetrueWhether the theme appearance automatically switches based upon the visitor’s operating system preference. Set to false to force the site to always use the defaultAppearance.
enableSearchfalseWhether site search is enabled. Set to true to enable search functionality. Note that the search feature depends on the outputs.home setting in the site configuration being set correctly.
enableCodeCopyfalseWhether copy-to-clipboard buttons are enabled for <code> blocks. The highlight.noClasses parameter must be set to false for code copy to function correctly. Read more about other configuration files below.
logoNot setThe relative path to the site logo file within the assets/ folder. The logo file should be provided at 2x resolution and supports any image dimensions.
mainSectionsNot setThe sections that should be displayed in the recent articles list. If not provided the section with the greatest number of articles is used.
robotsNot setString that indicates how robots should handle your site. If set, it will be output in the page head. Refer to Google’s docs for valid values.
header.layout"basic"The layout of the page header and menu. Valid values are basic, hamburger or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/header/custom.html file.
footer.showCopyrighttrueWhether or not to show the copyright string in the site footer. Note that the string itself can be customised using the copyright parameter in the languages configuration.
footer.showThemeAttributiontrueWhether or not to show the “powered by” theme attribution in the site footer. If you choose to disable this message, please consider attributing the theme somewhere else on your site (for example, on your about page).
footer.showAppearanceSwitcherfalseWhether or not to show the appearance switcher in the site footer. The browser’s local storage is used to persist the visitor’s preference.
footer.showScrollToToptrueWhen set to true the scroll to top arrow is displayed.
homepage.layout"page"The layout of the homepage. Valid values are page, profile or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/home/custom.html file. Refer to the Homepage Layout section for more details.
homepage.showRecentfalseWhether or not to display the recent articles list on the homepage.
article.showDatetrueWhether or not article dates are displayed.
article.showDateUpdatedfalseWhether or not the dates articles were updated are displayed.
article.showAuthortrueWhether or not the author box is displayed in the article footer.
article.showBreadcrumbsfalseWhether or not breadcrumbs are displayed in the article header.
article.showDraftLabeltrueWhether or not the draft indicator is shown next to articles when site is built with --buildDrafts.
article.showEditfalseWhether or not the link to edit the article content should be displayed.
article.editURLNot setWhen article.showEdit is active, the URL for the edit link.
article.editAppendPathtrueWhen article.showEdit is active, whether or not the path to the current article should be appended to the URL set at article.editURL.
article.showHeadingAnchorstrueWhether or not heading anchor links are displayed alongside headings within articles.
article.showPaginationtrueWhether or not the next/previous article links are displayed in the article footer.
article.invertPaginationfalseWhether or not to flip the direction of the next/previous article links.
article.showReadingTimetrueWhether or not article reading times are displayed.
article.showTableOfContentsfalseWhether or not the table of contents is displayed on articles.
article.showTaxonomiesfalseWhether or not the taxonomies related to this article are displayed.
article.showWordCountfalseWhether or not article word counts are displayed.
article.showCommentsfalseWhether or not the comments partial is included after the article footer.
article.sharingLinksNot setWhich sharing links to display at the end of each article. When not provided, or set to false no links will be displayed.
list.showBreadcrumbsfalseWhether or not breadcrumbs are displayed in the header on list pages.
list.showTableOfContentsfalseWhether or not the table of contents is displayed on list pages.
list.showSummaryfalseWhether or not article summaries are displayed on list pages. If a summary is not provided in the front matter, one will be auto generated using the summaryLength parameter in the site configuration.
list.groupByYeartrueWhether or not articles are grouped by year on list pages.
sitemap.excludedKinds["taxonomy", "term"]Kinds of content that should be excluded from the generated /sitemap.xml file. Refer to the Hugo docs for acceptable values.
taxonomy.showTermCounttrueWhether or not the number of articles within a taxonomy term is displayed on the taxonomy listing.
fathomAnalytics.siteNot setThe site code generated by Fathom Analytics for the website. Refer to the Analytics docs for more details.
fathomAnalytics.domainNot setIf using a custom domain with Fathom Analytics, provide it here to serve script.js from the custom domain.
verification.googleNot setThe site verification string provided by Google to be included in the site metadata.
verification.bingNot setThe site verification string provided by Bing to be included in the site metadata.
verification.pinterestNot setThe site verification string provided by Pinterest to be included in the site metadata.
verification.yandexNot setThe site verification string provided by Yandex to be included in the site metadata.

Other configuration files #

The theme also includes a markup.toml configuration file. This file contains some important parameters that ensure that Hugo is correctly configured to generate sites built with Congo.

Always ensure this file is present in the config directory and that the required values are set. Failure to do so may cause certain features to fucntion incorrectly and could result in unintended behaviour.

  1. Documentation/

Configuration

2127 words·10 mins·0 views· +
Table of Contents

Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.

The theme ships with a default configuration that gets you up and running with a basic blog or static website.

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.

The default theme configuration is documented in each file so you can freely adjust the settings to meet your needs.

As outlined in the installation instructions, you should adjust your theme configuration by modifying the files in the config/_default/ folder of your Hugo project and delete the config.toml file in your project root.

Site configuration #

Standard Hugo configuration variables are respected throughout the theme, however there are some specific things that should be configured for the best experience.

The site configuration is managed through the config/_default/config.toml file. The table below outlines all the settings that the Congo takes advantage of.

Note that the variable names provided in this table use dot notation to simplify the TOML data structure (ie. outputs.home refers to [outputs] home).

NameDefaultDescription
theme"congo"When using Hugo Modules this config value should be removed. For all other installation types, this must be set to congo for the theme to function.
baseURLNot setThe URL to the root of the website.
defaultContentLanguage"en"This value determines the default language of theme components and content. Refer to the language and i18n section below for supported language codes.
enableRobotsTXTtrueWhen enabled, a robots.txt file will be created in the site root that allows search engines to crawl the entire site. If you prefer to provide your own pre-made robots.txt, set to false and place your file in the static directory. For complete control, you may provide a custom layout to generate this file.
paginate10The number of articles listed on each page of the article listing.
summaryLength0The number of words that are used to generate the article summary when one is not provided in the front matter. A value of 0 will use the first sentence. This value has no effect when summaries are hidden.
outputs.home["HTML", "RSS", "JSON"]The output formats that are generated for the site. Congo requires HTML, RSS and JSON for all theme components to work correctly.
permalinksNot setRefer to the Hugo docs for permalink configuration.
taxonomiesNot setRefer to the Organising content section for taxonomy configuration.

Language and i18n #

Congo is optimised for full multilingual websites and theme assets are translated into several languages out of the box. The language configuration allows you to generate multiple versions of your content to provide a customised experience to your visitors in their native language.

The theme currently supports the following languages by default:

LanguageCode
🇬🇧 Englishen
🇧🇩 Bengalibn
🇨🇳 Simplified Chinese (China)zh-cn
🇹🇼 Traditional Chinese (Taiwan)zh-tw
🇫🇮 Finnishfi
🇫🇷 Frenchfr
🇩🇪 Germande
🇮🇱 Hebrewhe
🇭🇺 Hungarianhu
🇮🇹 Italianit
🇯🇵 Japaneseja
🇧🇷 Portuguese (Brazil)pt-br
🇵🇹 Portuguese (Portugal)pt-pt
🇷🇴 Romanianro
🇪🇸 Spanish (Spain)es
🇹🇷 Turkishtr

The default translations can be overridden by creating a custom file in i18n/[code].yaml that contains the translation strings. You can also use this method to add new languages. If you’d like to share a new translation with the community, please open a pull request.

Configuration #

In order to be as flexible as possible, a language configuration file needs to be created for each language on the website. By default Congo includes an English language configuration at config/_default/languages.en.toml.

The default file can be used as a template to create additional languages, or renamed if you wish to author your website in a language other than English. Simply name the file using the format languages.[language-code].toml.

Note: Ensure the defaultContentLanguage parameter in the site configuration matches the language code in your language config filename.
NameDefaultDescription
languageCode"en"The Hugo language code for this file. It can be a top-level language (ie. en) or a sub-variant (ie. en-au) and should match the language code in the filename. Hugo expects this value to always be in lowercase. For proper HTML compliance, set the isoCode parameter which is case-sensitive.
languageName"English"The name of the language.
displayName"EN"The name used when the language appears on the website.
isoCode"en"The ISO language code for HTML metadata purposes. It can be a top-level language (ie. en) or a sub-variant (ie. en-AU).
weight1The weight determines the order of languages when building multilingual sites.
rtlfalseWhether or not this is a RTL language. Set to true to reflow content from right-to-left. Congo fully supports using RTL and LTR languages at the same time and will dynamically adjust to both.
dateFormat"2 January 2006"How dates are formatted in this language. Refer to the Hugo docs for acceptable formats.
title"Congo"The title of the website. This will be displayed in the site header and footer.
descriptionNot setThe website description. This will be used in the site metadata.
copyrightNot setA 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 title.
author.nameNot setThe author’s name. This will be displayed in article footers, and on the homepage when the profile layout is used.
author.imageNot setPath to the image file of the author. The image should be a 1:1 aspect ratio and placed in the site’s assets/ folder.
author.headlineNot setA Markdown string containing the author’s headline. It will be displayed on the profile homepage under the author’s name.
author.bioNot setA Markdown string containing the author’s bio. It will be displayed in article footers.
author.linksNot setThe 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 assets/icons/.

Congo also supports language-specific menu configurations. Menu config files follow the same naming format as the languages file. Simply provide the language code in the file name to tell Hugo which language the file relates to.

Menu config files are named with the format menus.[language-code].toml. Always ensure that the language code used in the menus configuration matches the languages configuration.

The Getting Started section explains more about the structure of this file. You can also refer to the Hugo menu docs for more configuration examples.

Theme parameters #

Congo provides a large number of configuration parameters that control how the theme functions. The table below outlines every available parameter in the config/_default/params.toml file.

Many of the article defaults here can be overridden on a per article basis by specifying it in the front matter. Refer to the Front Matter section for further details.

NameDefaultDescription
colorScheme"congo"The theme colour scheme to use. Valid values are congo (default), avocado, ocean, fire and slate. Refer to the Colour Schemes section for more details.
defaultAppearance"light"The default theme appearance, either light or dark.
autoSwitchAppearancetrueWhether the theme appearance automatically switches based upon the visitor’s operating system preference. Set to false to force the site to always use the defaultAppearance.
enableSearchfalseWhether site search is enabled. Set to true to enable search functionality. Note that the search feature depends on the outputs.home setting in the site configuration being set correctly.
enableCodeCopyfalseWhether copy-to-clipboard buttons are enabled for <code> blocks. The highlight.noClasses parameter must be set to false for code copy to function correctly. Read more about other configuration files below.
logoNot setThe relative path to the site logo file within the assets/ folder. The logo file should be provided at 2x resolution and supports any image dimensions.
mainSectionsNot setThe sections that should be displayed in the recent articles list. If not provided the section with the greatest number of articles is used.
robotsNot setString that indicates how robots should handle your site. If set, it will be output in the page head. Refer to Google’s docs for valid values.
header.layout"basic"The layout of the page header and menu. Valid values are basic, hamburger or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/header/custom.html file.
footer.showCopyrighttrueWhether or not to show the copyright string in the site footer. Note that the string itself can be customised using the copyright parameter in the languages configuration.
footer.showThemeAttributiontrueWhether or not to show the “powered by” theme attribution in the site footer. If you choose to disable this message, please consider attributing the theme somewhere else on your site (for example, on your about page).
footer.showAppearanceSwitcherfalseWhether or not to show the appearance switcher in the site footer. The browser’s local storage is used to persist the visitor’s preference.
footer.showScrollToToptrueWhen set to true the scroll to top arrow is displayed.
homepage.layout"page"The layout of the homepage. Valid values are page, profile or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/home/custom.html file. Refer to the Homepage Layout section for more details.
homepage.showRecentfalseWhether or not to display the recent articles list on the homepage.
article.showDatetrueWhether or not article dates are displayed.
article.showDateUpdatedfalseWhether or not the dates articles were updated are displayed.
article.showAuthortrueWhether or not the author box is displayed in the article footer.
article.showBreadcrumbsfalseWhether or not breadcrumbs are displayed in the article header.
article.showDraftLabeltrueWhether or not the draft indicator is shown next to articles when site is built with --buildDrafts.
article.showEditfalseWhether or not the link to edit the article content should be displayed.
article.editURLNot setWhen article.showEdit is active, the URL for the edit link.
article.editAppendPathtrueWhen article.showEdit is active, whether or not the path to the current article should be appended to the URL set at article.editURL.
article.showHeadingAnchorstrueWhether or not heading anchor links are displayed alongside headings within articles.
article.showPaginationtrueWhether or not the next/previous article links are displayed in the article footer.
article.invertPaginationfalseWhether or not to flip the direction of the next/previous article links.
article.showReadingTimetrueWhether or not article reading times are displayed.
article.showTableOfContentsfalseWhether or not the table of contents is displayed on articles.
article.showTaxonomiesfalseWhether or not the taxonomies related to this article are displayed.
article.showWordCountfalseWhether or not article word counts are displayed.
article.showCommentsfalseWhether or not the comments partial is included after the article footer.
article.sharingLinksNot setWhich sharing links to display at the end of each article. When not provided, or set to false no links will be displayed.
list.showBreadcrumbsfalseWhether or not breadcrumbs are displayed in the header on list pages.
list.showTableOfContentsfalseWhether or not the table of contents is displayed on list pages.
list.showSummaryfalseWhether or not article summaries are displayed on list pages. If a summary is not provided in the front matter, one will be auto generated using the summaryLength parameter in the site configuration.
list.groupByYeartrueWhether or not articles are grouped by year on list pages.
sitemap.excludedKinds["taxonomy", "term"]Kinds of content that should be excluded from the generated /sitemap.xml file. Refer to the Hugo docs for acceptable values.
taxonomy.showTermCounttrueWhether or not the number of articles within a taxonomy term is displayed on the taxonomy listing.
fathomAnalytics.siteNot setThe site code generated by Fathom Analytics for the website. Refer to the Analytics docs for more details.
fathomAnalytics.domainNot setIf using a custom domain with Fathom Analytics, provide it here to serve script.js from the custom domain.
verification.googleNot setThe site verification string provided by Google to be included in the site metadata.
verification.bingNot setThe site verification string provided by Bing to be included in the site metadata.
verification.pinterestNot setThe site verification string provided by Pinterest to be included in the site metadata.
verification.yandexNot setThe site verification string provided by Yandex to be included in the site metadata.

Other configuration files #

The theme also includes a markup.toml configuration file. This file contains some important parameters that ensure that Hugo is correctly configured to generate sites built with Congo.

Always ensure this file is present in the config directory and that the required values are set. Failure to do so may cause certain features to fucntion incorrectly and could result in unintended behaviour.

↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/content-examples/index.html b/docs/docs/content-examples/index.html index c46e877b..c9bd4061 100644 --- a/docs/docs/content-examples/index.html +++ b/docs/docs/content-examples/index.html @@ -1,16 +1,22 @@ Content Examples · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Content Examples

2005 words·10 mins·0 views· -
Table of Contents

If you’ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.

Tip: If you’re new to Hugo, be sure to check out the official docs to learn more about the concept of page bundles and resources.

The examples on this page can all be adapted to different scenarios but hopefully give you some ideas about how to approach formatting a particular content item for your individual project.

Branch pages #

Branch page bundles in Hugo cover items like the homepage, section listings, and taxonomy pages. The important thing to remember about branch bundles is that the filename for this content type is _index.md.

Congo will honour the front matter parameters specified in branch pages and these will override the default settings for that particular page. For example, setting the title parameter in a branch page will allow overriding the page title.

Homepage #

Layout:layouts/index.html
Content:content/_index.md

The homepage in Congo is special in that it’s overarching design is controlled by the homepage layout config parameter. You can learn more about this in the Homepage Layout section.

If you want to add custom content to this page, you simply need to create a content/_index.md file. Anything in this file will then be included in your homepage.

Example:

---
+
+
+ +
  1. Documentation/

Content Examples

2005 words·10 mins·0 views· +
Table of Contents

If you’ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.

Tip: If you’re new to Hugo, be sure to check out the official docs to learn more about the concept of page bundles and resources.

The examples on this page can all be adapted to different scenarios but hopefully give you some ideas about how to approach formatting a particular content item for your individual project.

Branch pages #

Branch page bundles in Hugo cover items like the homepage, section listings, and taxonomy pages. The important thing to remember about branch bundles is that the filename for this content type is _index.md.

Congo will honour the front matter parameters specified in branch pages and these will override the default settings for that particular page. For example, setting the title parameter in a branch page will allow overriding the page title.

Homepage #

Layout:layouts/index.html
Content:content/_index.md

The homepage in Congo is special in that it’s overarching design is controlled by the homepage layout config parameter. You can learn more about this in the Homepage Layout section.

If you want to add custom content to this page, you simply need to create a content/_index.md file. Anything in this file will then be included in your homepage.

Example:

---
 title: "Welcome to Congo!"
 description: "This is a demo of adding content to the homepage."
 ---
@@ -124,4 +130,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/front-matter/index.html b/docs/docs/front-matter/index.html index 2104db82..8fac4763 100644 --- a/docs/docs/front-matter/index.html +++ b/docs/docs/front-matter/index.html @@ -1,20 +1,27 @@ Front Matter · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Front Matter

508 words·3 mins·0 views· -

In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.

Front matter parameter default values are inherited from the theme’s base configuration, so you only need to specify these parameters in your front matter when you want to override the default.

NameDefaultDescription
titleNot setThe name of the article.
descriptionNot setThe text description for the article. It is used in the HTML metadata.
externalUrlNot setIf this article is published on a third-party website, the URL to this article. Providing a URL will prevent a content page being generated and any references to this article will link directly to the third-party website.
editURLarticle.editURLWhen showEdit is active, the URL for the edit link.
editAppendPatharticle.editAppendPathWhen showEdit is active, whether or not the path to the current article should be appended to the URL set at editURL.
groupByYearlist.groupByYearWhether or not articles are grouped by year on list pages.
menuNot setWhen a value is provided, a link to this article will appear in the named menus. Valid values are main or footer.
robotsNot setString that indicates how robots should handle this article. If set, it will be output in the page head. Refer to Google’s docs for valid values.
sharingLinksarticle.sharingLinksWhich sharing links to display at the end of this article. When not provided, or set to false no links will be displayed.
showAuthorarticle.showAuthorWhether or not the author box is displayed in the article footer.
showBreadcrumbsarticle.showBreadcrumbs or list.showBreadcrumbsWhether the breadcrumbs are displayed in the article or list header.
showDatearticle.showDateWhether or not the article date is displayed. The date is set using the date parameter.
showDateUpdatedarticle.showDateUpdatedWhether or not the date the article was updated is displayed. The date is set using the lastmod parameter.
showEditarticle.showEditWhether or not the link to edit the article content should be displayed.
showHeadingAnchorsarticle.showHeadingAnchorsWhether or not heading anchor links are displayed alongside headings within this article.
showPaginationarticle.showPaginationWhether or not the next/previous article links are displayed in the article footer.
invertPaginationarticle.invertPaginationWhether or not to flip the direction of the next/previous article links.
showReadingTimearticle.showReadingTimeWhether or not the article reading time is displayed.
showTaxonomiesarticle.showTaxonomiesWhether or not the taxonomies that relate to this article are displayed.
showTableOfContentsarticle.showTableOfContentsWhether or not the table of contents is displayed on this article.
showWordCountarticle.showWordCountWhether or not the article word count is displayed.
showCommentsarticle.showCommentsWhether or not the comments partial is included after the article footer.
showSummarylist.showSummaryWhether or not the article summary should be displayed on list pages.
summaryAuto generated using summaryLength (see site configuration)When showSummary is enabled, this is the Markdown string to be used as the summary for this article.
xmltrue unless excluded by sitemap.excludedKindsWhether or not this article is included in the generated /sitemap.xml file.
  1. Documentation/

Front Matter

508 words·3 mins·0 views· +

In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.

Front matter parameter default values are inherited from the theme’s base configuration, so you only need to specify these parameters in your front matter when you want to override the default.

NameDefaultDescription
titleNot setThe name of the article.
descriptionNot setThe text description for the article. It is used in the HTML metadata.
externalUrlNot setIf this article is published on a third-party website, the URL to this article. Providing a URL will prevent a content page being generated and any references to this article will link directly to the third-party website.
editURLarticle.editURLWhen showEdit is active, the URL for the edit link.
editAppendPatharticle.editAppendPathWhen showEdit is active, whether or not the path to the current article should be appended to the URL set at editURL.
groupByYearlist.groupByYearWhether or not articles are grouped by year on list pages.
menuNot setWhen a value is provided, a link to this article will appear in the named menus. Valid values are main or footer.
robotsNot setString that indicates how robots should handle this article. If set, it will be output in the page head. Refer to Google’s docs for valid values.
sharingLinksarticle.sharingLinksWhich sharing links to display at the end of this article. When not provided, or set to false no links will be displayed.
showAuthorarticle.showAuthorWhether or not the author box is displayed in the article footer.
showBreadcrumbsarticle.showBreadcrumbs or list.showBreadcrumbsWhether the breadcrumbs are displayed in the article or list header.
showDatearticle.showDateWhether or not the article date is displayed. The date is set using the date parameter.
showDateUpdatedarticle.showDateUpdatedWhether or not the date the article was updated is displayed. The date is set using the lastmod parameter.
showEditarticle.showEditWhether or not the link to edit the article content should be displayed.
showHeadingAnchorsarticle.showHeadingAnchorsWhether or not heading anchor links are displayed alongside headings within this article.
showPaginationarticle.showPaginationWhether or not the next/previous article links are displayed in the article footer.
invertPaginationarticle.invertPaginationWhether or not to flip the direction of the next/previous article links.
showReadingTimearticle.showReadingTimeWhether or not the article reading time is displayed.
showTaxonomiesarticle.showTaxonomiesWhether or not the taxonomies that relate to this article are displayed.
showTableOfContentsarticle.showTableOfContentsWhether or not the table of contents is displayed on this article.
showWordCountarticle.showWordCountWhether or not the article word count is displayed.
showCommentsarticle.showCommentsWhether or not the comments partial is included after the article footer.
showSummarylist.showSummaryWhether or not the article summary should be displayed on list pages.
summaryAuto generated using summaryLength (see site configuration)When showSummary is enabled, this is the Markdown string to be used as the summary for this article.
xmltrue unless excluded by sitemap.excludedKindsWhether or not this article is included in the generated /sitemap.xml file.
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/getting-started/index.html b/docs/docs/getting-started/index.html index 5d91c993..9f2fd756 100644 --- a/docs/docs/getting-started/index.html +++ b/docs/docs/getting-started/index.html @@ -1,16 +1,22 @@ Getting Started · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Getting Started

897 words·5 mins·0 views· -
Table of Contents
This section assumes you have already installed the Congo theme.

The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.

Basic configuration #

Before creating any content, there are a few things you should set for a new installation. Starting in the config.toml file, set the baseURL and languageCode parameters. The languageCode should be set to the main language that you will be using to author your content.

# config/_default/config.toml
+
+
+ +
  1. Documentation/

Getting Started

897 words·5 mins·0 views· +
Table of Contents
This section assumes you have already installed the Congo theme.

The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.

Basic configuration #

Before creating any content, there are a few things you should set for a new installation. Starting in the config.toml file, set the baseURL and languageCode parameters. The languageCode should be set to the main language that you will be using to author your content.

# config/_default/config.toml
 
 baseURL = "https://your_domain.com/"
 languageCode = "en"
@@ -81,4 +87,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/homepage-layout/index.html b/docs/docs/homepage-layout/index.html index a5a4c924..2efe9663 100644 --- a/docs/docs/homepage-layout/index.html +++ b/docs/docs/homepage-layout/index.html @@ -1,16 +1,22 @@ Homepage Layout · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Homepage Layout

478 words·3 mins·0 views· -
Table of Contents

Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.

The layout of the homepage is controlled by the homepage.layout setting in the params.toml configuration file. Additionally, all layouts have the option to include a listing of recent articles.

Page layout #

The default layout is the page layout. It’s simply a normal content page that displays your Markdown content. It’s great for static websites and provides a lot of flexibility.

+
+ +
  1. Documentation/

Homepage Layout

478 words·3 mins·0 views· +
Table of Contents

Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.

The layout of the homepage is controlled by the homepage.layout setting in the params.toml configuration file. Additionally, all layouts have the option to include a listing of recent articles.

Page layout #

The default layout is the page layout. It’s simply a normal content page that displays your Markdown content. It’s great for static websites and provides a lot of flexibility.

Screenshot of homepage layout

To enable the page layout, set homepage.layout = "page" in the params.toml configuration file.

Profile layout #

The profile layout is great for personal websites and blogs. It puts the author’s details front and centre by providing an image and links to social profiles.

→ ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/hosting-deployment/index.html b/docs/docs/hosting-deployment/index.html index 689dbe95..c8621d08 100644 --- a/docs/docs/hosting-deployment/index.html +++ b/docs/docs/hosting-deployment/index.html @@ -1,17 +1,23 @@ Hosting & Deployment · Blowfish - + - - + + -
  1. Documentation/

Hosting & Deployment

822 words·4 mins·0 views· -
Table of Contents

There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.

Congo is built using relative URLs throughout the theme. This enables sites to easily be deployed to sub-folders and hosts like GitHub Pages. There’s usually no special configuration required for this to work as long as the baseURL parameter has been configured in the config.toml file.

The official Hugo Hosting and Deployment docs are the best place to learn how to deploy your site. The sections below contain some specific theme configuration details that can help you deploy smoothly with certain providers.

Choose your provider:

GitHub Pages #

GitHub allows hosting on GitHub Pages using Actions. To enable this functionality, enable Pages on your repo and create a new Actions workflow to build and deploy your site.

The file needs to be in YAML format, placed within the .github/workflows/ directory of your GitHub repository and named with a .yml extension.

Important: Ensure you set the correct branch name under branches and in the deploy step if parameter to the source branch used in your project.
# .github/workflows/gh-pages.yml
+
Table of Contents

There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.

Congo is built using relative URLs throughout the theme. This enables sites to easily be deployed to sub-folders and hosts like GitHub Pages. There’s usually no special configuration required for this to work as long as the baseURL parameter has been configured in the config.toml file.

The official Hugo Hosting and Deployment docs are the best place to learn how to deploy your site. The sections below contain some specific theme configuration details that can help you deploy smoothly with certain providers.

Choose your provider:

GitHub Pages #

GitHub allows hosting on GitHub Pages using Actions. To enable this functionality, enable Pages on your repo and create a new Actions workflow to build and deploy your site.

The file needs to be in YAML format, placed within the .github/workflows/ directory of your GitHub repository and named with a .yml extension.

Important: Ensure you set the correct branch name under branches and in the deploy step if parameter to the source branch used in your project.
# .github/workflows/gh-pages.yml
 
 name: GitHub Pages
 
@@ -69,4 +75,5 @@
 Advanced Customisation
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/index.html b/docs/docs/index.html index 6e4edd16..a1df913b 100644 --- a/docs/docs/index.html +++ b/docs/docs/index.html @@ -1,17 +1,24 @@ Documentation · Blowfish - + - - + + -

Documentation

Simple, yet powerful. Learn how to use Congo and its features.

Screenshots of Congo on an iPhone, iPad and MacBook

This section contains everything you need to know about Congo. If you’re new, check out the Installation guide to begin or visit the Samples section to see what Congo can do.

2022

What's New in 2.0 ✨

771 words·4 mins·0 views

2020

Installation

976 words·5 mins·0 views

Getting Started

897 words·5 mins·0 views

Configuration

2127 words·10 mins·0 views

Homepage Layout

478 words·3 mins·0 views

Front Matter

508 words·3 mins·0 views

Shortcodes

954 words·5 mins·0 views

Partials

751 words·4 mins·0 views

Content Examples

2005 words·10 mins·0 views

Advanced Customisation

1519 words·8 mins·0 views

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/installation/index.html b/docs/docs/installation/index.html index a816630b..030420b6 100644 --- a/docs/docs/installation/index.html +++ b/docs/docs/installation/index.html @@ -1,16 +1,22 @@ Installation · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Installation

976 words·5 mins·0 views· -
Table of Contents

Simply follow the standard Hugo Quick Start procedure to get up and running quickly.

Detailed installation instructions can be found below. Instructions for updating the theme are also available.

Installation #

These instructions will get you up and running using Hugo and Congo from a completely blank state. Most of the dependencies mentioned in this guide can be installed using the package manager of choice for your platform.

Install Hugo #

If you haven’t used Hugo before, you will need to install it onto your local machine. You can check if it’s already installed by running the command hugo version.

Make sure you are using Hugo version 0.87.0 or later as the theme takes advantage of some of the latest Hugo features.

You can find detailed installation instructions for your platform in the Hugo docs.

Create a new site #

Run the command hugo new site mywebsite to create a new Hugo site in a directory named mywebsite.

Note that you can name the project directory whatever you choose, but the instructions below will assume it’s named mywebsite. If you use a different name, be sure to substitute it accordingly.

Download the Congo theme #

There several different ways to install the Congo theme into your Hugo website. From easiest to most difficult to install and maintain, they are:

If you’re unsure, choose the Hugo module method.

Install using Hugo #

This method is the quickest and easiest for keeping the theme up-to-date. Hugo uses Go to initialise and manage modules so you need to ensure you have go installed before proceeding.

  1. Download and install Go. You can check if it’s already installed by using the command go version.

    Make sure you are using Go version 1.12 or later as Hugo requires this for modules to work correctly.

  2. From your Hugo project directory (that you created above), initialise modules for your website:

    # If you're managing your project on GitHub
+
+
    + +
  1. Documentation/

Installation

976 words·5 mins·0 views· +
Table of Contents

Simply follow the standard Hugo Quick Start procedure to get up and running quickly.

Detailed installation instructions can be found below. Instructions for updating the theme are also available.

Installation #

These instructions will get you up and running using Hugo and Congo from a completely blank state. Most of the dependencies mentioned in this guide can be installed using the package manager of choice for your platform.

Install Hugo #

If you haven’t used Hugo before, you will need to install it onto your local machine. You can check if it’s already installed by running the command hugo version.

Make sure you are using Hugo version 0.87.0 or later as the theme takes advantage of some of the latest Hugo features.

You can find detailed installation instructions for your platform in the Hugo docs.

Create a new site #

Run the command hugo new site mywebsite to create a new Hugo site in a directory named mywebsite.

Note that you can name the project directory whatever you choose, but the instructions below will assume it’s named mywebsite. If you use a different name, be sure to substitute it accordingly.

Download the Congo theme #

There several different ways to install the Congo theme into your Hugo website. From easiest to most difficult to install and maintain, they are:

If you’re unsure, choose the Hugo module method.

Install using Hugo #

This method is the quickest and easiest for keeping the theme up-to-date. Hugo uses Go to initialise and manage modules so you need to ensure you have go installed before proceeding.

  1. Download and install Go. You can check if it’s already installed by using the command go version.

    Make sure you are using Go version 1.12 or later as Hugo requires this for modules to work correctly.

  2. From your Hugo project directory (that you created above), initialise modules for your website:

    # If you're managing your project on GitHub
 hugo mod init github.com/<username>/<repo-name>
 
 # If you're managing your project locally
@@ -32,4 +38,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/partials/index.html b/docs/docs/partials/index.html index 8761347a..919f23e3 100644 --- a/docs/docs/partials/index.html +++ b/docs/docs/partials/index.html @@ -1,16 +1,22 @@ Partials · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Partials

751 words·4 mins·0 views· -
Table of Contents

Analytics #

Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you’re interested you can use this affiliate link to receive $10 credit and try the service.

Fathom Analytics #

To enable Fathom Analytics support, simply provide your Fathom site code in the config/_default/params.toml file. If you also use the custom domain feature of Fathom and would like to serve their script from your domain, you can also additionally provide the domain configuration value. If you don’t provide a domain value, the script will load directly from Fathom DNS.

# config/_default/params.toml
+
+
+ +
  1. Documentation/

Partials

751 words·4 mins·0 views· +
Table of Contents

Analytics #

Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you’re interested you can use this affiliate link to receive $10 credit and try the service.

Fathom Analytics #

To enable Fathom Analytics support, simply provide your Fathom site code in the config/_default/params.toml file. If you also use the custom domain feature of Fathom and would like to serve their script from your domain, you can also additionally provide the domain configuration value. If you don’t provide a domain value, the script will load directly from Fathom DNS.

# config/_default/params.toml
 
 [fathomAnalytics]
   site = "ABC12345"
@@ -37,4 +43,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/shortcodes/index.html b/docs/docs/shortcodes/index.html index 76d988a5..96f59e15 100644 --- a/docs/docs/shortcodes/index.html +++ b/docs/docs/shortcodes/index.html @@ -1,20 +1,26 @@ Shortcodes · Blowfish - + - - + + -
Blowfish +
  1. Documentation/

Shortcodes

954 words·5 mins·0 views· -
Table of Contents

In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.

Alert #

alert outputs its contents as a stylised message box within your article. It’s useful for drawing attention to important information that you don’t want the reader to miss.

The input is written in Markdown so you can format it however you please.

By default, the alert is presented with an exclaimation triangle icon. To change the icon, include the icon name in the shortcode. Check out the icon shortcode for more details on using icons.

Example:

{{< alert >}}
+
+
+ +
  1. Documentation/

Shortcodes

954 words·5 mins·0 views· +
Table of Contents

In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.

Alert #

alert outputs its contents as a stylised message box within your article. It’s useful for drawing attention to important information that you don’t want the reader to miss.

The input is written in Markdown so you can format it however you please.

By default, the alert is presented with an exclaimation triangle icon. To change the icon, include the icon name in the shortcode. Check out the icon shortcode for more details on using icons.

Example:

{{< alert >}}
 **Warning!** This action is destructive!
 {{< /alert >}}
 
@@ -37,8 +43,8 @@
   }]
 }
 {{< /chart >}}
-
-

You can see some additional Chart.js examples on the charts samples page.

Figure #

Congo includes a figure shortcode for adding images to content. The shortcode replaces the base Hugo functionality in order to provide additional performance benefits.

When a provided image is a page resource, it will be optimised using Hugo Pipes and scaled in order to provide images appropriate to different device resolutions. If a static asset or URL to an external image is provided, it will be included as-is without any image processing by Hugo.

The figure shortcode accepts six parameters:

ParameterDescription
srcRequired. The local path/filename or URL of the image. When providing a path and filename, the theme will attempt to locate the image using the following lookup order: Firstly, as a page resource bundled with the page; then an asset in the assets/ directory; then finally, a static image in the static/ directory.
altAlternative text description for the image.
captionMarkdown for the image caption, which will be displayed below the image.
classAdditional CSS classes to apply to the image.
hrefURL that the image should be linked to.
defaultSpecial parameter to revert to default Hugo figure behaviour. Simply provide default=true and then use normal Hugo shortcode syntax.

Congo also supports automatic conversion of images included using standard Markdown syntax. Simply use the following format and the theme will handle the rest:

![Alt text](image.jpg "Image caption")
+
+

You can see some additional Chart.js examples on the charts samples page.

Figure #

Congo includes a figure shortcode for adding images to content. The shortcode replaces the base Hugo functionality in order to provide additional performance benefits.

When a provided image is a page resource, it will be optimised using Hugo Pipes and scaled in order to provide images appropriate to different device resolutions. If a static asset or URL to an external image is provided, it will be included as-is without any image processing by Hugo.

The figure shortcode accepts six parameters:

ParameterDescription
srcRequired. The local path/filename or URL of the image. When providing a path and filename, the theme will attempt to locate the image using the following lookup order: Firstly, as a page resource bundled with the page; then an asset in the assets/ directory; then finally, a static image in the static/ directory.
altAlternative text description for the image.
captionMarkdown for the image caption, which will be displayed below the image.
classAdditional CSS classes to apply to the image.
hrefURL that the image should be linked to.
defaultSpecial parameter to revert to default Hugo figure behaviour. Simply provide default=true and then use normal Hugo shortcode syntax.

Congo also supports automatic conversion of images included using standard Markdown syntax. Simply use the following format and the theme will handle the rest:

![Alt text](image.jpg "Image caption")

Example:

{{< figure
     src="abstract.jpg"
     alt="Abstract purple artwork"
@@ -72,4 +78,5 @@ B-->C[Profit]

You can see some additional Mermaid examples on the → ←

↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/version-2/index.html b/docs/docs/version-2/index.html index 204ae684..eb9c6d5c 100644 --- a/docs/docs/version-2/index.html +++ b/docs/docs/version-2/index.html @@ -1,15 +1,21 @@ What's New in 2.0 ✨ · Blowfish - + - - + + -
Blowfish +

What's New in 2.0 ✨

Congo 2.0 is packed with tons of new features and optimisations.

The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.

Continue reading below to discover what’s new. When you’re ready to upgrade, check out the guide to upgrading.

Tailwind CSS 3.0 #

Tailwind CSS is at the heart of Congo and this new release contains the very latest Tailwind CSS version 3. It brings with it performance optimisations and support for some great new CSS features.

Implementing this new version has also removed some Tailwind plugin dependencies from the theme, allowing the overall footprint to remain lightweight.

Multilingual support #

A highly requested feature, Congo is now multilingual! If you publish your content in multiple languages, the site will be built with all the translations available.

🇬🇧 🇩🇪 🇫🇷 🇪🇸 🇨🇳 🇧🇷 🇹🇷 🇧🇩

Thanks to submissions from the community, Congo has already been translated into eight languages with more to be added over time. By the way, pull requests for new languages are always welcome!

RTL language support #

One of the benefits of the new Tailwind and Multilingual features is the ability to add RTL language support. When enabled, the entire site will reflow content from right-to-left. Every element in the theme has been restyled to ensure it looks great in this mode which aids authors who wish to generate content in RTL languages.

RTL is controlled on a per-language basis so you can mix and match both RTL and LTR content in your projects and the theme will respond accordingly.

Automatic image resizing #

A big change in Congo 2.0 is the addition of automatic image resizing. Using the power of Hugo Pipes, images in Markdown content are now automatically scaled to different output sizes. These are then presented using HTML srcset attributes enabling optimised file sizes to be served to your site visitors.

+
+ +

What's New in 2.0 ✨

Congo 2.0 is packed with tons of new features and optimisations.

The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.

Continue reading below to discover what’s new. When you’re ready to upgrade, check out the guide to upgrading.

Tailwind CSS 3.0 #

Tailwind CSS is at the heart of Congo and this new release contains the very latest Tailwind CSS version 3. It brings with it performance optimisations and support for some great new CSS features.

Implementing this new version has also removed some Tailwind plugin dependencies from the theme, allowing the overall footprint to remain lightweight.

Multilingual support #

A highly requested feature, Congo is now multilingual! If you publish your content in multiple languages, the site will be built with all the translations available.

🇬🇧 🇩🇪 🇫🇷 🇪🇸 🇨🇳 🇧🇷 🇹🇷 🇧🇩

Thanks to submissions from the community, Congo has already been translated into eight languages with more to be added over time. By the way, pull requests for new languages are always welcome!

RTL language support #

One of the benefits of the new Tailwind and Multilingual features is the ability to add RTL language support. When enabled, the entire site will reflow content from right-to-left. Every element in the theme has been restyled to ensure it looks great in this mode which aids authors who wish to generate content in RTL languages.

RTL is controlled on a per-language basis so you can mix and match both RTL and LTR content in your projects and the theme will respond accordingly.

Automatic image resizing #

A big change in Congo 2.0 is the addition of automatic image resizing. Using the power of Hugo Pipes, images in Markdown content are now automatically scaled to different output sizes. These are then presented using HTML srcset attributes enabling optimised file sizes to be served to your site visitors.

<!-- Markdown: ![My image](image.jpg) -->
@@ -24,4 +30,5 @@
 />

Best of all there’s nothing you need to change! Simply insert standard Markdown image syntax and let the theme do the rest. If you want a little more control, the figure shortcode has been completely rewritten to provide the same resizing benefits.

Performance improvements #

This update packs performance improvements throughout. A key objective for this release was to improve Lighthouse scores and Congo now scores a perfect 100 on all four metrics.

There’s too many individual changes to highlight them here but the results speak for themselves. If you want to dig deeper, you can view the Lighthouse report. Real world performance will vary based upon server configuration.

Powered by Fuse.js, site search allows visitors to quickly and easily find your content. All searches are performed client-side meaning there’s nothing to configure on the server and queries are performed super fast. Simply enable the feature in your site configuration and you’re all set. Oh, and it also supports full keyboard navigation!

Tables of contents #

A highly requested feature, Congo now supports tables of contents on article pages. You can see it in action on this page. The contents are fully responsive and will adjust to take advantage of the space available at different screen resolutions.

Available on a global or per article basis, the table of contents can be fully customised using standard Hugo configuration values, allowing you to adjust the behaviour to suit your project.

Accessibility improvements #

From adding ARIA descriptions to more items or simply adjusting the contrast of certain text elements, this release is the most accessible yet.

Version 2 also introduces “skip to content” and “scroll to top” links that enable quick navigation. There’s also keyboard shortcuts for enabling items like search without reaching for the mouse.

The new image resizing features also provide full control over alt and title elements enabling an accessible experience for all visitors.

A whole lot more #

There’s countless other minor changes to explore. From being able to display taxonomies on articles and list pages, to using the new headline author parameter to customise your homepage. There’s also improved JSON-LD strucured data which further optimises SEO performance. Plus the entire theme has had extra polish to ensure a consistent design language.

🚀 Check out the full changelog to learn more.

Next steps #

If you’re ready to upgrade, read the upgrading from version 1 guide to get started. If you’re new to Congo, check out the Installation guide to begin a new project.

2022

Upgrading from Congo 1.x

1382 words·7 mins·0 views
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/docs/version-2/upgrade/index.html b/docs/docs/version-2/upgrade/index.html index edd7070a..48b83104 100644 --- a/docs/docs/version-2/upgrade/index.html +++ b/docs/docs/version-2/upgrade/index.html @@ -1,16 +1,22 @@ Upgrading from Congo 1.x · Blowfish - + - - + + -
Blowfish +
  1. Documentation/
  2. What's New in 2.0 ✨/

Upgrading from Congo 1.x

1382 words·7 mins·0 views· -
Table of Contents

Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.

That said, there are some changes that require adjustments to existing sites that are built with Congo version 1.x. This guide will step you through the process and highlight things you need to consider.

Step 1: Upgrade Hugo #

Congo 2.0 requires a minimum of Hugo v0.87.0 or later

Congo is built to take advantage of some of the latest Hugo features. You should regularly keep your Hugo installation up to date to avoid any issues.

You can check your current version using the command hugo version. Visit the Hugo docs for information on obtaining a newer release for your platform.

Step 2: Upgrade Congo #

The process for upgrading Congo will depend on how you include the theme in your project. Instructions for each method can be found below.

Upgrade using Hugo #

To upgrade a go module to a new major release, the modules.toml and go.mod files need to be updated. In each file, update the path to the theme from github.com/jpanther/congo to github.com/jpanther/congo/v2.

Then change into your project directory and execute the following command:

hugo mod get -u
+
+
+ +
  1. Documentation/
  2. What's New in 2.0 ✨/

Upgrading from Congo 1.x

1382 words·7 mins·0 views· +
Table of Contents

Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.

That said, there are some changes that require adjustments to existing sites that are built with Congo version 1.x. This guide will step you through the process and highlight things you need to consider.

Step 1: Upgrade Hugo #

Congo 2.0 requires a minimum of Hugo v0.87.0 or later

Congo is built to take advantage of some of the latest Hugo features. You should regularly keep your Hugo installation up to date to avoid any issues.

You can check your current version using the command hugo version. Visit the Hugo docs for information on obtaining a newer release for your platform.

Step 2: Upgrade Congo #

The process for upgrading Congo will depend on how you include the theme in your project. Instructions for each method can be found below.

Upgrade using Hugo #

To upgrade a go module to a new major release, the modules.toml and go.mod files need to be updated. In each file, update the path to the theme from github.com/jpanther/congo to github.com/jpanther/congo/v2.

Then change into your project directory and execute the following command:

hugo mod get -u

Note that in some circumstances there may be issues with this step due to the way that Hugo locally caches modules. If the command above doesn’t work, try using hugo mod clean to clear out the local cache and re-download any modules.

Once the theme has been upgraded, continue to the next section.

Upgrade using git #

Git submodules can be upgraded using the git command. Simply execute the following command and the latest version of the theme will be downloaded into your local repository:

git submodule update --remote --merge

Once the submodule has been upgraded, continue to the next section.

Upgrade manually #

Updating Congo manually requires you to download the latest copy of the theme and replace the old version in your project.

Note that any local customisations you have made to the theme files will be lost during this process.

  1. Download the latest release of the theme source code.

    Download from Github

  2. Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project’s root folder. You will need to overwrite the existing directory to replace all the theme files.

  3. Continue to the next section.

Step 3: Theme configuration #

Congo 2.0 introduces a number of new theme configuration parameters. Although the theme will adapt to existing version 1 configurations, in order to take advantage of some of the newer theme features, you will need to adjust your existing configuration.

The simplest way to do this is to take a copy of the theme’s default configuration and compare it to your existing files. The process is outlined in greater detail below.

Languages.toml #

In order to provide multilingual support, language-specific theme parameters have been moved to a new config file languages.[lang-code].toml. The theme comes with a template languages.en.toml file which can be used as a guide.

This step is optional if you do not need multilingual support, although completing it now will make future theme upgrades easier.

The languages config file follows this structure:

# config/_default/languagues.en.toml
 
@@ -39,4 +45,5 @@
   endLevel = 4

Params.toml #

A number of new theme parameters have been introduced in Congo 2.0. Some minor changes are requried to existing configurations. Remember, the theme will always revert to a sensible default if a parameter is not provided.

The way that dark mode works in Congo has been changed to allow greater flexibility around configuration. The old darkMode and darkToggle parameters have been removed and replaced by three new parameters. These new options operate independently of each other, making it possible to force the appearance while still allowing the user to override.

New parameterTypeDefaultDescription
defaultAppearanceString"light"Default theme appearance; either light or dark.
⚠️ Setting this to light replicates the old darkMode = false setting, while dark replicates darkMode = true.
autoSwitchAppearanceBooleantrueWhether the theme appearance automatically switches based upon the operating system preference. Set to false to force the site to always use the defaultAppearance.
⚠️ Setting this to true replicates the old darkMode = "auto" setting.
showAppearanceSwitcherBooleanfalseWhether the theme appearance switcher is dispalyed in the site footer.
⚠️ This parameter replaces darkToggle.

The following table outlines some other key new parameters that control new features in version 2:

New parameterTypeDefault
enableSearchBooleanfalse
showScrollToTopBooleantrue
article.showTaxonomiesBooleanfalse
article.showTableOfContentsBooleanfalse
list.showTableOfContentsBooleanfalse

For the full list of supported parameters, refer to the Configuration docs.

Step 4: Move assets #

All site assets, with the exception of favicons, now use Hugo Pipes to build an optimised version of your project. In order for the theme to locate your files, any previously static theme assets need to be moved to the Hugo assets folder. Primarily this is the author image and site logo:

static/me.jpg → assets/me.jpg
static/logo.jpg → assets/logo.jpg

If you have provided an author image or site logo, simply move these assets from static/ to assets/. If you use the same directory structure the theme will know where to find these files automatically. If you would like to provide a new path, update the logo and author.image config values accordingly.

Note that this step does not apply to any assets in your project that are actually static. For example, a PDF file that you link directly to from within an article is a static asset. These files should remain in the static/ directory to ensure they are copied to the output folder when Hugo builds the site.

Step 5: Check content #

The behavior of the figure shortcode is different in version 2. If you are using figure in your content and have advanced use cases, you may need to adjust the parameters you are providing.

Consult the shortcode docs to learn more about supported parameters.

Step 6: Rebuild #

Now that all the configuration changes are complete, it’s time to rebuild the site. Run hugo, or your build command, and check that everything works as expected.

If you come across any errors, check the configuration is correct and refer to the full documentation for further guidance. Remember, the example config files bundled with the theme contain all the default parameters and are a great starting point.

🙋‍♀️ If you still need help, feel free to ask your question on GitHub Discussions.

↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/index.html b/docs/index.html index 74ace3ab..78f73a52 100644 --- a/docs/index.html +++ b/docs/index.html @@ -1,15 +1,22 @@ Blowfish - + - - + + -
Blowfish

Blowfish

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/index.json b/docs/index.json index 3ef3edc6..a32a3ffc 100644 --- a/docs/index.json +++ b/docs/index.json @@ -1 +1 @@ -[{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/amazon/","section":"Tags","summary":"","title":"Amazon"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/apple/","section":"Tags","summary":"","title":"Apple"},{"content":"","date":"4 September 2022","permalink":"/blowfish/","section":"Blowfish","summary":"","title":"Blowfish"},{"content":"","date":"4 September 2022","permalink":"/blowfish/categories/","section":"Categories","summary":"","title":"Categories"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/disney/","section":"Tags","summary":"","title":"Disney"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/netflix/","section":"Tags","summary":"","title":"Netflix"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/prediction/","section":"Tags","summary":"","title":"Prediction"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/product/","section":"Tags","summary":"","title":"Product"},{"content":"","date":"4 September 2022","permalink":"/blowfish/categories/product/","section":"Categories","summary":"","title":"Product"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/strategy/","section":"Tags","summary":"","title":"Strategy"},{"content":"","date":"4 September 2022","permalink":"/blowfish/categories/strategy/","section":"Categories","summary":"","title":"Strategy"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/streaming/","section":"Tags","summary":"","title":"Streaming"},{"content":" Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players (cough, cough… Blockbuster) laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches (e.g., Curiosity Stream - documentaries, Crunchyroll - anime, etc.).\nHow Did We Get Here? # This question could turn into its series of posts, aka a very long and boring answer. The short version, Netflix hit gold when they launched their streaming-only subscription service that allowed customers to watch what they wanted when they wanted. This was a massive shift from the linear TV experience where you either had to wait in front of the TV to watch your favorite show, record and watch it later, or wait for a rerun (fun fact: there was another option to set a reminder to watch your shows :D). Not only did Netflix launch a way better product to consume content, but it also changed the way users discovered new series and movies by recommending new shows based on previous history. Users flocked to this service, which was significantly better than the alternatives and also cheaper than the average cable subscription at the time (i.e., cutting the chord).\nAfter Netflix showed everyone how people really wanted to consume content, several players were interested in replicating that model themselves. Traditional content producers (e.g., HBO, Disney, etc.) saw a way to control their distribution channel and get a direct relationship with their customers. Other players, like Apple and Amazon, saw a good opportunity to expand their service subscription strategy by offering yet-another-service to their user-base. This year, most of these services reached hundreds of millions of paying users, and the competition in this industry was never been this strong.\nMassive Investment in Content # One of the strong signals of this competition is the huge amounts of money being spent in content production. HBO just released House of the Dragon, a prequel to their hit series Game of Thrones. The first season had an estimated production cost of just under $20 million per episode, making the 10 episode run cost a full $200 million. In comparison, Game of Thrones cost around $100 million per season, with the average cost per episode starting around $6 million in season 1 and going up to $15 million in the final season. This means HBO just invested roughly double what it did in the last season of Game of Thrones.\nAmazon, coincidentally, also decided to launch its prequel of a super-loved property in the fantasy drama space, Lord of the Rings. Investment in the new series, called Lord of the Rings: The Rings of Power, is estimated to be around $1 billion. Amazon bought the franchise rights to Lord of the Rings for $250 million and invested $465 million to produce the eight-episode first season of the show. In comparison, the entire trilogy of the Lord of the Rings was produced for roughly $300 million, $100 million for each movie.\nNetflix has been increasing its costs with content production in the last years, arriving at $17 billion this year. Disney is set to spend even more than that, $32 billion (even after cuts). In a different space, big tech companies are also getting into live sports. All of this spending creates a super competitive environment across all services, which is not necessarily in the best interest of the viewers.\nQuality is Decreasing # One could argue that all the investment and all the money being thrown at content production will bring the golden age of entertainment. However, as most big investments, they are made to make someone money. In the entertainment industry, one of the ways to reduce risk is to invest in properties that have already proven their value in opposition to new Intellectual Property (IP).\nThe levels of “content pumping” that we are seeing nowadays lead to a massive decrease in quality, and worse, viewer fatigue. Especially since it is focused on a minimal set of genres (i.e., fantasy, hero movies, etc.) and franchises (i.e., Marvel Cinematic Universe, DC Cinematic Universe, Star Wars, Fast and the Furious, etc.)\nMore Money In… More Money Out # When a company increases costs, usually the aim is to increase revenue and profit. Streaming services charge a fixed fee per month. Therefore, it doesn’t really matter how much or how little you loved the next big fantasy drama series from your favorite streaming provider – they will make the same amount of money from you.\nUnless… streaming companies increase subscription prices and find new ways to monetize content. Aided by the excuse of inflation, most services have increased their prices in the last year. Specifically, Disney+ subscription in the U.S. will rise from $7.99 to $10.99, while Hulu\u0026rsquo;s ad-free offering will jump from $12.99 per month to $14.99 per month. Netflix cheapest plan increased to $9.99, with the top one at $20.00. Additionally, executives from most of these big companies are also planning to roll out ads for their services. Yes, even Netflix that resisted for years cannot keep ignoring that option when faced with competition.\nUltimately, this is a worse product for the user. Price increases could make the overall cost of streaming services too high for some users, which will force a choice of which services to keep. Furthermore, you will get ads again, or you can pay more if you would rather not see them.\nWhat Happens Next? # The high levels of competition have begun to generate frustration among users. Users are starting to get fatigued with the low-quality and constant recycling of content (I swear, I am uncertain whether I can handle yet another Marvel Movie or Star Wars trilogy). The increase in prices, especially in the current economic situation, will force users to choose which services to pay for, if any. And ultimately, competition for user’s attention has never been so high. Social networks like Twitter, Instagram, and TikTok take hours of engagement daily out of each user. Video game investment has never been so high, with so many options of games and consoles.\nIn my opinion, the streaming wars have already peaked, and we’ll see a change in the upcoming years before getting to a new equilibrium. I think that one out of three things will happen:\nHorizontal Expansion - current streaming services would need to expand to provide additional services and bundle them together. This would increase the value for money and could be interesting to some users depending on what is being bundled. Netflix has begun doing this with games. Companies like Amazon and Apple came into streaming exactly for this reason, expanding into streaming even if it was not their core business. Aggregation - One service to rule them all… If one of the existing services, or a new player, can aggregate content from several players at a lower price point, this could create a captivating value proposition for customers on the lower end. This option seems highly unlikely, this was Netflix play years ago, and it didn’t work, potentially because they were greedy. Nevertheless, in the current scenario, it is highly unlikely that big players would share rights with another VS getting exclusivity on those. Merges and Acquisitions - Big fish eats smaller fish. This is bound to happen at some point, it’s just a matter of time and which company will acquire which company for what amount of money. It’s not clear if this will be good or bad for customers, depending on who starts playing together. My prediction is that ultimately, big tech companies like Amazon or Apple will begin acquiring other smaller players. These companies come into streaming as a horizontal expansion from their core businesses. Both are armed with an order of magnitude more revenues than their content only counterparts. As an example, in 2021 Disney’s revenue was $81.10 billion and Netflix\u0026rsquo;s was $24.9 billion. In comparison, Apple’s revenue in the same year was $378.32 billion and Amazon’s was $468.82 billion. With this kind of “war chest” plus their own core business (Apple devices, and Amazon e-commerce business) it will be way easier for these companies to step in when they want to.\n","date":"4 September 2022","permalink":"/blowfish/posts/202209-streaming-wars/","section":"Posts","summary":"Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?","title":"Streaming Wars and What Comes After… "},{"content":"Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.\nThis area could be used to add some extra decriptive text to each taxonomy. Check out the advanced tag below to see how to take this concept even further.\n","date":"4 September 2022","permalink":"/blowfish/tags/","section":"Tags","summary":"Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.","title":"Tags"},{"content":"","date":"4 September 2022","permalink":"/blowfish/tags/wars/","section":"Tags","summary":"","title":"Wars"},{"content":" This article was originally published externally, read the original here. Docker’s goal is to create a world-class product experience for our customers. We want to build a robust product that will help all teams achieve their goals. In line with that, we’ve tried to simplify the process of onboarding your team into the Docker ecosystem with our Bulk User Add feature for Docker Business and Docker Team subscriptions.\nYou can invite your team to their accounts by uploading a file including their email addresses to Docker Hub. The CSV file can either be a file you create for this specific purpose, or one that’s extracted from another in-house system. The sole requirement is that the file contains a column with the email addresses of the users that will be invited into Docker. Once the CSV file is uploaded using Docker Hub, each team member in the file will receive an invitation to use their account.\nWe’ve also updated Docker Hub’s web interface to add multiple members at once. We hope this is useful for smaller teams that can just copy and paste a list of emails directly in the web interface and onboard everyone they need. Once your team is invited, you can see both the pending and accepted invites through Docker Hub.\nBulk User Add can be used without needing to have SSO setup for your organization. This feature allows you to get the most out of your Docker Team or Business subscription, and it greatly simplifies the onboarding process.\nLearn more about the feature on our docs page, and sign in to your Docker Hub account to try it for yourself.\nAnd if you have any questions or would like to discuss this feature, please attend our upcoming\n","date":"27 July 2022","permalink":"/blowfish/posts/202207-docker-bulk-add/","section":"Posts","summary":"Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!","title":"Bulk User Add for Docker Business and Teams"},{"content":"","date":"27 July 2022","permalink":"/blowfish/tags/docker/","section":"Tags","summary":"","title":"Docker"},{"content":"","date":"27 July 2022","permalink":"/blowfish/categories/docker/","section":"Categories","summary":"","title":"Docker"},{"content":"","date":"27 July 2022","permalink":"/blowfish/tags/docker-hub/","section":"Tags","summary":"","title":"Docker Hub"},{"content":"","date":"27 July 2022","permalink":"/blowfish/tags/feature/","section":"Tags","summary":"","title":"Feature"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/congo/","section":"Tags","summary":"","title":"Congo"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/development/","section":"Tags","summary":"","title":"Development"},{"content":"","date":"27 June 2022","permalink":"/blowfish/categories/development/","section":"Categories","summary":"","title":"Development"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/environment/","section":"Tags","summary":"","title":"Environment"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/go/","section":"Tags","summary":"","title":"Go"},{"content":" TL;DR # Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results.\nWhy would a PM build their own homepage from scratch… # A couple of months ago I decided that I wanted to start writing more in order to a) exercise my writing skills and b) get feedback on some of my ideas. With this goal in mind, I started researching tools/platforms that would help me publish without creating too much friction for me, or for the people wanting to read what I have to say e.g. having to pay. Ultimately I decided upon creating my own website.\nI had a couple of reasons for wanting to try this:\nchallenge me to see if I, a previous software engineering student, could still bodge something together that would work and feel good about not having forgotten everything I ever learned about programming,\nfind a flexible free solution that would allow me to kickstart my website without investing money right away into it, aka avoiding operational costs with platforms and services that would lock me in the future,\nhave my content hosted in a place that will not require people to pay for reading it,\nplay around with Docker\u0026rsquo;s developer environments and Microsoft\u0026rsquo;s developer containers to get myself familiar with both solutions.\nLet’s get started… # After some research, I decided to choose a website generator framework and a free hosting service. For the website framework, I choose Hugo with Congo as the theme, and for the hosting service Firebase. And for obvious reasons, I decided to set up my development environment using Docker in order to put myself in the user\u0026rsquo;s shoes for this experiment.\nI didn\u0026rsquo;t go into a deep analysis of which framework was the best for my problem as I wanted to get an MVP out fast so I went through a couple of options and picked the first one that I liked. There are several other options with different features and approaches from the one I picked. If you want to explore other options these are some you can explore: Docussaurus, Gatsby, Jekyll, Ghost, and even WordPress. The same is applicable to the hosting part, even though I chose Firebase there are other solutions like Cloudflare Pages, GitHub Pages, Digital Ocean, Netlify, Vercel, and others that you might consider exploring. If you have any suggestions for this guide feel free to reach out, always happy to chat and learn.\nTools # For this guide, I will use the following tools, which should be installed on your machine. Here is a small explanation of what each component is going to be used for and a link to the installation instructions.\nDocker - I will use Docker to configure a development environment for this project so that we can skip the need to install all the software required to run Hugo and Firebase CLI i.e. cURL, Go, Hugo, Node, NPM, etc. This will allow you to start from a git repository, start the environment and go straight into writing code instead of spending hours figuring out how to install a specific compiler for your CPU architecture. Install Docker\nVisual Studio Code - I\u0026rsquo;m using Visual Studio Code as my code editor at the moment, and all the material in the guide assumes that this is what you\u0026rsquo;re using. If you have a different preference you’ll need to adapt some parts of this guide to achieve the same results. Install Visual Studio Code\nSetup the Development Environment # Let\u0026rsquo;s start by configuring your development environment using Docker. This will allow you to create a container with all the tools you need inside of it without having to mess with your system configurations. Moreover, it will also make it easier to just delete the container and rebuild it whenever you need it instead of keeping old versions of software you don\u0026rsquo;t require daily in your personal machine.\nNote: If you just want to clone a repo with the final skeleton feel free to clone this repo and skip to the deploy section I\u0026rsquo;ll provide two ways of setting up your development environment feel free to choose the one you prefer or try both to explore the differences between them. Both options rely on a Dockerfile built by me which uses klakegg/hugo:0.93.2-ubuntu as the base image, even though this is not Hugo\u0026rsquo;s official image (since there isn\u0026rsquo;t one at the moment) it\u0026rsquo;s the one recommended on their website,.\nUsing Docker # To spin up a Dev Environment just open Docker Dashboard and select the \u0026ldquo;Dev Environments\u0026rdquo; tab on the left. If you don\u0026rsquo;t have any dev environments setup select \u0026ldquo;Create New Environment\u0026rdquo; otherwise use the button on the upper right side \u0026ldquo;Create\u0026rdquo;. Proceed to the setup step.\nHere choose the \u0026ldquo;Existing Git repo\u0026rdquo; option and use the following GitHub URL:\nhttps://github.com/nunocoracao/homepage-kickstart Note: If you clone the repo locally you can also start from the local folder Once the container is running you should see something similar to the images below.\nIn both situations, you will be able to see and click the button \u0026ldquo;Open in VSCode\u0026rdquo; which will open the editor and will allow you to start working. From there open a terminal and proceed to create the site skeleton\nUsing Visual Studio Code # Start by cloning the GitHub repository with the development environment configurations.\ngit clone https://github.com/nunocoracao/homepage-kickstart This method requires the installation of an extra VSCode extension in order to spin up the containers. Please search for Remote - Containers and install the extension to continue this guide.\nAfter successfully installing the extension, open your source folder in VSCode and open the “Remote - Containers” extension panel on the left. Select \u0026ldquo;Open Folder in Container\u0026rdquo; to spin up a container with the development environment.\nWait a couple of minutes while the image is built. Docker is creating an image with all the required software for the development of the website. This will only happen the first time you spin the environment.\nOnce the image is built, VSCode will spin the container and will place your working environment inside of it (information available in the bottom left corner of the window). You now have a development environment with Go, Hugo, Firebase CLI, and all the tools you will need for this guide. Just open a new terminal and you’re ready to begin creating your site.\n\u0026hellip;but I really want to run everything locally # If you either prefer or need to run your environment locally follow the guides below to install everything you need for your setup:\nHomebrew - Install homebrew Hugo - Install Hugo Node.js and NPM - Install node.js \u0026amp; NPM (easier to install Firebase CLI) Firebase CLI - Install Firebase CLI Create Site Skeleton # Now that we have a development environment running the first step is to create the base version of your website. For this let’s use Hugo to generate the folder template and configuration files we need by running the following command (--force parameter is required to run Hugo on a non-empty directory):\nhugo new site . --force This should have created a set of folders inside your workspace that you don’t need to worry about for now. The next step is to install a theme for Hugo. I choose Congo as it had all the features I required for my website and it seemed to be easy to change if I ever need it to. If you want to try a different theme there are several available in Hugo’s documentation, each with documentation and examples.\nInstall Congo using git submodules by running the following command:\ngit submodule add -b stable https://github.com/jpanther/congo.git themes/congo Now we need to make some changes to the directory and file structure so that Congo can work properly. I will not get into the details of what is happening in this guide (you can consult Congo’s documentation if you want to learn more), the main takeaway is that we’re creating and configuring a folder in config/_default/ which will contain all the important configuration files for Hugo and Congo.\nPlease run the following commands in order:\nmkdir -p config/_default rm config.toml cp themes/congo/config/_default/*.toml config/_default/ echo \u0026#39;theme = \u0026#34;congo\u0026#34;\u0026#39; | cat - config/_default/config.toml \u0026gt; temp \u0026amp;\u0026amp; mv temp config/_default/config.toml Congratulations, you should have your site up and running now. Let\u0026rsquo;s try it out by running Hugo\u0026rsquo;s debug server:\nhugo server -D Please open your favorite browser and navigate to localhost:1313 to see your page.\nYou should see something similar to the image above. Doesn’t look that exciting, does it? Let’s configure the theme in the next sections and learn how to create your first article.\nConfigure Theme # Now I’ll be covering how to change the look and feel of your website, add some personal information, and activate the dark mode toggle (aka the most important feature in any website these days).\nA note, I am covering a very simple configuration for this theme please check Congo’s theme documentation to understand everything you can do with this theme. Profile picture # Let’s start by adding a profile picture to your site. Create a folder called “assets” at the root of your project. Choose a profile picture and place it inside the assets folder. The rest of the guide will assume the final picture is named \u0026ldquo;profile.jpg\u0026rdquo;, so please rename your picture or take that into account when configuring some of the other files.\nIf you still need to take a proper awesome picture for this feel free to download this one to proceed with the tutorial. Configuration Files # Let’s open a couple of configuration files and start updating them. All the files we are going to change are inside config/_default/ folder.\nconfig.toml # Uncomment the baseURL parameter and replace it with the final domain of your website. This value will be used to create the robots.txt file for any search engines to successfully crawl and index your website.\nNote: if you want to configure Google Analytics please add the following line with your id to this file googleAnalytics = \u0026quot;G-XXXXXX\u0026quot; languages.en.toml # This file will drive the main information for the website and the author of the page (you). Replace the title and description for the ones you want for your page, these values will drive the HTML title and description tags.\nWithin the [author] block you can update the details that you wish to highlight in your profile. The bare minimum would be name, image, headline, and links. For the links parameter don\u0026rsquo;t forget to uncomment the last line of the file as this is a json array. Update each entry with your personal links.\nparams.toml # This file defines much of the overall behavior across the entire framework. For this tutorial I changed some of the overall values and one for the homepage, if you want to learn more about the other available configurations please consult Congo’s theme documentation.\nI\u0026rsquo;ve changed colorScheme to \u0026ldquo;ocean\u0026rdquo; which changes the global UI theme. Congo defines a three-color palette that is used throughout the theme. Valid values are congo (default), avocado, ocean, fire, and slate. Although these are the default schemes, you can also create your own. Refer to the theme\u0026rsquo;s main documentation to learn how.\nActivated showAppearanceSwitcher to enable the light/dark mode toggle. Activated enableSearch which indexes all future posts each time you build the site and provides a simple search feature. I\u0026rsquo;ve also changed the value of layout, inside [homepage], to \u0026ldquo;profile\u0026rdquo; which changes the way the landing page is rendered. Finally, the last interesting value here is showRecent, which when turned on shows the recent posts on the homepage.\nFinal # Let’s see how it looks, run the Hugo again:\nhugo server -D And navigate to localhost:1313 you should see something similar to the page below.\nCongrats it’s looking great, let’s learn how to generate your first articles.\nHow to generate articles # Hugo provides some tools to generate your articles (markdown files) with a base set of tags already in them. Run the following command to create your first post\nhugo new posts/my-first-post.md replace the contents of the file with the following:\n--- title: \u0026#34;My Published Post\u0026#34; date: 2022-06-19T20:10:29Z draft: false categories: [\u0026#34;published\u0026#34;, \u0026#34;test\u0026#34;] tags: [\u0026#34;first\u0026#34;, \u0026#34;awesome\u0026#34;] --- This is my first blog post This just created your first blog post. We\u0026rsquo;ve added a couple of categories and tags, which will be indexed by Hugo during build time. These tags will be used to create the Categories and Tags section of the website automatically for you. Notice that I\u0026rsquo;ve changed the draft to false to simulate a published post.\nRun the following command to create your second post\nhugo new posts/my-draft-post.md and replace the contents of that file with the following:\n--- title: \u0026#34;My Draft Post\u0026#34; date: 2022-06-19T20:20:39Z draft: true categories: [\u0026#34;draft\u0026#34;, \u0026#34;test\u0026#34;] tags: [\u0026#34;second\u0026#34;, \u0026#34;awesome\u0026#34;] --- This is my second blog post For the second post, I\u0026rsquo;ve left the draft parameter true to simulate a draft post.\nHugo automatically hides draft posts from the final site generation. You can keep working on articles leaving the draft label true and they will be ignored by the engine. If you want to run in DEBUG mode just use the command:\nhugo server -D If you go to the posts on the site you should be able to see both entries. If you then run the server in normal mode the draft articles will disappear. You can use the command below to do so:\nhugo server You can use this command to test the final version of the website or an article before generating the final build. When you\u0026rsquo;re ready just use the command \u0026lsquo;Hugo\u0026rsquo; to generate the final website inside the /public folder.\nhugo All files are written in Markdown which Hugo then uses to generate the final pages. I\u0026rsquo;ll not teach you how to write markdown files in this guide but I can recommend this \u0026ldquo;getting started\u0026rdquo; tutorial and this \u0026ldquo;cheat sheet\u0026rdquo; to get you started.\nDeploy # Ok, you’ve configured your website and created a couple of articles, but we still need to deploy it somewhere. As I mentioned before I chose Firebase for this guide, even though I know that it offers much more than just a simple hosting service it allows me to host my site for free without much of a hassle.\nCreate Firebase Project # Let’s start by going to https://firebase.google.com and creating an account. Once that is done you can create a project for free. The process should be straightforward and when you finish you should be in Firebase\u0026rsquo;s project dashboard.\nSetup Firebase # Now you can go back to your environment which already has Firebase CLI tools installed and ready to go. Let’s start by authenticating using:\nfirebase login Once you are successfully logged in you need to initiate the project configurations for firebase. For that please use:\nfirebase init The tool will offer you a wide variety of different options in order to configure your Firebase project. For now, we just want to configure hosting. If you are using GitHub, you might want to consider configuring GitHub action deploys which can automatically build and deploy your site every time there is a push to a specific branch or a merged pull request.\nChoose the Firebase project created before as the hosting destination. And select the configurations you wish for the deployment process. The important one here is the folder where the final files to the server will be placed and this is the public folder. For the other parameters you experiment with what better matches your use-case, the image below shows you what I picked (Note: for this tutorial I didn\u0026rsquo;t configure GitHub actions but I am using that in my real setup).\nDeploy # Ok, now for the long and boring process of deployment… joking! Once you are ready and have all your files generated by the hugo command in the public folder just use the following command to deploy:\nfirebase deploy The process should take a couple of seconds and there you go your site is deployed. The final line of the CLI tool will give you a URL to see for yourself, otherwise, you can explore your Firebase dashboard hosting section which will have more information regarding the deployment.\nConclusion # By now you should have a simple version of your website which you can configure to your needs. The main advantage of this solution is that it is flexible and extensible to a variety of different needs especially if you take the time to explore Hugo\u0026rsquo;s theme catalog. True that it might require some coding to implement complex but I would guess that this solves the problem for almost everyone.\nAbove all, it’s a completely free solution if you\u0026rsquo;re looking to start and can\u0026rsquo;t (or don\u0026rsquo;t want to) spend money. Hope this guide helps you, feel free to share it with your network and give me feedback so that I can make it better over time.\nResources # GitHub Repo for development environment GitHub Repo for base Hugo and Congo configuration GitHub Repo for base image Docker Hub image URL Hugo's Documentation Congo's Documentation Firebase Documentation Markdown Guide Markdown Getting Started\u0026quot; Markdown Cheat Sheet ","date":"27 June 2022","permalink":"/blowfish/posts/202206-homepage-guide/","section":"Posts","summary":"Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results.","title":"How I Created My Homepage (for free) Using Docker, Hugo, and Firebase"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/hugo/","section":"Tags","summary":"","title":"Hugo"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/tutorial/","section":"Tags","summary":"","title":"Tutorial"},{"content":"","date":"27 June 2022","permalink":"/blowfish/categories/tutorial/","section":"Categories","summary":"","title":"Tutorial"},{"content":"","date":"27 June 2022","permalink":"/blowfish/tags/vscode/","section":"Tags","summary":"","title":"VSCode"},{"content":"","date":"26 June 2022","permalink":"/blowfish/tags/interview/","section":"Tags","summary":"","title":"Interview"},{"content":"","date":"26 June 2022","permalink":"/blowfish/categories/interview/","section":"Categories","summary":"","title":"Interview"},{"content":"","date":"26 June 2022","permalink":"/blowfish/tags/mentorcruise/","section":"Tags","summary":"","title":"Mentorcruise"},{"content":"","date":"26 June 2022","permalink":"/blowfish/tags/mentorship/","section":"Tags","summary":"","title":"Mentorship"},{"content":"","date":"26 June 2022","permalink":"/blowfish/categories/mentorship/","section":"Categories","summary":"","title":"Mentorship"},{"content":" This article was originally published externally, read the original here. I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms.\nWhy did you decide to become a mentor? # Throughout my career, I was fortunate enough to find (or be found by) amazing mentors that helped me in several different ways. Some provided advice for professional decisions and career management, others access to opportunities, and some just took me along for the ride to “watch \u0026amp; learn”. All of those contributed so much to make me a better professional and gave me some really interesting opportunities in my career. In the last few years, I started being a mentor myself and I am really enjoying the experience of helping others grow and fulfill their career dreams.\nWhat benefits did you gain from working with mentors early on? # The main benefit was the ability to tap into someone else’s experience and seniority and learn from their past experiences. It allowed me to get a glimpse of the future and accelerate some career milestones I wanted for myself. As an example, I never had the dream of working or living abroad, but after talking about it with my mentors (that had that experience) I learned so much about what it could bring me professionally and personally that when that opportunity came I was better prepared to make the right decision. Overall, it gave me the chance to learn how to become a better professional by watching how my mentors did it on a professional setting. Moreover, it gave me the chance to manage my career by tapping into their advice and experience in order to achieve my goals.\nHow did you get your career start? # My career started as a trainee in a telco company here in Portugal. I just left university and a junior researcher position to become a solutions architect for the TV department. It was amazing to get the first job with such responsibility and exposure to the entire organization. However, I have to say that the best part of that role was my manager who made an extra effort to coach and teach me so many invaluable lessons that I do still remember after so many years.\nGood advice is not “one-size-fits-all”\nHow do you usually set up mentorships? # I usually like to understand what are the person’s goals for the mentorship and depending on those design a specific plan. Independently of the goal, I aim to have a weekly 1:1 with each mentee to catch up on progress and see if there is anything that I can do to help with. I also like to have a log file in docs to track questions/actions/open points. What we do within this framework highly depends on the goals themselves. For example, if the mentee is looking for help in switching into a product role, I might help review the CV and LinkedIn profile and prepare them for interviews with material and mock sessions.\nWhat benefit can you provide to mentees over self-studying? # As with my own personal experience, the best benefit I can provide my mentees is to allow them to tap into my experiences, and the rational behind them, so that they can learn from it. I don’t mean to say they should do exactly as I did, no advice comes in a “one-size-fits-all” package. Moreover, I definitely made some mistakes along the way. But with that insight, each person can decide what resonates with them and what doesn’t in order to make their own decisions. In summary, I’m here to help with product topics and career management, specially people that want to get into product and don’t know where to start.\nWhat’s been your favourite mentorship story so far? # In one of my previous role I was managing two young professionals that joined the product team as QA Engineers. Both of them wanted to become Product Managers and were looking for ways to make that move happen. During one year I made an extra effort to share my experiences, give advice, and try to get them as many opportunities to have a “taste” of what PM is by getting them into meetings and brainstormings with my dev teams, shadow customer calls, attend meetings with management, etc. I was really happy the day I was able to sponsor both of them into their first PM roles still within the company. Since then it has been even more fulfilling to watch them grow and have their own successful careers in Product.\nWhat are you getting out of being a mentor? # From my experience, having access to mentors, allowed me to grow and improve at a professional and personal level faster than by myself. At this stage in my life, I feel like I’ve experienced enough to have something valuable to share with others and maybe help them achieve their goals. Ultimately, that is what I am aiming to get out of this experience, to be able to have the same impact as a mentor as my mentors had on me.\n","date":"26 June 2022","permalink":"/blowfish/posts/202206-mentorcruise-interview-copy/","section":"Posts","summary":"Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.","title":"Nuno Coração – Meet the Mentor"},{"content":" This article was originally published externally, read the original here. I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms.\nWhy did you decide to become a mentor? # Throughout my career, I was fortunate enough to find (or be found by) amazing mentors that helped me in several different ways. Some provided advice for professional decisions and career management, others access to opportunities, and some just took me along for the ride to “watch \u0026amp; learn”. All of those contributed so much to make me a better professional and gave me some really interesting opportunities in my career. In the last few years, I started being a mentor myself and I am really enjoying the experience of helping others grow and fulfill their career dreams.\nWhat benefits did you gain from working with mentors early on? # The main benefit was the ability to tap into someone else’s experience and seniority and learn from their past experiences. It allowed me to get a glimpse of the future and accelerate some career milestones I wanted for myself. As an example, I never had the dream of working or living abroad, but after talking about it with my mentors (that had that experience) I learned so much about what it could bring me professionally and personally that when that opportunity came I was better prepared to make the right decision. Overall, it gave me the chance to learn how to become a better professional by watching how my mentors did it on a professional setting. Moreover, it gave me the chance to manage my career by tapping into their advice and experience in order to achieve my goals.\nHow did you get your career start? # My career started as a trainee in a telco company here in Portugal. I just left university and a junior researcher position to become a solutions architect for the TV department. It was amazing to get the first job with such responsibility and exposure to the entire organization. However, I have to say that the best part of that role was my manager who made an extra effort to coach and teach me so many invaluable lessons that I do still remember after so many years.\nGood advice is not “one-size-fits-all”\nHow do you usually set up mentorships? # I usually like to understand what are the person’s goals for the mentorship and depending on those design a specific plan. Independently of the goal, I aim to have a weekly 1:1 with each mentee to catch up on progress and see if there is anything that I can do to help with. I also like to have a log file in docs to track questions/actions/open points. What we do within this framework highly depends on the goals themselves. For example, if the mentee is looking for help in switching into a product role, I might help review the CV and LinkedIn profile and prepare them for interviews with material and mock sessions.\nWhat benefit can you provide to mentees over self-studying? # As with my own personal experience, the best benefit I can provide my mentees is to allow them to tap into my experiences, and the rational behind them, so that they can learn from it. I don’t mean to say they should do exactly as I did, no advice comes in a “one-size-fits-all” package. Moreover, I definitely made some mistakes along the way. But with that insight, each person can decide what resonates with them and what doesn’t in order to make their own decisions. In summary, I’m here to help with product topics and career management, specially people that want to get into product and don’t know where to start.\nWhat’s been your favourite mentorship story so far? # In one of my previous role I was managing two young professionals that joined the product team as QA Engineers. Both of them wanted to become Product Managers and were looking for ways to make that move happen. During one year I made an extra effort to share my experiences, give advice, and try to get them as many opportunities to have a “taste” of what PM is by getting them into meetings and brainstormings with my dev teams, shadow customer calls, attend meetings with management, etc. I was really happy the day I was able to sponsor both of them into their first PM roles still within the company. Since then it has been even more fulfilling to watch them grow and have their own successful careers in Product.\nWhat are you getting out of being a mentor? # From my experience, having access to mentors, allowed me to grow and improve at a professional and personal level faster than by myself. At this stage in my life, I feel like I’ve experienced enough to have something valuable to share with others and maybe help them achieve their goals. Ultimately, that is what I am aiming to get out of this experience, to be able to have the same impact as a mentor as my mentors had on me.\n","date":"26 June 2022","permalink":"/blowfish/posts/202206-mentorcruise-interview/","section":"Posts","summary":"Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.","title":"Nuno Coração – Meet the Mentor"},{"content":"Experience Company Link Role Dates Location Docker Staff Product Manager 2022 - Present Full Remote Lisbon, PT AWS Startup Loft Startup Advisor 2022 - Present Full Remote Lisbon, PT Truphone Group Product Manager 2021 - 2022 Hybrid Lisbon, PT Senior Product Manager 2020 - 2021 Vodafone Group Analytics Squad Lead 2019 - 2020 Lisbon, PT London, UK Senior Product Manager 2018 - 2019 Sky Deutschland Senior Product Architect 2016 - 2018 Munich, DE Skimic Founder 2016 - 2017 Munich, DE Vodafone Group Product Manager 2015 - 2016 Lisbon, PTLondon, UK NOS Product Manager 2014 - 2015 Lisbon, PT Solutions Architect 2012 - 2014 Inesc-ID Junior Researcher 2011 - 2012 Lisbon, PT Education School Link Degree Date Harvard Business School Online Entrepreneurship Essentials 2022 Disruptive Strategy 2022 Tecnico Lisboa MSc in Computer Science - Distributed Systems 2012 BSc, Computer Science 2010 ","date":"13 June 2022","permalink":"/blowfish/resume/","section":"Blowfish","summary":"Experience Company Link Role Dates Location Docker Staff Product Manager 2022 - Present Full Remote Lisbon, PT AWS Startup Loft Startup Advisor 2022 - Present Full Remote Lisbon, PT Truphone Group Product Manager 2021 - 2022 Hybrid Lisbon, PT Senior Product Manager 2020 - 2021 Vodafone Group Analytics Squad Lead 2019 - 2020 Lisbon, PT London, UK Senior Product Manager 2018 - 2019 Sky Deutschland Senior Product Architect 2016 - 2018 Munich, DE Skimic Founder 2016 - 2017 Munich, DE Vodafone Group Product Manager 2015 - 2016 Lisbon, PTLondon, UK NOS Product Manager 2014 - 2015 Lisbon, PT Solutions Architect 2012 - 2014 Inesc-ID Junior Researcher 2011 - 2012 Lisbon, PT Education School Link Degree Date Harvard Business School Online Entrepreneurship Essentials 2022 Disruptive Strategy 2022 Tecnico Lisboa MSc in Computer Science - Distributed Systems 2012 BSc, Computer Science 2010 ","title":"Resume"},{"content":"I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.\nI’ve worked for several years in big companies and recently decided to trade that for the opportunity of working in smaller teams. Definitely prefer the latter where one can succeed/fail faster, learn faster, and overall have a way bigger impact.\nCurrently, I am focused on improving the lives of developers worldwide. I’m trying to write more about my previous experiences / random thoughts and would love to gather your feedback on it. I also love to dedicate my time to helping and mentoring other PMs or people that want to get into product.\nRecently I’ve also joined AWS Loft to help Startups and their founders with their product strategy.\nFeel free to reach out.\n","date":"13 June 2022","permalink":"/blowfish/about/","section":"Blowfish","summary":"I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.","title":"About"},{"content":"I started learning music by myself at the age of 14. I play several instruments and I love to record, compose and produce my own music. I\u0026rsquo;ve been releasing my songs under the name \u0026ldquo;Doppler Effect\u0026rdquo; in the usual streaming services. Here are the links if you want to listen.\nCover Title Released Listen Remember a New Day August 2022 Teardrop July 2022 The Devil Dances Tonight July 2022 Bellucci's Catwalk June 2022 Another Beginning June 2022 Blue in Green June 2022 Dreaming in Color January 2022 Sweet June September 2021 Walking Miles April 2021 A Different Kind of Tango April 2021 Burka April 2021 Smoking with a Ninja April 2021 ","date":"13 June 2022","permalink":"/blowfish/music/","section":"Blowfish","summary":"I started learning music by myself at the age of 14. I play several instruments and I love to record, compose and produce my own music. I\u0026rsquo;ve been releasing my songs under the name \u0026ldquo;Doppler Effect\u0026rdquo; in the usual streaming services.","title":"Music"},{"content":"","date":"13 June 2022","permalink":"/blowfish/posts/","section":"Posts","summary":"","title":"Posts"},{"content":"","date":"20 January 2022","permalink":"/blowfish/tags/docs/","section":"Tags","summary":"","title":"docs"},{"content":" Simple, yet powerful. Learn how to use Congo and its features. This section contains everything you need to know about Congo. If you\u0026rsquo;re new, check out the Installation guide to begin or visit the Samples section to see what Congo can do.\n","date":"20 January 2022","permalink":"/blowfish/docs/","section":"Documentation","summary":"Simple, yet powerful. Learn how to use Congo and its features. This section contains everything you need to know about Congo. If you\u0026rsquo;re new, check out the Installation guide to begin or visit the Samples section to see what Congo can do.","title":"Documentation"},{"content":"","date":"20 January 2022","permalink":"/blowfish/tags/new/","section":"Tags","summary":"","title":"new"},{"content":"Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.\nThat said, there are some changes that require adjustments to existing sites that are built with Congo version 1.x. This guide will step you through the process and highlight things you need to consider.\nStep 1: Upgrade Hugo # Congo 2.0 requires a minimum of Hugo v0.87.0 or later Congo is built to take advantage of some of the latest Hugo features. You should regularly keep your Hugo installation up to date to avoid any issues.\nYou can check your current version using the command hugo version. Visit the Hugo docs for information on obtaining a newer release for your platform.\nStep 2: Upgrade Congo # The process for upgrading Congo will depend on how you include the theme in your project. Instructions for each method can be found below.\nUpgrade using Hugo Upgrade using git Upgrade manually Upgrade using Hugo # To upgrade a go module to a new major release, the modules.toml and go.mod files need to be updated. In each file, update the path to the theme from github.com/jpanther/congo to github.com/jpanther/congo/v2.\nThen change into your project directory and execute the following command:\nhugo mod get -u Note that in some circumstances there may be issues with this step due to the way that Hugo locally caches modules. If the command above doesn\u0026rsquo;t work, try using hugo mod clean to clear out the local cache and re-download any modules.\nOnce the theme has been upgraded, continue to the next section.\nUpgrade using git # Git submodules can be upgraded using the git command. Simply execute the following command and the latest version of the theme will be downloaded into your local repository:\ngit submodule update --remote --merge Once the submodule has been upgraded, continue to the next section.\nUpgrade manually # Updating Congo manually requires you to download the latest copy of the theme and replace the old version in your project.\nNote that any local customisations you have made to the theme files will be lost during this process. Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder. You will need to overwrite the existing directory to replace all the theme files.\nContinue to the next section.\nStep 3: Theme configuration # Congo 2.0 introduces a number of new theme configuration parameters. Although the theme will adapt to existing version 1 configurations, in order to take advantage of some of the newer theme features, you will need to adjust your existing configuration.\nThe simplest way to do this is to take a copy of the theme\u0026rsquo;s default configuration and compare it to your existing files. The process is outlined in greater detail below.\nLanguages.toml # In order to provide multilingual support, language-specific theme parameters have been moved to a new config file languages.[lang-code].toml. The theme comes with a template languages.en.toml file which can be used as a guide.\nThis step is optional if you do not need multilingual support, although completing it now will make future theme upgrades easier. The languages config file follows this structure:\n# config/_default/languagues.en.toml languageCode = \u0026#34;en\u0026#34; languageName = \u0026#34;English\u0026#34; displayName = \u0026#34;EN\u0026#34; htmlCode = \u0026#34;en\u0026#34; weight = 1 rtl = false # Language-specific parameters go here Using your preferred language, simply create this new file in config/_default/ and then move the language-specific parameters from any existing config files over to this new file. The table below outlines the parameters that need to be moved.\nParameter Old location title config.toml description params.toml copyright config.toml dateFormat params.toml [author] config.toml Once the values have been moved to the new location, these parameters should be deleted from their original locations.\nMenus.toml # As the theme is now aware of languages, the menus.toml file should also be renamed to include a language code. Rename the existing menus.toml to menus.[lang-code].toml, where the language code matches the code used in the languages.toml file in the previous section.\nConfig.toml # The config.toml file now only contains base Hugo configuration values. Other than removing the language-specific strings above, there are only two changes to consider.\nIf you\u0026rsquo;re using a language other than English, provide a defaultContentLanguage value that matches the language code in the config file you created for your language. Secondly, to take advange of the new site search in Congo 2.0, an [outputs] block needs to be provided.\n# config/_default/config.toml defaultContentLanguage = \u0026#34;en\u0026#34; enableRobotsTXT = true paginate = 10 summaryLength = 0 [outputs] home = [\u0026#34;HTML\u0026#34;, \u0026#34;RSS\u0026#34;, \u0026#34;JSON\u0026#34;] Markup.toml # Congo 2.0 adds support for tables of contents on article pages. Although Hugo ships with default settings for generating contents listings, you can adjust this behaviour by adding a new [tableOfContents] block to your markup.toml file.\nThe recommended settings are as follows, which includes any headings in the Markdown content at levels 2, 3 and 4:\n# config/_default/markup.toml [tableOfContents] startLevel = 2 endLevel = 4 Params.toml # A number of new theme parameters have been introduced in Congo 2.0. Some minor changes are requried to existing configurations. Remember, the theme will always revert to a sensible default if a parameter is not provided.\nThe way that dark mode works in Congo has been changed to allow greater flexibility around configuration. The old darkMode and darkToggle parameters have been removed and replaced by three new parameters. These new options operate independently of each other, making it possible to force the appearance while still allowing the user to override.\nNew parameter Type Default Description defaultAppearance String \u0026quot;light\u0026quot; Default theme appearance; either light or dark.\n⚠️ Setting this to light replicates the old darkMode = false setting, while dark replicates darkMode = true. autoSwitchAppearance Boolean true Whether the theme appearance automatically switches based upon the operating system preference. Set to false to force the site to always use the defaultAppearance. ⚠️ Setting this to true replicates the old darkMode = \u0026quot;auto\u0026quot; setting. showAppearanceSwitcher Boolean false Whether the theme appearance switcher is dispalyed in the site footer. ⚠️ This parameter replaces darkToggle. The following table outlines some other key new parameters that control new features in version 2:\nNew parameter Type Default enableSearch Boolean false showScrollToTop Boolean true article.showTaxonomies Boolean false article.showTableOfContents Boolean false list.showTableOfContents Boolean false For the full list of supported parameters, refer to the Configuration docs.\nStep 4: Move assets # All site assets, with the exception of favicons, now use Hugo Pipes to build an optimised version of your project. In order for the theme to locate your files, any previously static theme assets need to be moved to the Hugo assets folder. Primarily this is the author image and site logo:\nstatic/me.jpg → assets/me.jpg\nstatic/logo.jpg → assets/logo.jpg\nIf you have provided an author image or site logo, simply move these assets from static/ to assets/. If you use the same directory structure the theme will know where to find these files automatically. If you would like to provide a new path, update the logo and author.image config values accordingly.\nNote that this step does not apply to any assets in your project that are actually static. For example, a PDF file that you link directly to from within an article is a static asset. These files should remain in the static/ directory to ensure they are copied to the output folder when Hugo builds the site.\nStep 5: Check content # The behavior of the figure shortcode is different in version 2. If you are using figure in your content and have advanced use cases, you may need to adjust the parameters you are providing.\nConsult the shortcode docs to learn more about supported parameters.\nStep 6: Rebuild # Now that all the configuration changes are complete, it\u0026rsquo;s time to rebuild the site. Run hugo, or your build command, and check that everything works as expected.\nIf you come across any errors, check the configuration is correct and refer to the full documentation for further guidance. Remember, the example config files bundled with the theme contain all the default parameters and are a great starting point.\n🙋‍♀️ If you still need help, feel free to ask your question on GitHub Discussions.\n","date":"20 January 2022","permalink":"/blowfish/docs/version-2/upgrade/","section":"Documentation","summary":"Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.\nThat said, there are some changes that require adjustments to existing sites that are built with Congo version 1.","title":"Upgrading from Congo 1.x"},{"content":" Congo 2.0 is packed with tons of new features and optimisations. The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.\nContinue reading below to discover what\u0026rsquo;s new. When you\u0026rsquo;re ready to upgrade, check out the guide to upgrading.\nTailwind CSS 3.0 # Tailwind CSS is at the heart of Congo and this new release contains the very latest Tailwind CSS version 3. It brings with it performance optimisations and support for some great new CSS features.\nImplementing this new version has also removed some Tailwind plugin dependencies from the theme, allowing the overall footprint to remain lightweight.\nMultilingual support # A highly requested feature, Congo is now multilingual! If you publish your content in multiple languages, the site will be built with all the translations available.\n🇬🇧 🇩🇪 🇫🇷 🇪🇸 🇨🇳 🇧🇷 🇹🇷 🇧🇩 Thanks to submissions from the community, Congo has already been translated into eight languages with more to be added over time. By the way, pull requests for new languages are always welcome!\nRTL language support # One of the benefits of the new Tailwind and Multilingual features is the ability to add RTL language support. When enabled, the entire site will reflow content from right-to-left. Every element in the theme has been restyled to ensure it looks great in this mode which aids authors who wish to generate content in RTL languages.\nRTL is controlled on a per-language basis so you can mix and match both RTL and LTR content in your projects and the theme will respond accordingly.\nAutomatic image resizing # A big change in Congo 2.0 is the addition of automatic image resizing. Using the power of Hugo Pipes, images in Markdown content are now automatically scaled to different output sizes. These are then presented using HTML srcset attributes enabling optimised file sizes to be served to your site visitors.\n\u0026lt;!-- Markdown: ![My image](image.jpg) --\u0026gt; \u0026lt;img srcset=\u0026#34; /image_320x0_resize_q75_box.jpg 320w, /image_635x0_resize_q75_box.jpg 635w, /image_1024x0_resize_q75_box.jpg 1024w, /image_1270x0_resize_q75_box.jpg 2x\u0026#34; src=\u0026#34;/image_635x0_resize_q75_box.jpg\u0026#34; alt=\u0026#34;My image\u0026#34; /\u0026gt; Best of all there\u0026rsquo;s nothing you need to change! Simply insert standard Markdown image syntax and let the theme do the rest. If you want a little more control, the figure shortcode has been completely rewritten to provide the same resizing benefits.\nPerformance improvements # This update packs performance improvements throughout. A key objective for this release was to improve Lighthouse scores and Congo now scores a perfect 100 on all four metrics.\nThere\u0026rsquo;s too many individual changes to highlight them here but the results speak for themselves. If you want to dig deeper, you can view the Lighthouse report. Real world performance will vary based upon server configuration.\nSite search # Powered by Fuse.js, site search allows visitors to quickly and easily find your content. All searches are performed client-side meaning there\u0026rsquo;s nothing to configure on the server and queries are performed super fast. Simply enable the feature in your site configuration and you\u0026rsquo;re all set. Oh, and it also supports full keyboard navigation!\nTables of contents # A highly requested feature, Congo now supports tables of contents on article pages. You can see it in action on this page. The contents are fully responsive and will adjust to take advantage of the space available at different screen resolutions.\nAvailable on a global or per article basis, the table of contents can be fully customised using standard Hugo configuration values, allowing you to adjust the behaviour to suit your project.\nAccessibility improvements # From adding ARIA descriptions to more items or simply adjusting the contrast of certain text elements, this release is the most accessible yet.\nVersion 2 also introduces \u0026ldquo;skip to content\u0026rdquo; and \u0026ldquo;scroll to top\u0026rdquo; links that enable quick navigation. There\u0026rsquo;s also keyboard shortcuts for enabling items like search without reaching for the mouse.\nThe new image resizing features also provide full control over alt and title elements enabling an accessible experience for all visitors.\nA whole lot more # There\u0026rsquo;s countless other minor changes to explore. From being able to display taxonomies on articles and list pages, to using the new headline author parameter to customise your homepage. There\u0026rsquo;s also improved JSON-LD strucured data which further optimises SEO performance. Plus the entire theme has had extra polish to ensure a consistent design language.\n🚀 Check out the full changelog to learn more.\nNext steps # If you\u0026rsquo;re ready to upgrade, read the upgrading from version 1 guide to get started. If you\u0026rsquo;re new to Congo, check out the Installation guide to begin a new project.\n","date":"19 January 2022","permalink":"/blowfish/docs/version-2/","section":"Documentation","summary":"Congo 2.0 is packed with tons of new features and optimisations. The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.","title":"What's New in 2.0 ✨"},{"content":"","date":"9 September 2021","permalink":"/blowfish/tags/disruption/","section":"Tags","summary":"","title":"Disruption"},{"content":"","date":"9 September 2021","permalink":"/blowfish/tags/nintendo/","section":"Tags","summary":"","title":"Nintendo"},{"content":"","date":"9 September 2021","permalink":"/blowfish/tags/switch/","section":"Tags","summary":"","title":"Switch"},{"content":" Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?\nA Little History\u0026hellip; # Nintendo is a Japanese multinational consumer electronics and video game company with headquarters in Kyoto, Japan. In its annual report for 2021, the company reported a revenue of $16 billion (¥1,759 trillion) and it currently employs around six thousand people around the world across several different business units.\nNintendo was founded in 1889 as a company that produced and distributed hanafuda, a traditional Japanese card game. During the first half of the 1900s, the company tried to diversify into several different markets with little to no success (e.g. instant rice, love hotels, and a taxi service). During the 60s to 80s, Nintendo started investing in games, electronic toys, and gaming entertainment.\nAll of these investments culminated in the 90s with the launch of the Super Nintendo Entertainment System which sold around 50 million units worldwide and helped the company enter the US market. By then Nintendo had built several valuable assets in hardware, software, and intellectual property (including the most famous plumber that ever lived, Mario).\nAfter the Super Nintendo, the company continued to release new games and gaming devices throughout the 90s and into the 00s, including the Gameboy, Nintendo 64, GameCube, and the Wii in 2006, which contributed to make Nintendo a force to be reckoned in the gaming industry with net sales that peaked at $18 billion in 2009.\nIn 2010, the previous generation of hardware Wii was approaching the end of its life cycle and coincidentally the company’s annual net sales started dropping. At the end of 2012 the company launched its next-generation gaming console that would replace the Wii, the Wii U. However, the Wii U was a commercial failure and never got a real foothold in the console market selling less than 15 million units worldwide. The platform was described as expensive, confusing and was never able to attract support from either hardcore nor casual customers leading to Nintendo\u0026rsquo;s sales eventually plummeting to just $4 billion in 2017.\n2017 was also the same year the company was able to disrupt itself and the entire gaming industry with the launch of the Nintendo Switch which until today sold more than 89 million units worldwide, led to a reported $16 billion net sales in 2021, and ultimately contributed to save Nintendo and establish it once again as one of the biggest players in the game industry.\nThe Switch\u0026rsquo;s Disruption # The Switch entered the market as the first console that was built from the ground up to provide a hybrid experience between mobile and living room gaming (or at least the first one that was actually able to deliver that experience). This hybrid setup allowed Nintendo to create different gaming modes from connecting the Switch to a TV using a dock, to connecting the controls to the main unit and taking it to play on the go. Additionally, the actual remote of the console can be used as two separate controlling devices which allows two players to enjoy a game at once. All these different modes and combinations made the switch a super attractive console for families and casual gamers since it was an affordable and flexible option when compared to the rest of the hardware available.\nA problem that Nintendo had to solve was the fact that launching a gaming console entails an interdependency between the actual hardware and its games. Or in other words, a console is only as valuable as the catalog of games available for it. To solve this problem, Nintendo adopted an integrated strategy in order to launch the Switch with a great catalog of games focusing on the same segment that the hardware features of the console were targeting. Nintendo developed several of the initial games and leveraged its valuable intellectual property of characters and stories to sell the Switch i.e. Mario, Zelda, etc.\nThe Switch is a traditional example of a new-market disruption. Nintendo was targeting casual gamers (non-consumption for the traditional gaming industry) by offering a product that was inferior when compared to the other consoles in the market using the metrics from that time (graphics power, storage, etc) but superior when using the new set of metrics important to the new segment (fun, flexible, casual, affordable, etc). The fact that the Switch was not a super powerful device led to Sony and Microsoft not seeing Nintendo as a real competitor since their performance metrics were focused on high-end gamers and AAA titles. This created an asymmetric motivation, meaning that the incumbent companies simply conceded that market to Nintendo as it was not interesting for them. Ultimately, Nintendo gained market share with the Switch selling over 80 million units worldwide. At the moment other players still do not have the incentives to compete in that market and even if they did, they would not be able to because neither of them is competing on the same performance metrics as the Switch nor with the same organization and business structure that would allow them to succeed.\nIn July 2019, Nintendo decided to launch a cheaper version of the product called the Switch Lite, this was a clear example of the company disrupting itself. Namely, Nintendo created a low-end disruption over its own product by creating a cheaper “good enough” product that targets over-served customers of the original Switch. This created a strong foothold on the low-end market for video games which is hard to compete against.\nCurrently, Nintendo and the Switch are in a phase of sustaining innovation where incremental performance improvements in attributes are provided to the more valuable/demanding customers in the market. The proof of this is the next version of the console, due to launch in October 2021, the Nintendo Switch OLED, which is basically the same as the current Switch with a bigger screen, bigger battery, and more internal storage. This makes complete sense from a strategic point of view, after defining and deploying such a successful product, Nintendo is focusing on a deliberate strategy to grow its market share and meet the needs of its best customers in order to beat the competition, not that there is actually one at the time.\nWhat\u0026rsquo;s Next for Nintendo and the Switch? # Currently, the Switch is already the 7th best selling console of all time and the 2nd best selling handheld gaming device of all time with 89 million units sold worldwide. Considering just the consoles still in the market, the Switch has already become the number 2 device in just 4 years.\nIt is expected that, for the time being, Nintendo will retain its position in the market and keep evolving the Switch and its ecosystem with new incremental improvements. Companies like Sony and Microsoft which are targeting the high-end gamer segment will not be able to compete with Nintendo due to the humongous differences in the structures of their businesses and organization. Moreover, the other organizations also do not have any incentive to try to compete in the same market as Nintendo because, from their point of view, it is a lower margin market than the one they already have which creates an asymmetric motivation for them to flee up, conceding the low-end without fighting over it. Finally, Nintendo will have a huge advantage over new competitors that tackle its segment and it has every motivation to fight the entrance of new players into its space.\nHowever, there are still points that might require course correction to avoid potential future problems. The first one is the lack of traction from other game developers and publishers in respect to the Switch. Looking at the list of the top 10 best-selling games for the platform only 2 were not developed by Nintendo or one of its subsidiaries. The Switch developer experience has a low barrier to entry (each dev kit costing around $450) but there is a 30% “tax” on each game sold taken from the developers/publishers by Nintendo. The company could potentially look at their developer relationships and explore ways to improve the business model to get a bigger catalog of games faster. A couple of examples would be to help promote games via their channels, or the creation of an indie games program to help and promote smaller companies. Ultimately, this means that in order to grow Nintendo needs to move away from its integrated strategy into a specialized one where it focuses on the most important pieces of the system and in delivering it perfectly i.e. the console, the store, and its IP. But for that, it needs to ensure the right level of modularity so that other developers and publishers can thrive in that space.\nAnother issue with the Switch is the lack of non-gaming applications available in the device that leads to a clash with the main Job-To-Be-Done for the product, “I want entertainment for me and my family”. The Switch has the potential to be the central hub for family entertainment, however, only three video streaming applications are available on the platform: Hulu, Youtube, and Funimation. Working with companies that provide other types of entertainment like Netflix and Disney and helping them launch those services on the Switch would be a great opportunity for Nintendo to improve the feature set of the device and better serve its users.\nRegarding the future, Nintendo is clearly betting on game streaming as a way to move up in the market and disrupt yet again the other players. This would be a great technology to drive the next round of low-end disruption by offering a cheaper way to play AAA games without having to own expensive hardware and upgrade it every one or two years. However, creating its own streaming service might not be the best strategy, Nintendo should look into making its system more modular and potentially partnering with other companies like Google Stadia to get access to streaming capabilities and an existing catalog of games right away.\nUltimately, the common factor across all of Nintendo’s decisions and actions has been the ability to focus on understanding and delivering against the underlying Job-To-Be-Done for its customers. The company was able to understand that the gaming experience could solve the problem (or “job”) of family or party entertainment as well as the standard problems customers hire a gaming device to solve (i.e. play games). By organizing the entire company around these jobs, Nintendo created the ability to target non-consumption and attract a completely different segment of users to its products. Moreover, by implementing an integrated strategy that delivered new hardware, developed new games, and leveraged family-friendly characters known around the world, Nintendo was able to deliver a perfect solution for the job and completely disrupt the gaming industry. In my view, this relentless focus on the customer and how to best solve its problem is why Nintendo has become a Purpose Brand that focuses on providing great family fun and entertainment using technology.\nReferences # Henderson, Rik. “What is Nintendo Switch Cloud Streaming, how does it work and what Cloud Version games are there?” Pocket-Lint\nHerold, Charles. “10 Reasons the Wii U Was a Failure.” Lifewire.\nNintendo. “Nintendo Annual Report FY 2021.”\nOrland, Kyle. “What the “OLED Model” means for the future of Nintendo Switch.” ARS Technica.\nPeckham, Matt. “19 Things Nintendo\u0026rsquo;s President Told Us About Switch and More.” Time.\nStatista. “Nintendo\u0026rsquo;s net sales from fiscal 2008 to 2021.”\nWikipedia. “List of best-selling game consoles.”\nWikipedia. “List of best-selling Nintendo Switch video games.”\n","date":"9 September 2021","permalink":"/blowfish/posts/202109-the-future-of-nintendo/","section":"Posts","summary":"Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?","title":"The Future of the Nintendo Switch"},{"content":"","date":"16 August 2020","permalink":"/blowfish/tags/installation/","section":"Tags","summary":"","title":"installation"},{"content":"Simply follow the standard Hugo Quick Start procedure to get up and running quickly.\nDetailed installation instructions can be found below. Instructions for updating the theme are also available.\nInstallation # These instructions will get you up and running using Hugo and Congo from a completely blank state. Most of the dependencies mentioned in this guide can be installed using the package manager of choice for your platform.\nInstall Hugo # If you haven\u0026rsquo;t used Hugo before, you will need to install it onto your local machine. You can check if it\u0026rsquo;s already installed by running the command hugo version.\nMake sure you are using Hugo version 0.87.0 or later as the theme takes advantage of some of the latest Hugo features. You can find detailed installation instructions for your platform in the Hugo docs.\nCreate a new site # Run the command hugo new site mywebsite to create a new Hugo site in a directory named mywebsite.\nNote that you can name the project directory whatever you choose, but the instructions below will assume it\u0026rsquo;s named mywebsite. If you use a different name, be sure to substitute it accordingly.\nDownload the Congo theme # There several different ways to install the Congo theme into your Hugo website. From easiest to most difficult to install and maintain, they are:\nHugo module (recommended) Git submodule Manual file copy If you\u0026rsquo;re unsure, choose the Hugo module method.\nInstall using Hugo # This method is the quickest and easiest for keeping the theme up-to-date. Hugo uses Go to initialise and manage modules so you need to ensure you have go installed before proceeding.\nDownload and install Go. You can check if it\u0026rsquo;s already installed by using the command go version.\nMake sure you are using Go version 1.12 or later as Hugo requires this for modules to work correctly. From your Hugo project directory (that you created above), initialise modules for your website:\n# If you\u0026#39;re managing your project on GitHub hugo mod init github.com/\u0026lt;username\u0026gt;/\u0026lt;repo-name\u0026gt; # If you\u0026#39;re managing your project locally hugo mod init my-project Add the theme to your configuration by creating a new file config/_default/module.toml and adding the following:\n[[imports]] path = \u0026#34;github.com/jpanther/congo/v2\u0026#34; Start your server using hugo server and the theme will be downloaded automatically.\nContinue to set up the theme configuration files.\nInstall using git # For this method you\u0026rsquo;ll need to ensure you have Git installed on your local machine.\nChange into the directory for your Hugo website (that you created above), initialise a new git repository and add Congo as a submodule.\ncd mywebsite git init git submodule add -b stable https://github.com/jpanther/congo.git themes/congo Then continue to set up the theme configuration files.\nInstall manually # Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder.\nContinue to set up the theme configuration files.\nSet up theme configuration files # In the root folder of your website, delete the config.toml file that was generated by Hugo. Copy the *.toml config files from the theme into your config/_default/ folder. This will ensure you have all the correct theme settings and will enable you to easily customise the theme to your needs.\nNote: You should not overwrite the module.toml file if one already exists in your project! Depending on how you installed the theme you will find the theme config files in different places:\nHugo Modules: In the Hugo cache directory, or download a copy from GitHub Git submodule or Manual install: themes/congo/config/_default Once you\u0026rsquo;ve copied the files, your config folder should look like this:\nconfig/_default/ ├─ config.toml ├─ markup.toml ├─ menus.toml ├─ module.toml # if you installed using Hugo Modules └─ params.toml Important: If you didn\u0026rsquo;t use Hugo Modules to install Congo, you must add the line theme = \u0026quot;congo\u0026quot; to the top of your config.toml file. Next steps # The basic Congo installation is now complete. Continue to the Getting Started section to learn more about configuring the theme.\nInstalling updates # From time to time there will be new releases posted that apply fixes and add new functionality to the theme. In order to take advantage of these changes, you will need to update the theme files on your website.\nHow you go about this will depend on the installation method you chose when the theme was originally installed. Instructions for each method can be found below.\nHugo module Git submodule Manual file copy Update using Hugo # Hugo makes updating modules super easy. Simply change into your project directory and execute the following command:\nhugo mod get -u Hugo will automatically update any modules that are required for your project. It does this by inspecting your module.toml and go.mod files. If you have any issues with the update, check to ensure these files are still configured correctly.\nThen simply rebuild your site and check everything works as expected.\nUpdate using git # Git submodules can be updated using the git command. Simply execute the following command and the latest version of the theme will be downloaded into your local repository:\ngit submodule update --remote --merge Once the submodule has been updated, rebuild your site and check everything works as expected.\nUpdate manually # Updating Congo manually requires you to download the latest copy of the theme and replace the old version in your project.\nNote that any local customisations you have made to the theme files will be lost during this process. Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder. You will need to overwrite the existing directory to replace all the theme files.\nRebuild your site and check everything works as expected.\n","date":"16 August 2020","permalink":"/blowfish/docs/installation/","section":"Documentation","summary":"Simply follow the standard Hugo Quick Start procedure to get up and running quickly.\nDetailed installation instructions can be found below. Instructions for updating the theme are also available.\nInstallation # These instructions will get you up and running using Hugo and Congo from a completely blank state.","title":"Installation"},{"content":" This section assumes you have already installed the Congo theme. The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.\nBasic configuration # Before creating any content, there are a few things you should set for a new installation. Starting in the config.toml file, set the baseURL and languageCode parameters. The languageCode should be set to the main language that you will be using to author your content.\n# config/_default/config.toml baseURL = \u0026#34;https://your_domain.com/\u0026#34; languageCode = \u0026#34;en\u0026#34; The next step is to configure the language settings. Although Congo supports multilingual setups, for now, just configure the main language.\nLocate the languages.en.toml file in the config folder. If your main language is English you can use this file as is. Otherwise, rename it so that it includes the correct language code in the filename. For example, for French, rename the file to languages.fr.toml.\nNote that the language code in the language config filename should match the languageCode setting in config.toml. # config/_default/languages.en.toml title = \u0026#34;My awesome website\u0026#34; [author] name = \u0026#34;My name\u0026#34; image = \u0026#34;img/author.jpg\u0026#34; headline = \u0026#34;A generally awesome human\u0026#34; bio = \u0026#34;A little bit about me\u0026#34; links = [ { twitter = \u0026#34;https://twitter.com/username\u0026#34; } ] The [author] configuration determines how the author information is displayed on the website. The image should be placed in the site\u0026rsquo;s assets/ folder. Links will be displayed in the order they are listed.\nIf you need extra detail, further information about each of these configuration options, is covered in the Configuration section.\nColour schemes # Congo ships with a number of colour schemes out of the box. To change the scheme, simply set the colorScheme theme parameter. Valid options are congo (default), avocado, fire, ocean and slate.\n# config/_default/params.toml colorScheme = \u0026#34;congo\u0026#34; Congo defines a three-colour palette that is used throughout the theme. Each main colour contains ten shades which are based upon the colours that are included in Tailwind.\nCongo (default) # Avocado # Fire # Ocean # Slate # Although these are the default schemes, you can also create your own. Refer to the Advanced Customisation section for details.\nOrganising content # By default, Congo doesn\u0026rsquo;t force you to use a particular content type. In doing so you are free to define your content as you wish. You might prefer pages for a static site, posts for a blog, or projects for a portfolio.\nHere\u0026rsquo;s a quick overview of a basic Congo project. All content is placed within the content folder:\n. ├── assets │ └── img │ └── author.jpg ├── config │ └── _default ├── content │ ├── _index.md │ ├── about.md │ └── posts │ ├── _index.md │ ├── first-post.md │ └── another-post │ ├── aardvark.jpg │ └── index.md └── themes └── congo It\u0026rsquo;s important to have a firm grasp of how Hugo expects content to be organised as the theme is designed to take full advantage of Hugo page bundles. Be sure to read the official Hugo docs for more information.\nCongo is also flexible when it comes to taxonomies. Some people prefer to use tags and categories to group their content, others prefer to use topics.\nHugo defaults to using posts, tags and categories out of the box and this will work fine if that\u0026rsquo;s what you want. If you wish to customise this, however, you can do so by creating a taxonomies.toml configuration file:\n# config/_default/taxonomies.toml topic = \u0026#34;topics\u0026#34; This will replace the default tags and categories with topics. Refer to the Hugo Taxonomy docs for more information on naming taxonomies.\nWhen you create a new taxonomy, you will need to adjust the navigation links on the website to point to the correct sections, which is covered below.\nMenus # Congo has two menus that can be customised to suit the content and layout of your site. The main menu appears in the site header and the footer menu appears at the bottom of the page just above the copyright notice.\nBoth menus are configured in the menus.en.toml file. Similarly to the languages config file, if you wish to use another language, rename this file and replace en with the language code you wish to use.\n# config/_default/menus.toml [[main]] name = \u0026#34;Blog\u0026#34; pageRef = \u0026#34;posts\u0026#34; weight = 10 [[main]] name = \u0026#34;Topics\u0026#34; pageRef = \u0026#34;topics\u0026#34; weight = 20 [[footer]] name = \u0026#34;Privacy\u0026#34; url = \u0026#34;https://external-link\u0026#34; The name parameter specifies the text that is used in the menu link. You can also optionally provide a title which fills the HTML title attribute for the link.\nThe pageRef parameter allows you to easily reference Hugo content pages and taxonomies. It is the quickest way to configure the menu as you can simply refer to any Hugo content item and it will automatically build the correct link. To link to external URLs, the url parameter can be used.\nMenu links will be sorted from lowest to highest weight, and then alphabetically by name.\nBoth menus are completely optional and can be commented out if not required. Use the template provided in the file as a guide.\nDetailed configuration # The steps above are the bare minimum configuration. If you now run hugo server you will be presented with a blank Congo website. Detailed configuration is covered in the Configuration section.\n","date":"15 August 2020","permalink":"/blowfish/docs/getting-started/","section":"Documentation","summary":"This section assumes you have already installed the Congo theme. The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.","title":"Getting Started"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/config/","section":"Tags","summary":"","title":"config"},{"content":"Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.\nThe theme ships with a default configuration that gets you up and running with a basic blog or static website.\nConfiguration 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.\nThe default theme configuration is documented in each file so you can freely adjust the settings to meet your needs.\nAs outlined in the installation instructions, you should adjust your theme configuration by modifying the files in the config/_default/ folder of your Hugo project and delete the config.toml file in your project root. Site configuration # Standard Hugo configuration variables are respected throughout the theme, however there are some specific things that should be configured for the best experience.\nThe site configuration is managed through the config/_default/config.toml file. The table below outlines all the settings that the Congo takes advantage of.\nNote that the variable names provided in this table use dot notation to simplify the TOML data structure (ie. outputs.home refers to [outputs] home).\nName Default Description theme \u0026quot;congo\u0026quot; When using Hugo Modules this config value should be removed. For all other installation types, this must be set to congo for the theme to function. baseURL Not set The URL to the root of the website. defaultContentLanguage \u0026quot;en\u0026quot; This value determines the default language of theme components and content. Refer to the language and i18n section below for supported language codes. enableRobotsTXT true When enabled, a robots.txt file will be created in the site root that allows search engines to crawl the entire site. If you prefer to provide your own pre-made robots.txt, set to false and place your file in the static directory. For complete control, you may provide a custom layout to generate this file. paginate 10 The number of articles listed on each page of the article listing. summaryLength 0 The number of words that are used to generate the article summary when one is not provided in the front matter. A value of 0 will use the first sentence. This value has no effect when summaries are hidden. outputs.home [\u0026quot;HTML\u0026quot;, \u0026quot;RSS\u0026quot;, \u0026quot;JSON\u0026quot;] The output formats that are generated for the site. Congo requires HTML, RSS and JSON for all theme components to work correctly. permalinks Not set Refer to the Hugo docs for permalink configuration. taxonomies Not set Refer to the Organising content section for taxonomy configuration. Language and i18n # Congo is optimised for full multilingual websites and theme assets are translated into several languages out of the box. The language configuration allows you to generate multiple versions of your content to provide a customised experience to your visitors in their native language.\nThe theme currently supports the following languages by default:\nLanguage Code 🇬🇧 English en 🇧🇩 Bengali bn 🇨🇳 Simplified Chinese (China) zh-cn 🇹🇼 Traditional Chinese (Taiwan) zh-tw 🇫🇮 Finnish fi 🇫🇷 French fr 🇩🇪 German de 🇮🇱 Hebrew he 🇭🇺 Hungarian hu 🇮🇹 Italian it 🇯🇵 Japanese ja 🇧🇷 Portuguese (Brazil) pt-br 🇵🇹 Portuguese (Portugal) pt-pt 🇷🇴 Romanian ro 🇪🇸 Spanish (Spain) es 🇹🇷 Turkish tr The default translations can be overridden by creating a custom file in i18n/[code].yaml that contains the translation strings. You can also use this method to add new languages. If you\u0026rsquo;d like to share a new translation with the community, please open a pull request.\nConfiguration # In order to be as flexible as possible, a language configuration file needs to be created for each language on the website. By default Congo includes an English language configuration at config/_default/languages.en.toml.\nThe default file can be used as a template to create additional languages, or renamed if you wish to author your website in a language other than English. Simply name the file using the format languages.[language-code].toml.\nNote: Ensure the defaultContentLanguage parameter in the site configuration matches the language code in your language config filename. Name Default Description languageCode \u0026quot;en\u0026quot; The Hugo language code for this file. It can be a top-level language (ie. en) or a sub-variant (ie. en-au) and should match the language code in the filename. Hugo expects this value to always be in lowercase. For proper HTML compliance, set the isoCode parameter which is case-sensitive. languageName \u0026quot;English\u0026quot; The name of the language. displayName \u0026quot;EN\u0026quot; The name used when the language appears on the website. isoCode \u0026quot;en\u0026quot; The ISO language code for HTML metadata purposes. It can be a top-level language (ie. en) or a sub-variant (ie. en-AU). weight 1 The weight determines the order of languages when building multilingual sites. rtl false Whether or not this is a RTL language. Set to true to reflow content from right-to-left. Congo fully supports using RTL and LTR languages at the same time and will dynamically adjust to both. dateFormat \u0026quot;2 January 2006\u0026quot; How dates are formatted in this language. Refer to the Hugo docs for acceptable formats. title \u0026quot;Congo\u0026quot; The title of the website. This will be displayed in the site header and footer. description Not set The website description. This will be used in the site metadata. copyright Not set 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 title. author.name Not set The author\u0026rsquo;s name. This will be displayed in article footers, and on the homepage when the profile layout is used. author.image Not set Path to the image file of the author. The image should be a 1:1 aspect ratio and placed in the site\u0026rsquo;s assets/ folder. author.headline Not set A Markdown string containing the author\u0026rsquo;s headline. It will be displayed on the profile homepage under the author\u0026rsquo;s name. author.bio Not set A Markdown string containing the author\u0026rsquo;s bio. It will be displayed in article footers. author.links Not set The links to display alongside the author\u0026rsquo;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 assets/icons/. Menus # Congo also supports language-specific menu configurations. Menu config files follow the same naming format as the languages file. Simply provide the language code in the file name to tell Hugo which language the file relates to.\nMenu config files are named with the format menus.[language-code].toml. Always ensure that the language code used in the menus configuration matches the languages configuration.\nThe Getting Started section explains more about the structure of this file. You can also refer to the Hugo menu docs for more configuration examples.\nTheme parameters # Congo provides a large number of configuration parameters that control how the theme functions. The table below outlines every available parameter in the config/_default/params.toml file.\nMany of the article defaults here can be overridden on a per article basis by specifying it in the front matter. Refer to the Front Matter section for further details.\nName Default Description colorScheme \u0026quot;congo\u0026quot; The theme colour scheme to use. Valid values are congo (default), avocado, ocean, fire and slate. Refer to the Colour Schemes section for more details. defaultAppearance \u0026quot;light\u0026quot; The default theme appearance, either light or dark. autoSwitchAppearance true Whether the theme appearance automatically switches based upon the visitor\u0026rsquo;s operating system preference. Set to false to force the site to always use the defaultAppearance. enableSearch false Whether site search is enabled. Set to true to enable search functionality. Note that the search feature depends on the outputs.home setting in the site configuration being set correctly. enableCodeCopy false Whether copy-to-clipboard buttons are enabled for \u0026lt;code\u0026gt; blocks. The highlight.noClasses parameter must be set to false for code copy to function correctly. Read more about other configuration files below. logo Not set The relative path to the site logo file within the assets/ folder. The logo file should be provided at 2x resolution and supports any image dimensions. mainSections Not set The sections that should be displayed in the recent articles list. If not provided the section with the greatest number of articles is used. robots Not set String that indicates how robots should handle your site. If set, it will be output in the page head. Refer to Google\u0026rsquo;s docs for valid values. header.layout \u0026quot;basic\u0026quot; The layout of the page header and menu. Valid values are basic, hamburger or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/header/custom.html file. footer.showCopyright true Whether or not to show the copyright string in the site footer. Note that the string itself can be customised using the copyright parameter in the languages configuration. footer.showThemeAttribution true Whether or not to show the \u0026ldquo;powered by\u0026rdquo; theme attribution in the site footer. If you choose to disable this message, please consider attributing the theme somewhere else on your site (for example, on your about page). footer.showAppearanceSwitcher false Whether or not to show the appearance switcher in the site footer. The browser\u0026rsquo;s local storage is used to persist the visitor\u0026rsquo;s preference. footer.showScrollToTop true When set to true the scroll to top arrow is displayed. homepage.layout \u0026quot;page\u0026quot; The layout of the homepage. Valid values are page, profile or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/home/custom.html file. Refer to the Homepage Layout section for more details. homepage.showRecent false Whether or not to display the recent articles list on the homepage. article.showDate true Whether or not article dates are displayed. article.showDateUpdated false Whether or not the dates articles were updated are displayed. article.showAuthor true Whether or not the author box is displayed in the article footer. article.showBreadcrumbs false Whether or not breadcrumbs are displayed in the article header. article.showDraftLabel true Whether or not the draft indicator is shown next to articles when site is built with --buildDrafts. article.showEdit false Whether or not the link to edit the article content should be displayed. article.editURL Not set When article.showEdit is active, the URL for the edit link. article.editAppendPath true When article.showEdit is active, whether or not the path to the current article should be appended to the URL set at article.editURL. article.showHeadingAnchors true Whether or not heading anchor links are displayed alongside headings within articles. article.showPagination true Whether or not the next/previous article links are displayed in the article footer. article.invertPagination false Whether or not to flip the direction of the next/previous article links. article.showReadingTime true Whether or not article reading times are displayed. article.showTableOfContents false Whether or not the table of contents is displayed on articles. article.showTaxonomies false Whether or not the taxonomies related to this article are displayed. article.showWordCount false Whether or not article word counts are displayed. article.showComments false Whether or not the comments partial is included after the article footer. article.sharingLinks Not set Which sharing links to display at the end of each article. When not provided, or set to false no links will be displayed. list.showBreadcrumbs false Whether or not breadcrumbs are displayed in the header on list pages. list.showTableOfContents false Whether or not the table of contents is displayed on list pages. list.showSummary false Whether or not article summaries are displayed on list pages. If a summary is not provided in the front matter, one will be auto generated using the summaryLength parameter in the site configuration. list.groupByYear true Whether or not articles are grouped by year on list pages. sitemap.excludedKinds [\u0026quot;taxonomy\u0026quot;, \u0026quot;term\u0026quot;] Kinds of content that should be excluded from the generated /sitemap.xml file. Refer to the Hugo docs for acceptable values. taxonomy.showTermCount true Whether or not the number of articles within a taxonomy term is displayed on the taxonomy listing. fathomAnalytics.site Not set The site code generated by Fathom Analytics for the website. Refer to the Analytics docs for more details. fathomAnalytics.domain Not set If using a custom domain with Fathom Analytics, provide it here to serve script.js from the custom domain. verification.google Not set The site verification string provided by Google to be included in the site metadata. verification.bing Not set The site verification string provided by Bing to be included in the site metadata. verification.pinterest Not set The site verification string provided by Pinterest to be included in the site metadata. verification.yandex Not set The site verification string provided by Yandex to be included in the site metadata. Other configuration files # The theme also includes a markup.toml configuration file. This file contains some important parameters that ensure that Hugo is correctly configured to generate sites built with Congo.\nAlways ensure this file is present in the config directory and that the required values are set. Failure to do so may cause certain features to fucntion incorrectly and could result in unintended behaviour.\n","date":"14 August 2020","permalink":"/blowfish/docs/configuration/","section":"Documentation","summary":"Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.\nThe theme ships with a default configuration that gets you up and running with a basic blog or static website.","title":"Configuration"},{"content":" Congo brings your content to life. 😍 This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.\nSidenote: This page is just a standard Congo article listing and Hugo has been configured to generate a samples content type and display article summaries.\n","date":"14 August 2020","permalink":"/blowfish/samples/","section":"Content Samples","summary":"Congo brings your content to life. 😍 This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.","title":"Content Samples"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/icons/","section":"Tags","summary":"","title":"icons"},{"content":"Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.\nAdditionally, custom icons are also fully supported. Simply provide your own SVG icon assets by placing them in the assets/icons/ directory in the root of your project. Any icons in the icons directory will then be available to use throughout the theme.\nThe full list of built-in icons and their corresponding names can referenced below.\nIcon name Preview amazon apple bars blogger bug check circle-info codepen comment dev dribbble edit email facebook flickr foursquare github gitlab google hashnode instagram keybase kickstarter lastfm lightbulb link linkedin list mastodon medium microsoft moon orcid patreon pencil pinterest reddit researchgate search skull-crossbones slack snapchat soundcloud stack-overflow steam sun tag telegram tiktok triangle-exclamation tumblr twitch twitter whatsapp xmark youtube ","date":"14 August 2020","permalink":"/blowfish/samples/icons/","section":"Content Samples","summary":"Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.\nAdditionally, custom icons are also fully supported.","title":"Icons"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/sample/","section":"Tags","summary":"","title":"sample"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/shortcodes/","section":"Tags","summary":"","title":"shortcodes"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/users/","section":"Tags","summary":"","title":"users"},{"content":" Real websites that are built with Congo. Website Details jamespanther.com Personal site - Theme author srisco.dev Personal site antoinesoetewey.com Personal site leif.io Personal site and Tech blog dr460nf1r3.org Personal site and Blog OCram85.com Personal site and Blog mackiser.github.io Personal site and Blog jamesmillner.dev Personal site and Blog jeremic.ca Personal site and Blog rohn.tech Personal site klimafreundlicher-kochen.de Food blog (in German) seyslee.github.io Tech blog (in Korean) datanalyze.be Professional site sneaky-potato.github.io Professional site and Blog kelset.dev Personal site docteurelsavancaster.com Professional site ruihao-li.github.io Personal site and Blog phalanxhead.dev Personal site and Blog Bible Multi Apps Personal site and Blog Jh123x Personal site and Blog sforzando LLC. and Inc. Corporate site and Blog Congo user? To add your site to this list, submit a pull request.\n","date":"14 August 2020","permalink":"/blowfish/users/","section":"Blowfish","summary":"Real websites that are built with Congo. Website Details jamespanther.com Personal site - Theme author srisco.dev Personal site antoinesoetewey.com Personal site leif.io Personal site and Tech blog dr460nf1r3.org Personal site and Blog OCram85.","title":"Users"},{"content":"","date":"13 August 2020","permalink":"/blowfish/tags/homepage/","section":"Tags","summary":"","title":"homepage"},{"content":"Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.\nThe layout of the homepage is controlled by the homepage.layout setting in the params.toml configuration file. Additionally, all layouts have the option to include a listing of recent articles.\nPage layout # The default layout is the page layout. It\u0026rsquo;s simply a normal content page that displays your Markdown content. It\u0026rsquo;s great for static websites and provides a lot of flexibility.\nTo enable the page layout, set homepage.layout = \u0026quot;page\u0026quot; in the params.toml configuration file.\nProfile layout # The profile layout is great for personal websites and blogs. It puts the author\u0026rsquo;s details front and centre by providing an image and links to social profiles.\nThe author information is provided in the languages configuration file. Refer to the Getting Started and Language Configuration sections for parameter details.\nAdditionally, any Markdown content that is provided in the homepage content will be placed below the author profile. This allows extra flexibility for displaying a bio or other custom content using shortcodes.\nTo enable the profile layout, set homepage.layout = \u0026quot;profile\u0026quot; in the params.toml configuration file.\nCustom layout # If the built-in homepage layouts aren\u0026rsquo;t sufficient for your needs, you have the option to provide your own custom layout. This allows you to have total control over the page content and essentially gives you a blank slate to work with.\nTo enable the custom layout, set homepage.layout = \u0026quot;custom\u0026quot; in the params.toml configuration file.\nWith the configuration value set, create a new custom.html file and place it in layouts/partials/home/custom.html. Now whatever is in the custom.html file will be placed in the content area of the site homepage. You may use whatever HTML, Tailwind, or Hugo templating functions you wish to define your layout.\nTo include recent articles on the custom layout, use the recent-articles.html partial.\nAs an example, the homepage on this site uses the custom layout to allow toggling between the profile and page layouts. Visit the GitHub repo to see how it works.\nRecent articles # All homepage layouts have the option of displaying recent articles below the main page content. To enable this, simply set the homepage.showRecent setting to true in the params.toml configuration file.\nThe articles listed in this section are derived from the mainSections setting which allows for whatever content types you are using on your website. For instance, if you had content sections for posts and projects you could set this setting to [\u0026quot;posts\u0026quot;, \u0026quot;projects\u0026quot;] and all the articles in these two sections would be used to populate the recent list. The theme expects this setting to be an array so if you only use one section for all your content, you should set this accordingly: [\u0026quot;blog\u0026quot;].\n","date":"13 August 2020","permalink":"/blowfish/docs/homepage-layout/","section":"Documentation","summary":"Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.","title":"Homepage Layout"},{"content":"","date":"13 August 2020","permalink":"/blowfish/tags/layouts/","section":"Tags","summary":"","title":"layouts"},{"content":"","date":"12 August 2020","permalink":"/blowfish/tags/front-matter/","section":"Tags","summary":"","title":"front matter"},{"content":"In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.\nFront matter parameter default values are inherited from the theme\u0026rsquo;s base configuration, so you only need to specify these parameters in your front matter when you want to override the default.\nName Default Description title Not set The name of the article. description Not set The text description for the article. It is used in the HTML metadata. externalUrl Not set If this article is published on a third-party website, the URL to this article. Providing a URL will prevent a content page being generated and any references to this article will link directly to the third-party website. editURL article.editURL When showEdit is active, the URL for the edit link. editAppendPath article.editAppendPath When showEdit is active, whether or not the path to the current article should be appended to the URL set at editURL. groupByYear list.groupByYear Whether or not articles are grouped by year on list pages. menu Not set When a value is provided, a link to this article will appear in the named menus. Valid values are main or footer. robots Not set String that indicates how robots should handle this article. If set, it will be output in the page head. Refer to Google\u0026rsquo;s docs for valid values. sharingLinks article.sharingLinks Which sharing links to display at the end of this article. When not provided, or set to false no links will be displayed. showAuthor article.showAuthor Whether or not the author box is displayed in the article footer. showBreadcrumbs article.showBreadcrumbs or list.showBreadcrumbs Whether the breadcrumbs are displayed in the article or list header. showDate article.showDate Whether or not the article date is displayed. The date is set using the date parameter. showDateUpdated article.showDateUpdated Whether or not the date the article was updated is displayed. The date is set using the lastmod parameter. showEdit article.showEdit Whether or not the link to edit the article content should be displayed. showHeadingAnchors article.showHeadingAnchors Whether or not heading anchor links are displayed alongside headings within this article. showPagination article.showPagination Whether or not the next/previous article links are displayed in the article footer. invertPagination article.invertPagination Whether or not to flip the direction of the next/previous article links. showReadingTime article.showReadingTime Whether or not the article reading time is displayed. showTaxonomies article.showTaxonomies Whether or not the taxonomies that relate to this article are displayed. showTableOfContents article.showTableOfContents Whether or not the table of contents is displayed on this article. showWordCount article.showWordCount Whether or not the article word count is displayed. showComments article.showComments Whether or not the comments partial is included after the article footer. showSummary list.showSummary Whether or not the article summary should be displayed on list pages. summary Auto generated using summaryLength (see site configuration) When showSummary is enabled, this is the Markdown string to be used as the summary for this article. xml true unless excluded by sitemap.excludedKinds Whether or not this article is included in the generated /sitemap.xml file. ","date":"12 August 2020","permalink":"/blowfish/docs/front-matter/","section":"Documentation","summary":"In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.","title":"Front Matter"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/icon/","section":"Tags","summary":"","title":"icon"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/lead/","section":"Tags","summary":"","title":"lead"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/mermaid/","section":"Tags","summary":"","title":"mermaid"},{"content":"In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.\nAlert # alert outputs its contents as a stylised message box within your article. It\u0026rsquo;s useful for drawing attention to important information that you don\u0026rsquo;t want the reader to miss.\nThe input is written in Markdown so you can format it however you please.\nBy default, the alert is presented with an exclaimation triangle icon. To change the icon, include the icon name in the shortcode. Check out the icon shortcode for more details on using icons.\nExample:\n{{\u0026lt; alert \u0026gt;}} **Warning!** This action is destructive! {{\u0026lt; /alert \u0026gt;}} {{\u0026lt; alert \u0026#34;twitter\u0026#34; \u0026gt;}} Don\u0026#39;t forget to [follow me](https://twitter.com/jpanther) on Twitter. {{\u0026lt; /alert \u0026gt;}} Warning! This action is destructive! Don\u0026rsquo;t forget to follow me on Twitter. Badge # badge outputs a styled badge component which is useful for displaying metadata.\nExample:\n{{\u0026lt; badge \u0026gt;}} New article! {{\u0026lt; /badge \u0026gt;}} New article! Button # button outputs a styled button component which can be used to highlight a primary action. It has two optional variables href and target which can be used to specify the URL and target of the link.\nExample:\n{{\u0026lt; button href=\u0026#34;#button\u0026#34; target=\u0026#34;_self\u0026#34; \u0026gt;}} Call to action {{\u0026lt; /button \u0026gt;}} Call to action Chart # chart uses the Chart.js library to embed charts into articles using simple structured data. It supports a number of different chart styles and everything can be configured from within the shortcode. Simply provide the chart parameters between the shortcode tags and Chart.js will do the rest.\nRefer to the official Chart.js docs for details on syntax and supported chart types.\nExample:\n{{\u0026lt; chart \u0026gt;}} type: \u0026#39;bar\u0026#39;, data: { labels: [\u0026#39;Tomato\u0026#39;, \u0026#39;Blueberry\u0026#39;, \u0026#39;Banana\u0026#39;, \u0026#39;Lime\u0026#39;, \u0026#39;Orange\u0026#39;], datasets: [{ label: \u0026#39;# of votes\u0026#39;, data: [12, 19, 3, 5, 2, 3], }] } {{\u0026lt; /chart \u0026gt;}} You can see some additional Chart.js examples on the charts samples page.\nFigure # Congo includes a figure shortcode for adding images to content. The shortcode replaces the base Hugo functionality in order to provide additional performance benefits.\nWhen a provided image is a page resource, it will be optimised using Hugo Pipes and scaled in order to provide images appropriate to different device resolutions. If a static asset or URL to an external image is provided, it will be included as-is without any image processing by Hugo.\nThe figure shortcode accepts six parameters:\nParameter Description src Required. The local path/filename or URL of the image. When providing a path and filename, the theme will attempt to locate the image using the following lookup order: Firstly, as a page resource bundled with the page; then an asset in the assets/ directory; then finally, a static image in the static/ directory. alt Alternative text description for the image. caption Markdown for the image caption, which will be displayed below the image. class Additional CSS classes to apply to the image. href URL that the image should be linked to. default Special parameter to revert to default Hugo figure behaviour. Simply provide default=true and then use normal Hugo shortcode syntax. Congo also supports automatic conversion of images included using standard Markdown syntax. Simply use the following format and the theme will handle the rest:\n![Alt text](image.jpg \u0026#34;Image caption\u0026#34;) Example:\n{{\u0026lt; figure src=\u0026#34;abstract.jpg\u0026#34; alt=\u0026#34;Abstract purple artwork\u0026#34; caption=\u0026#34;Photo by [Jr Korpa](https://unsplash.com/@jrkorpa) on [Unsplash](https://unsplash.com/)\u0026#34; \u0026gt;}} \u0026lt;!-- OR --\u0026gt; ![Abstract purple artwork](abstract.jpg \u0026#34;Photo by [Jr Korpa](https://unsplash.com/@jrkorpa) on [Unsplash](https://unsplash.com/)\u0026#34;) Photo by Jr Korpa on Unsplash Icon # icon outputs an SVG icon and takes the icon name as its only parameter. The icon is scaled to match the current text size.\nExample:\n{{\u0026lt; icon \u0026#34;github\u0026#34; \u0026gt;}} Output: Icons are populated using Hugo pipelines which makes them very flexible. Congo includes a number of built-in icons for social, links and other purposes. Check the icon samples page for a full list of supported icons.\nCustom icons can be added by providing your own icon assets in the assets/icons/ directory of your project. The icon can then be referenced in the shortcode by using the SVG filename without the .svg extension.\nIcons can also be used in partials by calling the icon partial.\nKatex # The katex shortcode can be used to add mathematical expressions to article content using the KaTeX package. Refer to the online reference of supported TeX functions for the available syntax.\nTo include mathematical expressions in an article, simply place the shortcode anywhere with the content. It only needs to be included once per article and KaTeX will automatically render any markup on that page. Both inline and block notation are supported.\nInline notation can be generated by wrapping the expression in \\\\( and \\\\) delimiters. Alternatively, block notation can be generated using $$ delimiters.\nExample:\n{{\u0026lt; katex \u0026gt;}} \\\\(f(a,b,c) = (a^2+b^2+c^2)^3\\\\) \\(f(a,b,c) = (a^2+b^2+c^2)^3\\)\nCheck out the mathematical notation samples page for more examples.\nLead # lead is used to bring emphasis to the start of an article. It can be used to style an introduction, or to call out an important piece of information. Simply wrap any Markdown content in the lead shortcode.\nExample:\n{{\u0026lt; lead \u0026gt;}} When life gives you lemons, make lemonade. {{\u0026lt; /lead \u0026gt;}} When life gives you lemons, make lemonade. Mermaid # mermaid allows you to draw detailed diagrams and visualisations using text. It uses Mermaid under the hood and supports a wide variety of diagrams, charts and other output formats.\nSimply write your Mermaid syntax within the mermaid shortcode and let the plugin do the rest.\nRefer to the official Mermaid docs for details on syntax and supported diagram types.\nExample:\n{{\u0026lt; mermaid \u0026gt;}} graph LR; A[Lemons]--\u0026gt;B[Lemonade]; B--\u0026gt;C[Profit] {{\u0026lt; /mermaid \u0026gt;}} graph LR; A[Lemons]--\u003eB[Lemonade]; B--\u003eC[Profit] You can see some additional Mermaid examples on the diagrams and flowcharts samples page.\n","date":"11 August 2020","permalink":"/blowfish/docs/shortcodes/","section":"Documentation","summary":"In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.\nAlert # alert outputs its contents as a stylised message box within your article. It\u0026rsquo;s useful for drawing attention to important information that you don\u0026rsquo;t want the reader to miss.","title":"Shortcodes"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/analytics/","section":"Tags","summary":"","title":"analytics"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/comments/","section":"Tags","summary":"","title":"comments"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/favicons/","section":"Tags","summary":"","title":"favicons"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/partials/","section":"Tags","summary":"","title":"partials"},{"content":"Analytics # Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you\u0026rsquo;re interested you can use this affiliate link to receive $10 credit and try the service.\nFathom Analytics # To enable Fathom Analytics support, simply provide your Fathom site code in the config/_default/params.toml file. If you also use the custom domain feature of Fathom and would like to serve their script from your domain, you can also additionally provide the domain configuration value. If you don\u0026rsquo;t provide a domain value, the script will load directly from Fathom DNS.\n# config/_default/params.toml [fathomAnalytics] site = \u0026#34;ABC12345\u0026#34; domain = \u0026#34;llama.yoursite.com\u0026#34; Google Analytics # Google Analytics support is provided through the internal Hugo partial. Simply provide the googleAnalytics key in the config/_default/config.toml file and the script will be added automatically.\nBoth version 3 (analytics.js) and version 4 (gtag.js) are supported, based on the configuration value provided:\n# config/_default/config.toml # version 3 googleAnalytics = \u0026#34;UA-PROPERTY_ID\u0026#34; # version 4 googleAnalytics = \u0026#34;G-MEASUREMENT_ID\u0026#34; Custom analytics providers # If you wish to use a different analytics provider on your website you can also override the analytics partial and provide your own script. Simply create the file layouts/partials/analytics.html in your project and it will automatically include it in the \u0026lt;head\u0026gt; of the website.\nComments # To add comments to your articles, Congo includes support for a comments partial that is included at the base of each article page. Simply provide a layouts/partials/comments.html which contains the code required to display your chosen comments.\nYou can use either the built-in Hugo Disqus template, or provide your own custom code. Refer to the Hugo docs for further information.\nOnce the partial has been provided, finer control over where comments are displayed is then managed using the showComments parameter. This value can be set at the theme level in the params.toml config file, or on a per-article basis by including it in the front matter. The parameter defaults to false so it must be set to true in one of these locations in order for comments to be displayed.\nFavicons # Congo provides a default set of blank favicons to get started but you can provide your own assets to override them. The easiest way to obtain new favicon assets is to generate them using a third-party provider like favicon.io.\nIcon assets should be placed directly in the static/ folder of your website and named as per the listing below. If you use favicon.io, these will be the filenames that are automatically generated for you, but you can provide your own assets if you wish.\nstatic/ ├─ android-chrome-192x192.png ├─ android-chrome-512x512.png ├─ apple-touch-icon.png ├─ favicon-16x16.png ├─ favicon-32x32.png ├─ favicon.ico └─ site.webmanifest Alternatively, you can also completely override the default favicon behaviour and provide your own favicon HTML tags and assets. Simply provide a layouts/partials/favicons.html file in your project and this will be injected into the site \u0026lt;head\u0026gt; in place of the default assets.\nIcon # Similar to the icon shortcode, you can include icons in your own templates and partials by using Congo\u0026rsquo;s icon.html partial. The partial takes one parameter which is the name of the icon to be included.\nExample:\n{{ partial \u0026#34;icon.html\u0026#34; \u0026#34;github\u0026#34; }} Icons are populated using Hugo pipelines which makes them very flexible. Congo includes a number of built-in icons for social, links and other purposes. Check the icon samples page for a full list of supported icons.\nCustom icons can be added by providing your own icon assets in the assets/icons/ directory of your project. The icon can then be referenced in the partial by using the SVG filename without the .svg extension.\nIcons can also be used in article content by calling the icon shortcode.\nExtensions # Congo also provides for a number of extension partials that allow for expanding upon base functionality.\nArticle link # If you wish to insert additional code after article links, create a layouts/partials/extend-article-link.html file. This is especially powerful when combined with the badge shortcode which can be used to highlight metadata for certain articles.\nHead and Footer # The theme allows for inserting additional code directly into the \u0026lt;head\u0026gt; and \u0026lt;footer\u0026gt; sections of the template. These can be useful for providing scripts or other logic that isn\u0026rsquo;t part of the theme.\nSimply create either layouts/partials/extend-head.html or layouts/partials/extend-footer.html and these will automatically be included in your website build. Both partials are injected as the last items in \u0026lt;head\u0026gt; and \u0026lt;footer\u0026gt; so they can be used to override theme defaults.\n","date":"10 August 2020","permalink":"/blowfish/docs/partials/","section":"Documentation","summary":"Analytics # Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you\u0026rsquo;re interested you can use this affiliate link to receive $10 credit and try the service.","title":"Partials"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/privacy/","section":"Tags","summary":"","title":"privacy"},{"content":"","date":"9 August 2020","permalink":"/blowfish/tags/content/","section":"Tags","summary":"","title":"content"},{"content":"If you\u0026rsquo;ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.\nTip: If you\u0026rsquo;re new to Hugo, be sure to check out the official docs to learn more about the concept of page bundles and resources. The examples on this page can all be adapted to different scenarios but hopefully give you some ideas about how to approach formatting a particular content item for your individual project.\nBranch pages # Branch page bundles in Hugo cover items like the homepage, section listings, and taxonomy pages. The important thing to remember about branch bundles is that the filename for this content type is _index.md.\nCongo will honour the front matter parameters specified in branch pages and these will override the default settings for that particular page. For example, setting the title parameter in a branch page will allow overriding the page title.\nHomepage # Layout: layouts/index.html Content: content/_index.md The homepage in Congo is special in that it\u0026rsquo;s overarching design is controlled by the homepage layout config parameter. You can learn more about this in the Homepage Layout section.\nIf you want to add custom content to this page, you simply need to create a content/_index.md file. Anything in this file will then be included in your homepage.\nExample:\n--- title: \u0026#34;Welcome to Congo!\u0026#34; description: \u0026#34;This is a demo of adding content to the homepage.\u0026#34; --- Welcome to my website! I\u0026#39;m really happy you stopped by. This example sets a custom title and adds some additional text to the body of the page. Any Markdown formatted text is acceptable, including shortcodes, images and links.\nList pages # Layout: layouts/_default/list.html Content: content/../_index.md List pages group all the pages within into a section and provide a way for visitors to reach each page. A blog or portfolio are examples of a list page as they group together posts or projects.\nCreating a list page is as simple as making a sub-directory in the content folder. For example, to create a \u0026ldquo;Projects\u0026rdquo; section, you would create content/projects/. Then create a Markdown file for each of your projects.\nA list page will be generated by default, however to customise the content, you should also create an _index.md page in this new directory.\n. └── content └── projects ├── _index.md # /projects ├── first-project.md # /projects/first-project └── another-project ├── index.md # /projects/another-project └── project.jpg Hugo will generate URLs for the pages in your projects folder accordingly.\nJust like the homepage, content in the _index.md file will be output into the generated list index. Congo will then list any pages in this section below the content.\nExample:\n--- title: \u0026#34;Projects\u0026#34; description: \u0026#34;Learn about some of my projects.\u0026#34; cascade: showReadingTime: false --- This section contains all my current projects. In this example, the special cascade parameter is being used to hide the reading time on any sub-pages within this section. By doing this, any project pages will not have their reading time showing. This is a great way to override default theme parameters for an entire section without having to include them in every individual page.\nThe samples section of this site is an example of a list page.\nTaxonomy pages # List layout: layouts/_default/taxonomy.html Term layout: layouts/_default/term.html Content: content/../_index.md Taxonomy pages come in two forms - taxonomy lists and taxonomy terms. Lists display a listing of each of the terms within a given taxonomy, while terms display a list of pages that are related to a given term.\nThe terminology can get a little confusing so let\u0026rsquo;s explore an example using a taxonomy named animals.\nFirstly, to use taxonomies in Hugo, they have to be configured. This is done by creating a config file at config/_default/taxonomies.toml and defining the taxonomy name.\n# config/_default/taxonomies.toml animal = \u0026#34;animals\u0026#34; Hugo expects taxonomies to be listed using their singular and plural forms, so we add the singular animal equals the plural animals to create our example taxonomy.\nNow that our animals taxonomy exists, it needs to be added to individual content items. It\u0026rsquo;s as simple as inserting it into the front matter:\n--- title: \u0026#34;Into the Lion\u0026#39;s Den\u0026#34; description: \u0026#34;This week we\u0026#39;re learning about lions.\u0026#34; animals: [\u0026#34;lion\u0026#34;, \u0026#34;cat\u0026#34;] --- This has now created two terms within our animals taxonomy - lion and cat.\nAlthough it\u0026rsquo;s not obvious at this point, Hugo will now be generating list and term pages for this new taxonomy. By default the listing can be accessed at /animals/ and the term pages can be found at /animals/lion/ and /animals/cat/.\nThe list page will list all the terms contained within the taxonomy. In this example, navigating to /animals/ will show a page that has links for \u0026ldquo;lion\u0026rdquo; and \u0026ldquo;cat\u0026rdquo; which take visitors to the individual term pages.\nThe term pages will list all the pages contained within that term. These term lists are essentially the same as normal list pages and behave in much the same way.\nIn order to add custom content to taxonomy pages, simply create _index.md files in the content folder using the taxonomy name as the sub-directory name.\n. └── content └── animals ├── _index.md # /animals └── lion └── _index.md # /animals/lion Anything in these content files will now be placed onto the generated taxonomy pages. As with other content, the front matter variables can be used to override defaults. In this way you could have a tag named lion but override the title to be \u0026ldquo;Lion\u0026rdquo;.\nTo see how this looks in reality, check out the tags taxonomy listing on this site.\nLeaf pages # Layout: layouts/_default/single.html Content (standalone): content/../page-name.md Content (bundled): content/../page-name/index.md Leaf pages in Hugo are basically standard content pages. They are defined as pages that don\u0026rsquo;t contain any sub-pages. These could be things like an about page, or an individual blog post that lives in the blog section of the website.\nThe most important thing to remember about leaf pages is that unlike branch pages, leaf pages should be named index.md without an underscore. Leaf pages are also special in that they can be grouped together at the top level of the section and named with a unique name.\n. └── content └── blog ├── first-post.md # /blog/first-post ├── second-post.md # /blog/second-post └── third-post ├── index.md # /blog/third-post └── image.jpg When including assets in a page, like an image, a page bundle should be used. Page bundles are created using a sub-directory with an index.md file. Grouping the assets with the content in its own directory is important as many of the shortcodes and other theme logic assumes that resources are bundled alongside pages.\nExample:\n--- title: \u0026#34;My First Blog Post\u0026#34; date: 2022-01-25 description: \u0026#34;Welcome to my blog!\u0026#34; summary: \u0026#34;Learn more about me and why I am starting this blog.\u0026#34; tags: [\u0026#34;welcome\u0026#34;, \u0026#34;new\u0026#34;, \u0026#34;about\u0026#34;, \u0026#34;first\u0026#34;] --- _This_ is the content of my blog post. Leaf pages have a wide variety of front matter parameters that can be used to customise how they are displayed.\nExternal links # Congo has a special feature that allows links to external pages to appear alongside articles in the article listings. This is useful if you have content on third party websites like Medium, or research papers that you\u0026rsquo;d like to link to, without replicating the content in your Hugo site.\nIn order to create an external link article, some special front matter needs to be set:\n--- title: \u0026#34;My Medium post\u0026#34; date: 2022-01-25 externalUrl: \u0026#34;https://medium.com/\u0026#34; summary: \u0026#34;I wrote a post on Medium.\u0026#34; showReadingTime: false _build: render: \u0026#34;false\u0026#34; list: \u0026#34;local\u0026#34; --- Along with the normal front matter parameters like title and summary, the externalUrl parameter is used to tell Congo that this is not an ordinary article. The URL provided here will be where visitors are directed when they select this article.\nAdditionally, we use a special Hugo front matter parameter _build to prevent a normal page for this content being generated - there\u0026rsquo;s no point generating a page since we\u0026rsquo;re linking to an external URL!\nThe theme includes an archetype to make generating these external link articles simple. Just specify -k external when making new content.\nhugo new -k external posts/my-post.md Simple pages # Layout: layouts/_default/simple.html Front Matter: layout: \u0026quot;simple\u0026quot; Congo also includes a special layout for simple pages. The simple layout is a full-width template that just places Markdown content into the page without any special theme features.\nThe only features available in the simple layout are breadcrumbs and sharing links. However, the behaviour of these can still be controlled using the normal page front matter variables.\nTo enable the simple layout on a particular page, add the layout front matter variable with a value of \u0026quot;simple\u0026quot;:\n--- title: \u0026#34;My landing page\u0026#34; date: 2022-03-08 layout: \u0026#34;simple\u0026#34; --- This page content is now full-width. Custom layouts # One of the benefits of Hugo is that it makes it easy to create custom layouts for the whole site, individual sections or pages.\nLayouts follow all the normal Hugo templating rules and more information is available in the official Hugo docs.\nOverriding default layouts # Each of the content types discussed above lists the layout file that is used to generate each type of page. If this file is created in your local project it will override the theme template and thus can be used to customise the default style of the website.\nFor example, creating a layouts/_default/single.html file will allow the layout of leaf pages to be completely customised.\nCustom section layouts # It is also simple to create custom layouts for individual content sections. This is useful when you want to make a section that lists a certain type of content using a particular style.\nLet\u0026rsquo;s step through an example that creates a custom \u0026ldquo;Projects\u0026rdquo; page that lists projects using a special layout.\nIn order to do this, structure your content using the normal Hugo content rules and create a section for your projects. Additionally, create a new layout for the projects section by using the same directory name as the content and adding a list.html file.\n. └── content │ └── projects │ ├── _index.md │ ├── first-project.md │ └── second-project.md └── layouts └── projects └── list.html This list.html file will now override the default list template, but only for the projects section. Before we look at this file, lets first look at the individual project files.\n--- title: \u0026#34;Congo\u0026#34; date: 2021-08-11 icon: \u0026#34;github\u0026#34; description: \u0026#34;A theme for Hugo built with Tailwind CSS.\u0026#34; topics: [\u0026#34;Hugo\u0026#34;, \u0026#34;Web\u0026#34;, \u0026#34;Tailwind\u0026#34;] externalUrl: \u0026#34;https://github.com/jpanther/congo/\u0026#34; --- In this example we are assigning some metadata for each project that we can then use in our list template. There\u0026rsquo;s no page content, but there\u0026rsquo;s nothing stopping you from including it. It\u0026rsquo;s your own custom template after all!\nWith the projects defined, now we can create a list template that outputs the details of each project.\n{{ define \u0026#34;main\u0026#34; }} \u0026lt;section class=\u0026#34;mt-8\u0026#34;\u0026gt; {{ range .Pages }} \u0026lt;article class=\u0026#34;pb-6\u0026#34;\u0026gt; \u0026lt;a class=\u0026#34;flex\u0026#34; href=\u0026#34;{{ .Params.externalUrl }}\u0026#34;\u0026gt; \u0026lt;div class=\u0026#34;mr-3 text-3xl text-neutral-300\u0026#34;\u0026gt; \u0026lt;span class=\u0026#34;relative inline-block align-text-bottom\u0026#34;\u0026gt; {{ partial \u0026#34;icon.html\u0026#34; .Params.icon }} \u0026lt;/span\u0026gt; \u0026lt;/div\u0026gt; \u0026lt;div\u0026gt; \u0026lt;h3 class=\u0026#34;flex text-xl font-semibold\u0026#34;\u0026gt; {{ .Title }} \u0026lt;/h3\u0026gt; \u0026lt;p class=\u0026#34;text-sm text-neutral-400\u0026#34;\u0026gt; {{ .Description }} \u0026lt;/p\u0026gt; \u0026lt;/div\u0026gt; \u0026lt;/a\u0026gt; \u0026lt;/article\u0026gt; {{ end }} \u0026lt;/section\u0026gt; {{ end }} Although this is quite a straightforward example, you can see that it steps through each of the pages in this section (ie. each project), and then outputs HTML links to each project alongside an icon. The metadata in the front matter for each project is used to determine which information is displayed.\nKeep in mind that you\u0026rsquo;ll need to ensure the relevant styles and classes are available, which may require the Tailwind CSS to be recompiled. This is discussed in more detail in the Advanced Customisation section.\nWhen making custom templates like this one, it\u0026rsquo;s always easiest to take a look at how the default Congo template works and then use that as a guide. Remember, the Hugo docs are a great resource to learn more about creating templates too.\n","date":"9 August 2020","permalink":"/blowfish/docs/content-examples/","section":"Documentation","summary":"If you\u0026rsquo;ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.","title":"Content Examples"},{"content":"","date":"9 August 2020","permalink":"/blowfish/tags/example/","section":"Tags","summary":"","title":"example"},{"content":"This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing. 🚀\nYou can also use these content pages to define Hugo metadata like titles and descriptions that will be used for SEO and other purposes.\n","date":"8 August 2020","permalink":"/blowfish/tags/advanced/","section":"Tags","summary":"This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing.","title":"advanced"},{"content":"There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.\nIf you need further advice, post your questions on GitHub Discussions.\nHugo project structure # Before leaping into it, first a quick note about Hugo project structure and best practices for managing your content and theme customisations.\nIn summary: Never directly edit the theme files. Only make customisations in your Hugo project\u0026rsquo;s sub-directories, not in the themes directory itself. Congo is built to take advantage of all the standard Hugo practices. It is designed to allow all aspects of the theme to be customised and overriden without changing any of the core theme files. This allows for a seamless upgrade experience while giving you total control over the look and feel of your website.\nIn order to achieve this, you should never manually adjust any of the theme files directly. Whether you install using Hugo modules, as a git submodule or manually include the theme in your themes/ directory, you should always leave these files intact.\nThe correct way to adjust any theme behaviour is by overriding files using Hugo\u0026rsquo;s powerful file lookup order. In summary, the lookup order ensures any files you include in your project directory will automatically take precedence over any theme files.\nFor example, if you wanted to override the main article template in Congo, you can simply create your own layouts/_default/single.html file and place it in the root of your project. This file will then override the single.html from the theme without ever changing the theme itself. This works for any theme files - HTML templates, partials, shortcodes, config files, data, assets, etc.\nAs long as you follow this simple practice, you will always be able to update the theme (or test different theme versions) without worrying that you will lose any of your custom changes.\nColour schemes # Congo ships with a number of colour schemes out of the box. To change the basic colour scheme, you can set the colorScheme theme parameter. Refer to the Getting Started section to learn more about the built-in schemes.\nIn addition to the default schemes, you can also create your own and re-style the entire website to your liking. Schemes are created by by placing a \u0026lt;scheme-name\u0026gt;.css file in the assets/css/schemes/ folder. Once the file is created, simply refer to it by name in the theme configuration.\nCongo defines a three-colour palette that is used throughout the theme. The three colours are defined as neutral, primary and secondary variants, each containing ten shades of colour.\nDue to the way Tailwind CSS 3.0 calculates colour values with opacity, the colours specified in the scheme need to conform to a particular format by providing the red, green and blue colour values.\n:root { --color-primary-500: 139, 92, 246; } This example defines a CSS variable for the primary-500 colour with a red value of 139, green value of 92 and blue value of 246.\nUse one of the existing theme stylesheets as a template. You are free to define your own colours, but for some inspiration, check out the official Tailwind colour palette reference.\nOverriding the stylesheet # Sometimes you need to add a custom style to style your own HTML elements. Congo provides for this scenario by allowing you to override the default styles in your own CSS stylesheet. Simply create a custom.css file in your project\u0026rsquo;s assets/css/ folder.\nThe custom.css file will be minified by Hugo and loaded automatically after all the other theme styles which means anything in your custom file will take precedence over the defaults.\nAdjusting the font size # Changing the font size of your website is one example of overriding the default stylesheet. Congo makes this simple as it uses scaled font sizes throughout the theme which are derived from the base HTML font size. By default, Tailwind sets the default size to 12pt, but it can be changed to whatever value you prefer.\nCreate a custom.css file using the instructions above and add the following CSS declaration:\n/* Increase the default font size */ html { font-size: 13pt; } Simply by changing this one value, all the font sizes on your website will be adjusted to match this new size. Therefore, to increase the overall font sizes used, make the value greater than 12pt. Similarly, to decrease the font sizes, make the value less than 12pt.\nBuilding the theme CSS from source # If you\u0026rsquo;d like to make a major change, you can take advantage of Tailwind CSS\u0026rsquo;s JIT compiler and rebuild the entire theme CSS from scratch. This is useful if you want to adjust the Tailwind configuration or add extra Tailwind classes to the main stylesheet.\nNote: Building the theme manually is intended for advanced users. Let\u0026rsquo;s step through how building the Tailwind CSS works.\nTailwind configuration # In order to generate a CSS file that only contains the Tailwind classes that are actually being used the JIT compiler needs to scan through all the HTML templates and Markdown content files to check which styles are present in the markup. The compiler does this by looking at the tailwind.config.js file which is included in the root of the theme directory:\n// themes/congo/tailwind.config.js module.exports = { content: [ \u0026#34;./layouts/**/*.html\u0026#34;, \u0026#34;./content/**/*.{html,md}\u0026#34;, \u0026#34;./themes/congo/layouts/**/*.html\u0026#34;, \u0026#34;./themes/congo/content/**/*.{html,md}\u0026#34;, ], // and more... }; This default configuration has been included with these content paths so that you can easily generate your own CSS file without needing to modify it, provided you follow a particular project structure. Namely, you have to include Congo in your project as a subdirectory at themes/congo/. This means you cannot easily use Hugo Modules to install the theme and you must go down either the git submodule (recommended) or manual install routes. The Installation docs explain how to install the theme using either of these methods.\nProject structure # In order to take advantage of the default configuration, your project should look something like this\u0026hellip;\n. ├── assets │ └── css │ └── compiled │ └── main.css # this is the file we will generate ├── config # site config │ └── _default ├── content # site content │ ├── _index.md │ ├── projects │ │ └── _index.md │ └── blog │ └── _index.md ├── layouts # custom layouts for your site │ ├── partials │ │ └── extend-article-link.html │ ├── projects │ │ └── list.html │ └── shortcodes │ └── disclaimer.html └── themes └── congo # git submodule or manual theme install This example structure adds a new projects content type with its own custom layout along with a custom shortcode and extended partial. Provided the project follows this structure, all that\u0026rsquo;s required is to recompile the main.css file.\nInstall dependencies # In order for this to work you\u0026rsquo;ll need to change into the themes/congo/ directory and install the project dependencies. You\u0026rsquo;ll need npm on your local machine for this step.\ncd themes/congo npm install Run the Tailwind compiler # With the dependencies installed all that\u0026rsquo;s left is to use Tailwind CLI to invoke the JIT compiler. Navigate back to the root of your Hugo project and issue the following command:\ncd ../.. ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit It\u0026rsquo;s a bit of an ugly command due to the paths involved but essentially you\u0026rsquo;re calling Tailwind CLI and passing it the location of the Tailwind config file (the one we looked at above), where to find the theme\u0026rsquo;s main.css file and then where you want the compiled CSS file to be placed (it\u0026rsquo;s going into the assets/css/compiled/ folder of your Hugo project).\nThe config file will automatically inspect all the content and layouts in your project as well as all those in the theme and build a new CSS file that contains all the CSS required for your website. Due to the way Hugo handles file hierarchy, this file in your project will now automatically override the one that comes with the theme.\nEach time you make a change to your layouts and need new Tailwind CSS styles, you can simply re-run the command and generate the new CSS file. You can also add -w to the end of the command to run the JIT compiler in watch mode.\nMake a build script # To fully complete this solution, you can simplify this whole process by adding aliases for these commands, or do what I do and add a package.json to the root of your project which contains the necessary scripts\u0026hellip;\n// package.json { \u0026#34;name\u0026#34;: \u0026#34;my-website\u0026#34;, \u0026#34;version\u0026#34;: \u0026#34;1.0.0\u0026#34;, \u0026#34;description\u0026#34;: \u0026#34;\u0026#34;, \u0026#34;scripts\u0026#34;: { \u0026#34;server\u0026#34;: \u0026#34;hugo server -b http://localhost -p 8000\u0026#34;, \u0026#34;dev\u0026#34;: \u0026#34;NODE_ENV=development ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit -w\u0026#34;, \u0026#34;build\u0026#34;: \u0026#34;NODE_ENV=production ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit\u0026#34; }, // and more... } Now when you want to work on designing your site, you can invoke npm run dev and the compiler will run in watch mode. When you\u0026rsquo;re ready to deploy, run npm run build and you\u0026rsquo;ll get a clean Tailwind CSS build.\n🙋‍♀️ If you need help, feel free to ask a question on GitHub Discussions.\n","date":"8 August 2020","permalink":"/blowfish/docs/advanced-customisation/","section":"Documentation","summary":"There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.","title":"Advanced Customisation"},{"content":"","date":"8 August 2020","permalink":"/blowfish/tags/css/","section":"Tags","summary":"","title":"css"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/deployment/","section":"Tags","summary":"","title":"deployment"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/github/","section":"Tags","summary":"","title":"github"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/hosting/","section":"Tags","summary":"","title":"hosting"},{"content":"There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.\nCongo is built using relative URLs throughout the theme. This enables sites to easily be deployed to sub-folders and hosts like GitHub Pages. There\u0026rsquo;s usually no special configuration required for this to work as long as the baseURL parameter has been configured in the config.toml file.\nThe official Hugo Hosting and Deployment docs are the best place to learn how to deploy your site. The sections below contain some specific theme configuration details that can help you deploy smoothly with certain providers.\nChoose your provider:\nGitHub Pages Netlify Render Cloudflare Pages Shared hosting, VPS or private web server GitHub Pages # GitHub allows hosting on GitHub Pages using Actions. To enable this functionality, enable Pages on your repo and create a new Actions workflow to build and deploy your site.\nThe file needs to be in YAML format, placed within the .github/workflows/ directory of your GitHub repository and named with a .yml extension.\nImportant: Ensure you set the correct branch name under branches and in the deploy step if parameter to the source branch used in your project. # .github/workflows/gh-pages.yml name: GitHub Pages on: push: branches: - main jobs: build-deploy: runs-on: ubuntu-20.04 concurrency: group: ${{ github.workflow }}-${{ github.ref }} steps: - name: Checkout uses: actions/checkout@v3 with: submodules: true fetch-depth: 0 - name: Setup Hugo uses: peaceiris/actions-hugo@v2 with: hugo-version: \u0026#34;latest\u0026#34; - name: Build run: hugo --minify - name: Deploy uses: peaceiris/actions-gh-pages@v3 if: ${{ github.ref == \u0026#39;refs/heads/main\u0026#39; }} with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_branch: gh-pages publish_dir: ./public Push the config file to GitHub and the action should automatically run. It may fail the first time and you\u0026rsquo;ll need to visit the Settings \u0026gt; Pages section of your GitHub repo to check the source is correct. It should be set to use the gh-pages branch.\nOnce the settings are configured, re-run the action and the site should build and deploy correctly. You can consult the actions log to check everything deployed successfully.\nNetlify # To deploy to Netlify, create a new continuous deployment site and link it to your source code. The build settings can be left blank in the Netlify UI. You will only need to configure the domain you\u0026rsquo;ll be using.\nThen in the root of your site repository, create a netlify.toml file:\n# netlify.toml [build] command = \u0026#34;hugo mod get -u \u0026amp;\u0026amp; hugo --gc --minify -b $URL\u0026#34; publish = \u0026#34;public\u0026#34; [build.environment] NODE_ENV = \u0026#34;production\u0026#34; GO_VERSION = \u0026#34;1.16\u0026#34; TZ = \u0026#34;UTC\u0026#34; # Set to preferred timezone [context.production.environment] HUGO_VERSION = \u0026#34;0.100.2\u0026#34; HUGO_ENV = \u0026#34;production\u0026#34; [context.deploy-preview.environment] HUGO_VERSION = \u0026#34;0.100.2\u0026#34; This configuration assumes you are deploying Congo as a Hugo module. If you have installed the theme using another method, change the build command to simply hugo --gc --minify -b $URL.\nWhen you push the config file to your repo, Netlify should automatically deploy your site. You can check the deploy logs in the Netlify UI to check for any errors.\nRender # Deploying to Render is very straightforward and all configuration is via the Render UI.\nCreate a new Static Site and link it to your project\u0026rsquo;s code repository. Then simply configure the build command to be hugo --gc --minify and publish directory to be public.\nThe site will automatically build and deploy whenever you push a change to your repo.\nCloudflare Pages # Cloudflare offers the Pages service that can host Hugo blogs. It builds the site from a git repository and then hosts it on Cloudflare\u0026rsquo;s CDN. Follow their Hugo deployment guide to get started.\nThe Rocket Loader™ feature offered by Cloudflare tries to speed up rendering of web pages with JavaScript, but it breaks the appearance switcher in the theme. It can also cause an annoying light/dark screen flash when browsing your site due to scripts loading in the wrong order.\nThis problem can be fixed by disabling it:\nGo to the Cloudflare dashboard Click on your domain name in the list Click Optimization in the Speed section Scroll down to Rocket Loader™ and disable it Hugo sites built with Congo still load very quickly, even with this feature disabled.\nShared hosting, VPS or private web server # Using traditional web hosting, or deploying to your own web server, is as simple as building your Hugo site and transferring the files to your host.\nMake sure that the baseURL parameter in config.toml is set to the full URL to the root of your website (including any sub domains or sub-folders).\nThen build your site using hugo and copy the contents of the output directory to the root of your web server and you will be ready to go. By default, the output directory is named public.\nIf you need a hosting provider, check out Vultr or DigitalOcean. Signing up using these affiliate links will give you up to $100 in free credit so you can try the service.\n","date":"7 August 2020","permalink":"/blowfish/docs/hosting-deployment/","section":"Documentation","summary":"There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.\nCongo is built using relative URLs throughout the theme.","title":"Hosting \u0026 Deployment"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/netlify/","section":"Tags","summary":"","title":"netlify"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/render/","section":"Tags","summary":"","title":"render"},{"content":"","date":"11 March 2019","permalink":"/blowfish/tags/html/","section":"Tags","summary":"","title":"html"},{"content":"","date":"11 March 2019","permalink":"/blowfish/tags/markdown/","section":"Tags","summary":"","title":"markdown"},{"content":"This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.\nHeadings # The following HTML \u0026lt;h1\u0026gt;—\u0026lt;h6\u0026gt; elements represent six levels of section headings. \u0026lt;h1\u0026gt; is the highest section level while \u0026lt;h6\u0026gt; is the lowest.\nH1 # H2 # H3 # H4 # H5 # H6 # Paragraph # Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.\nItatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.\nBlockquotes # The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a footer or cite element, and optionally with in-line changes such as annotations and abbreviations.\nBlockquote without attribution # Tiam, ad mint andaepu dandae nostion secatur sequo quae. Note that you can use Markdown syntax within a blockquote.\nBlockquote with attribution # Don\u0026rsquo;t communicate by sharing memory, share memory by communicating.\n— Rob Pike1\nTables # Tables aren\u0026rsquo;t part of the core Markdown spec, but Hugo supports supports them out-of-the-box.\nName Age Bob 27 Alice 23 Inline Markdown within tables # Italics Bold Code italics bold code Code Blocks # Code block with backticks # \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026#34;en\u0026#34;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026#34;utf-8\u0026#34; /\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; Code block indented with four spaces # \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026quot;en\u0026quot;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026quot;utf-8\u0026quot;\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; Code block with Hugo\u0026rsquo;s internal highlight shortcode # 1 2 3 4 5 6 7 8 9 10 \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026#34;en\u0026#34;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026#34;utf-8\u0026#34;\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; List Types # Ordered List # First item Second item Third item Unordered List # List item Another item And another item Nested list # Fruit Apple Orange Banana Dairy Milk Cheese Other Elements — abbr, sub, sup, kbd, mark # GIF is a bitmap image format.\nH2O\nXn + Yn = Zn\nPress CTRL+ALT+Delete to end the session.\nMost salamanders are nocturnal, and hunt for insects, worms, and other small creatures.\nThe above quote is excerpted from Rob Pike\u0026rsquo;s talk about nothing during Gopherfest, November 18, 2015.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\n","date":"11 March 2019","permalink":"/blowfish/samples/markdown/","section":"Content Samples","summary":"\u003cp\u003eThis article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.\u003c/p\u003e","title":"Markdown"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/gist/","section":"Tags","summary":"","title":"gist"},{"content":"Hugo ships with several built-in shortcodes for rich content, along with a privacy config and a set of simple shortcodes that enable static and no-JS versions of various social media embeds.\nYouTube # Below is an example using the built-in youtube shortcode.\nTwitter # This example uses the twitter_simple shortcode to output a Tweet. It requires two named parameters user and id.\n“In addition to being more logical, asymmetry has the advantage that its complete appearance is far more optically effective than symmetry.”\n— Jan Tschichold pic.twitter.com/gcv7SrhvJb\n\u0026mdash; Graphic Design History (@DesignReviewed) January 17, 2019 Alternatively, the tweet shortcode can be used to embed a fully marked up Twitter card.\nGist # The gist shortcode can be used to embed a GitHub Gist. It requires two unnamed parameters: the username and ID of the Gist.\nVimeo # The vimeo_simple shortcode will embed a Vimeo video.\n","date":"10 March 2019","permalink":"/blowfish/samples/rich-content/","section":"Content Samples","summary":"This is an \u003cem\u003eexample\u003c/em\u003e of a \u003cstrong\u003erich\u003c/strong\u003e content summary.","title":"Rich Content"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/twitter/","section":"Tags","summary":"","title":"twitter"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/vimeo/","section":"Tags","summary":"","title":"vimeo"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/youtube/","section":"Tags","summary":"","title":"youtube"},{"content":"","date":"8 March 2019","permalink":"/blowfish/tags/katex/","section":"Tags","summary":"","title":"katex"},{"content":"KaTeX can be used to render mathematical notation within articles.\nCongo will only bundle the KaTeX assets into your project if you make use of mathematical notation. In order for this to work, simply include the katex shortcode within the article. Any KaTeX syntax on that page will then be automatically rendered.\nUse the online reference of supported TeX functions for the available syntax.\nInline notation # Inline notation can be generated by wrapping the expression in \\\\( and \\\\) delimiters.\nExample:\n% KaTeX inline notation Inline notation: \\\\(\\varphi = \\dfrac{1+\\sqrt5}{2}= 1.6180339887…\\\\) Inline notation: \\(\\varphi = \\dfrac{1+\\sqrt5}{2}= 1.6180339887…\\)\nBlock notation # Alternatively, block notation can be generated using $$ delimiters. This will output the expression in its own HTML block.\nExample:\n% KaTeX block notation $$ \\varphi = 1+\\frac{1} {1+\\frac{1} {1+\\frac{1} {1+\\cdots} } } $$ $$ \\varphi = 1+\\frac{1} {1+\\frac{1} {1+\\frac{1} {1+\\cdots} } } $$\n","date":"8 March 2019","permalink":"/blowfish/samples/mathematical-notation/","section":"Content Samples","summary":"\u003cp\u003eKaTeX can be used to render mathematical notation within articles.\u003c/p\u003e","title":"Mathematical notation"},{"content":"","date":"8 March 2019","permalink":"/blowfish/tags/maths/","section":"Tags","summary":"","title":"maths"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/chart/","section":"Tags","summary":"","title":"chart"},{"content":"Congo includes support for Chart.js using the chart shortcode. Simply wrap the chart markup within the shortcode. Congo automatically themes charts to match the configured colorScheme parameter, however the colours can be customised using normal Chart.js syntax.\nRefer to the chart shortcode docs for more details.\nThe examples below are a small selection taken from the official Chart.js docs. You can also view the page source on GitHub to see the markup.\nBar chart # Line chart # Doughnut chart # ","date":"6 March 2019","permalink":"/blowfish/samples/charts/","section":"Content Samples","summary":"Congo includes Chart.js for powerful charts and data visualisations.","title":"Charts"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/diagram/","section":"Tags","summary":"","title":"diagram"},{"content":"Mermaid diagrams are supported in Congo using the mermaid shortcode. Simply wrap the diagram markup within the shortcode. Congo automatically themes Mermaid diagrams to match the configured colorScheme parameter.\nRefer to the mermaid shortcode docs for more details.\nThe examples below are a small selection taken from the official Mermaid docs. You can also view the page source on GitHub to see the markup.\nFlowchart # graph TD A[Christmas] --\u003e|Get money| B(Go shopping) B --\u003e C{Let me think} B --\u003e G[/Another/] C ==\u003e|One| D[Laptop] C --\u003e|Two| E[iPhone] C --\u003e|Three| F[Car] subgraph Section C D E F G end Sequence diagram # sequenceDiagram autonumber par Action 1 Alice-\u003e\u003eJohn: Hello John, how are you? and Action 2 Alice-\u003e\u003eBob: Hello Bob, how are you? end Alice-\u003e\u003e+John: Hello John, how are you? Alice-\u003e\u003e+John: John, can you hear me? John--\u003e\u003e-Alice: Hi Alice, I can hear you! Note right of John: John is perceptive John--\u003e\u003e-Alice: I feel great! loop Every minute John--\u003eAlice: Great! end Class diagram # classDiagram Animal \"1\" \u003c|-- Duck Animal \u003c|-- Fish Animal \u003c--o Zebra Animal : +int age Animal : +String gender Animal: +isMammal() Animal: +mate() class Duck{ +String beakColor +swim() +quack() } class Fish{ -int sizeInFeet -canEat() } class Zebra{ +bool is_wild +run() } Entity relationship diagram # erDiagram CUSTOMER }|..|{ DELIVERY-ADDRESS : has CUSTOMER ||--o{ ORDER : places CUSTOMER ||--o{ INVOICE : \"liable for\" DELIVERY-ADDRESS ||--o{ ORDER : receives INVOICE ||--|{ ORDER : covers ORDER ||--|{ ORDER-ITEM : includes PRODUCT-CATEGORY ||--|{ PRODUCT : contains PRODUCT ||--o{ ORDER-ITEM : \"ordered in\" ","date":"6 March 2019","permalink":"/blowfish/samples/diagrams-flowcharts/","section":"Content Samples","summary":"It\u0026rsquo;s easy to add diagrams and flowcharts to articles using Mermaid.","title":"Diagrams and Flowcharts"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/graph/","section":"Tags","summary":"","title":"graph"},{"content":"","date":"5 March 2019","permalink":"/blowfish/tags/emoji/","section":"Tags","summary":"","title":"emoji"},{"content":"Emoji is supported throughout Congo by default. Emoji can be used in titles, menu items and article content.\nNote: The rendering of these glyphs depends on the browser and the platform. To style the emoji you can either use a third party emoji font or a font stack. Emoji replacements are automatic throughout Congo, so you can use shorthand codes in your content and front matter and they will be converted to their corresponding symbols at build time.\nExample: see_no_evil 🙈, hear_no_evil 🙉, speak_no_evil 🙊.\nThe Emoji cheat sheet is a useful reference for emoji shorthand codes.\n","date":"5 March 2019","permalink":"/blowfish/samples/emoji/","section":"Content Samples","summary":"📖🏞️🧗🏽🐉🧙🏽‍♂️🧚🏽👸","title":"Emoji 🪂"},{"content":" A powerful, lightweight theme for Hugo built with Tailwind CSS. This is a demo site built entirely using Congo. It also contains a complete set of theme documentation. Congo is flexible and is great for both static page-based content (like this demo) or a traditional blog with a feed of recent posts.\nThis is a demo of the page layout. Switch layout \u0026orarr; Explore the sample pages to get a feel for what Congo can do. If you like what you see, check out the project on Github or read the Installation guide to get started.\nPhoto by Jippe Joosten on Unsplash. ","date":"1 January 0001","permalink":"/blowfish/s_index/","section":"Blowfish","summary":"A powerful, lightweight theme for Hugo built with Tailwind CSS. This is a demo site built entirely using Congo. It also contains a complete set of theme documentation. Congo is flexible and is great for both static page-based content (like this demo) or a traditional blog with a feed of recent posts.","title":"Welcome to Congo! 🎉"}] \ No newline at end of file +[{"content":"I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.\nI’ve worked for several years in big companies and recently decided to trade that for the opportunity of working in smaller teams. Definitely prefer the latter where one can succeed/fail faster, learn faster, and overall have a way bigger impact.\nCurrently, I am focused on improving the lives of developers worldwide. I’m trying to write more about my previous experiences / random thoughts and would love to gather your feedback on it. I also love to dedicate my time to helping and mentoring other PMs or people that want to get into product.\nRecently I’ve also joined AWS Loft to help Startups and their founders with their product strategy.\nFeel free to reach out.\n","date":"13 June 2022","permalink":"/blowfish/about/","section":"Blowfish","summary":"I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.","title":"About"},{"content":"","date":"13 June 2022","permalink":"/blowfish/","section":"Blowfish","summary":"","title":"Blowfish"},{"content":"","date":"13 June 2022","permalink":"/blowfish/posts/","section":"Posts","summary":"","title":"Posts"},{"content":"","date":"20 January 2022","permalink":"/blowfish/tags/docs/","section":"Tags","summary":"","title":"docs"},{"content":" Simple, yet powerful. Learn how to use Congo and its features. This section contains everything you need to know about Congo. If you\u0026rsquo;re new, check out the Installation guide to begin or visit the Samples section to see what Congo can do.\n","date":"20 January 2022","permalink":"/blowfish/docs/","section":"Documentation","summary":"Simple, yet powerful. Learn how to use Congo and its features. This section contains everything you need to know about Congo. If you\u0026rsquo;re new, check out the Installation guide to begin or visit the Samples section to see what Congo can do.","title":"Documentation"},{"content":"","date":"20 January 2022","permalink":"/blowfish/tags/new/","section":"Tags","summary":"","title":"new"},{"content":"Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.\nThis area could be used to add some extra decriptive text to each taxonomy. Check out the advanced tag below to see how to take this concept even further.\n","date":"20 January 2022","permalink":"/blowfish/tags/","section":"Tags","summary":"Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.","title":"Tags"},{"content":"Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.\nThat said, there are some changes that require adjustments to existing sites that are built with Congo version 1.x. This guide will step you through the process and highlight things you need to consider.\nStep 1: Upgrade Hugo # Congo 2.0 requires a minimum of Hugo v0.87.0 or later Congo is built to take advantage of some of the latest Hugo features. You should regularly keep your Hugo installation up to date to avoid any issues.\nYou can check your current version using the command hugo version. Visit the Hugo docs for information on obtaining a newer release for your platform.\nStep 2: Upgrade Congo # The process for upgrading Congo will depend on how you include the theme in your project. Instructions for each method can be found below.\nUpgrade using Hugo Upgrade using git Upgrade manually Upgrade using Hugo # To upgrade a go module to a new major release, the modules.toml and go.mod files need to be updated. In each file, update the path to the theme from github.com/jpanther/congo to github.com/jpanther/congo/v2.\nThen change into your project directory and execute the following command:\nhugo mod get -u Note that in some circumstances there may be issues with this step due to the way that Hugo locally caches modules. If the command above doesn\u0026rsquo;t work, try using hugo mod clean to clear out the local cache and re-download any modules.\nOnce the theme has been upgraded, continue to the next section.\nUpgrade using git # Git submodules can be upgraded using the git command. Simply execute the following command and the latest version of the theme will be downloaded into your local repository:\ngit submodule update --remote --merge Once the submodule has been upgraded, continue to the next section.\nUpgrade manually # Updating Congo manually requires you to download the latest copy of the theme and replace the old version in your project.\nNote that any local customisations you have made to the theme files will be lost during this process. Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder. You will need to overwrite the existing directory to replace all the theme files.\nContinue to the next section.\nStep 3: Theme configuration # Congo 2.0 introduces a number of new theme configuration parameters. Although the theme will adapt to existing version 1 configurations, in order to take advantage of some of the newer theme features, you will need to adjust your existing configuration.\nThe simplest way to do this is to take a copy of the theme\u0026rsquo;s default configuration and compare it to your existing files. The process is outlined in greater detail below.\nLanguages.toml # In order to provide multilingual support, language-specific theme parameters have been moved to a new config file languages.[lang-code].toml. The theme comes with a template languages.en.toml file which can be used as a guide.\nThis step is optional if you do not need multilingual support, although completing it now will make future theme upgrades easier. The languages config file follows this structure:\n# config/_default/languagues.en.toml languageCode = \u0026#34;en\u0026#34; languageName = \u0026#34;English\u0026#34; displayName = \u0026#34;EN\u0026#34; htmlCode = \u0026#34;en\u0026#34; weight = 1 rtl = false # Language-specific parameters go here Using your preferred language, simply create this new file in config/_default/ and then move the language-specific parameters from any existing config files over to this new file. The table below outlines the parameters that need to be moved.\nParameter Old location title config.toml description params.toml copyright config.toml dateFormat params.toml [author] config.toml Once the values have been moved to the new location, these parameters should be deleted from their original locations.\nMenus.toml # As the theme is now aware of languages, the menus.toml file should also be renamed to include a language code. Rename the existing menus.toml to menus.[lang-code].toml, where the language code matches the code used in the languages.toml file in the previous section.\nConfig.toml # The config.toml file now only contains base Hugo configuration values. Other than removing the language-specific strings above, there are only two changes to consider.\nIf you\u0026rsquo;re using a language other than English, provide a defaultContentLanguage value that matches the language code in the config file you created for your language. Secondly, to take advange of the new site search in Congo 2.0, an [outputs] block needs to be provided.\n# config/_default/config.toml defaultContentLanguage = \u0026#34;en\u0026#34; enableRobotsTXT = true paginate = 10 summaryLength = 0 [outputs] home = [\u0026#34;HTML\u0026#34;, \u0026#34;RSS\u0026#34;, \u0026#34;JSON\u0026#34;] Markup.toml # Congo 2.0 adds support for tables of contents on article pages. Although Hugo ships with default settings for generating contents listings, you can adjust this behaviour by adding a new [tableOfContents] block to your markup.toml file.\nThe recommended settings are as follows, which includes any headings in the Markdown content at levels 2, 3 and 4:\n# config/_default/markup.toml [tableOfContents] startLevel = 2 endLevel = 4 Params.toml # A number of new theme parameters have been introduced in Congo 2.0. Some minor changes are requried to existing configurations. Remember, the theme will always revert to a sensible default if a parameter is not provided.\nThe way that dark mode works in Congo has been changed to allow greater flexibility around configuration. The old darkMode and darkToggle parameters have been removed and replaced by three new parameters. These new options operate independently of each other, making it possible to force the appearance while still allowing the user to override.\nNew parameter Type Default Description defaultAppearance String \u0026quot;light\u0026quot; Default theme appearance; either light or dark.\n⚠️ Setting this to light replicates the old darkMode = false setting, while dark replicates darkMode = true. autoSwitchAppearance Boolean true Whether the theme appearance automatically switches based upon the operating system preference. Set to false to force the site to always use the defaultAppearance. ⚠️ Setting this to true replicates the old darkMode = \u0026quot;auto\u0026quot; setting. showAppearanceSwitcher Boolean false Whether the theme appearance switcher is dispalyed in the site footer. ⚠️ This parameter replaces darkToggle. The following table outlines some other key new parameters that control new features in version 2:\nNew parameter Type Default enableSearch Boolean false showScrollToTop Boolean true article.showTaxonomies Boolean false article.showTableOfContents Boolean false list.showTableOfContents Boolean false For the full list of supported parameters, refer to the Configuration docs.\nStep 4: Move assets # All site assets, with the exception of favicons, now use Hugo Pipes to build an optimised version of your project. In order for the theme to locate your files, any previously static theme assets need to be moved to the Hugo assets folder. Primarily this is the author image and site logo:\nstatic/me.jpg → assets/me.jpg\nstatic/logo.jpg → assets/logo.jpg\nIf you have provided an author image or site logo, simply move these assets from static/ to assets/. If you use the same directory structure the theme will know where to find these files automatically. If you would like to provide a new path, update the logo and author.image config values accordingly.\nNote that this step does not apply to any assets in your project that are actually static. For example, a PDF file that you link directly to from within an article is a static asset. These files should remain in the static/ directory to ensure they are copied to the output folder when Hugo builds the site.\nStep 5: Check content # The behavior of the figure shortcode is different in version 2. If you are using figure in your content and have advanced use cases, you may need to adjust the parameters you are providing.\nConsult the shortcode docs to learn more about supported parameters.\nStep 6: Rebuild # Now that all the configuration changes are complete, it\u0026rsquo;s time to rebuild the site. Run hugo, or your build command, and check that everything works as expected.\nIf you come across any errors, check the configuration is correct and refer to the full documentation for further guidance. Remember, the example config files bundled with the theme contain all the default parameters and are a great starting point.\n🙋‍♀️ If you still need help, feel free to ask your question on GitHub Discussions.\n","date":"20 January 2022","permalink":"/blowfish/docs/version-2/upgrade/","section":"Documentation","summary":"Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release.\nThat said, there are some changes that require adjustments to existing sites that are built with Congo version 1.","title":"Upgrading from Congo 1.x"},{"content":" Congo 2.0 is packed with tons of new features and optimisations. The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.\nContinue reading below to discover what\u0026rsquo;s new. When you\u0026rsquo;re ready to upgrade, check out the guide to upgrading.\nTailwind CSS 3.0 # Tailwind CSS is at the heart of Congo and this new release contains the very latest Tailwind CSS version 3. It brings with it performance optimisations and support for some great new CSS features.\nImplementing this new version has also removed some Tailwind plugin dependencies from the theme, allowing the overall footprint to remain lightweight.\nMultilingual support # A highly requested feature, Congo is now multilingual! If you publish your content in multiple languages, the site will be built with all the translations available.\n🇬🇧 🇩🇪 🇫🇷 🇪🇸 🇨🇳 🇧🇷 🇹🇷 🇧🇩 Thanks to submissions from the community, Congo has already been translated into eight languages with more to be added over time. By the way, pull requests for new languages are always welcome!\nRTL language support # One of the benefits of the new Tailwind and Multilingual features is the ability to add RTL language support. When enabled, the entire site will reflow content from right-to-left. Every element in the theme has been restyled to ensure it looks great in this mode which aids authors who wish to generate content in RTL languages.\nRTL is controlled on a per-language basis so you can mix and match both RTL and LTR content in your projects and the theme will respond accordingly.\nAutomatic image resizing # A big change in Congo 2.0 is the addition of automatic image resizing. Using the power of Hugo Pipes, images in Markdown content are now automatically scaled to different output sizes. These are then presented using HTML srcset attributes enabling optimised file sizes to be served to your site visitors.\n\u0026lt;!-- Markdown: ![My image](image.jpg) --\u0026gt; \u0026lt;img srcset=\u0026#34; /image_320x0_resize_q75_box.jpg 320w, /image_635x0_resize_q75_box.jpg 635w, /image_1024x0_resize_q75_box.jpg 1024w, /image_1270x0_resize_q75_box.jpg 2x\u0026#34; src=\u0026#34;/image_635x0_resize_q75_box.jpg\u0026#34; alt=\u0026#34;My image\u0026#34; /\u0026gt; Best of all there\u0026rsquo;s nothing you need to change! Simply insert standard Markdown image syntax and let the theme do the rest. If you want a little more control, the figure shortcode has been completely rewritten to provide the same resizing benefits.\nPerformance improvements # This update packs performance improvements throughout. A key objective for this release was to improve Lighthouse scores and Congo now scores a perfect 100 on all four metrics.\nThere\u0026rsquo;s too many individual changes to highlight them here but the results speak for themselves. If you want to dig deeper, you can view the Lighthouse report. Real world performance will vary based upon server configuration.\nSite search # Powered by Fuse.js, site search allows visitors to quickly and easily find your content. All searches are performed client-side meaning there\u0026rsquo;s nothing to configure on the server and queries are performed super fast. Simply enable the feature in your site configuration and you\u0026rsquo;re all set. Oh, and it also supports full keyboard navigation!\nTables of contents # A highly requested feature, Congo now supports tables of contents on article pages. You can see it in action on this page. The contents are fully responsive and will adjust to take advantage of the space available at different screen resolutions.\nAvailable on a global or per article basis, the table of contents can be fully customised using standard Hugo configuration values, allowing you to adjust the behaviour to suit your project.\nAccessibility improvements # From adding ARIA descriptions to more items or simply adjusting the contrast of certain text elements, this release is the most accessible yet.\nVersion 2 also introduces \u0026ldquo;skip to content\u0026rdquo; and \u0026ldquo;scroll to top\u0026rdquo; links that enable quick navigation. There\u0026rsquo;s also keyboard shortcuts for enabling items like search without reaching for the mouse.\nThe new image resizing features also provide full control over alt and title elements enabling an accessible experience for all visitors.\nA whole lot more # There\u0026rsquo;s countless other minor changes to explore. From being able to display taxonomies on articles and list pages, to using the new headline author parameter to customise your homepage. There\u0026rsquo;s also improved JSON-LD strucured data which further optimises SEO performance. Plus the entire theme has had extra polish to ensure a consistent design language.\n🚀 Check out the full changelog to learn more.\nNext steps # If you\u0026rsquo;re ready to upgrade, read the upgrading from version 1 guide to get started. If you\u0026rsquo;re new to Congo, check out the Installation guide to begin a new project.\n","date":"19 January 2022","permalink":"/blowfish/docs/version-2/","section":"Documentation","summary":"Congo 2.0 is packed with tons of new features and optimisations. The original aim of Congo was to develop a theme that was simple and lightweight. Version 2 takes this one step further and makes the theme even more powerful while still maintaining its lightweight footprint.","title":"What's New in 2.0 ✨"},{"content":"","date":"16 August 2020","permalink":"/blowfish/tags/installation/","section":"Tags","summary":"","title":"installation"},{"content":"Simply follow the standard Hugo Quick Start procedure to get up and running quickly.\nDetailed installation instructions can be found below. Instructions for updating the theme are also available.\nInstallation # These instructions will get you up and running using Hugo and Congo from a completely blank state. Most of the dependencies mentioned in this guide can be installed using the package manager of choice for your platform.\nInstall Hugo # If you haven\u0026rsquo;t used Hugo before, you will need to install it onto your local machine. You can check if it\u0026rsquo;s already installed by running the command hugo version.\nMake sure you are using Hugo version 0.87.0 or later as the theme takes advantage of some of the latest Hugo features. You can find detailed installation instructions for your platform in the Hugo docs.\nCreate a new site # Run the command hugo new site mywebsite to create a new Hugo site in a directory named mywebsite.\nNote that you can name the project directory whatever you choose, but the instructions below will assume it\u0026rsquo;s named mywebsite. If you use a different name, be sure to substitute it accordingly.\nDownload the Congo theme # There several different ways to install the Congo theme into your Hugo website. From easiest to most difficult to install and maintain, they are:\nHugo module (recommended) Git submodule Manual file copy If you\u0026rsquo;re unsure, choose the Hugo module method.\nInstall using Hugo # This method is the quickest and easiest for keeping the theme up-to-date. Hugo uses Go to initialise and manage modules so you need to ensure you have go installed before proceeding.\nDownload and install Go. You can check if it\u0026rsquo;s already installed by using the command go version.\nMake sure you are using Go version 1.12 or later as Hugo requires this for modules to work correctly. From your Hugo project directory (that you created above), initialise modules for your website:\n# If you\u0026#39;re managing your project on GitHub hugo mod init github.com/\u0026lt;username\u0026gt;/\u0026lt;repo-name\u0026gt; # If you\u0026#39;re managing your project locally hugo mod init my-project Add the theme to your configuration by creating a new file config/_default/module.toml and adding the following:\n[[imports]] path = \u0026#34;github.com/jpanther/congo/v2\u0026#34; Start your server using hugo server and the theme will be downloaded automatically.\nContinue to set up the theme configuration files.\nInstall using git # For this method you\u0026rsquo;ll need to ensure you have Git installed on your local machine.\nChange into the directory for your Hugo website (that you created above), initialise a new git repository and add Congo as a submodule.\ncd mywebsite git init git submodule add -b stable https://github.com/jpanther/congo.git themes/congo Then continue to set up the theme configuration files.\nInstall manually # Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder.\nContinue to set up the theme configuration files.\nSet up theme configuration files # In the root folder of your website, delete the config.toml file that was generated by Hugo. Copy the *.toml config files from the theme into your config/_default/ folder. This will ensure you have all the correct theme settings and will enable you to easily customise the theme to your needs.\nNote: You should not overwrite the module.toml file if one already exists in your project! Depending on how you installed the theme you will find the theme config files in different places:\nHugo Modules: In the Hugo cache directory, or download a copy from GitHub Git submodule or Manual install: themes/congo/config/_default Once you\u0026rsquo;ve copied the files, your config folder should look like this:\nconfig/_default/ ├─ config.toml ├─ markup.toml ├─ menus.toml ├─ module.toml # if you installed using Hugo Modules └─ params.toml Important: If you didn\u0026rsquo;t use Hugo Modules to install Congo, you must add the line theme = \u0026quot;congo\u0026quot; to the top of your config.toml file. Next steps # The basic Congo installation is now complete. Continue to the Getting Started section to learn more about configuring the theme.\nInstalling updates # From time to time there will be new releases posted that apply fixes and add new functionality to the theme. In order to take advantage of these changes, you will need to update the theme files on your website.\nHow you go about this will depend on the installation method you chose when the theme was originally installed. Instructions for each method can be found below.\nHugo module Git submodule Manual file copy Update using Hugo # Hugo makes updating modules super easy. Simply change into your project directory and execute the following command:\nhugo mod get -u Hugo will automatically update any modules that are required for your project. It does this by inspecting your module.toml and go.mod files. If you have any issues with the update, check to ensure these files are still configured correctly.\nThen simply rebuild your site and check everything works as expected.\nUpdate using git # Git submodules can be updated using the git command. Simply execute the following command and the latest version of the theme will be downloaded into your local repository:\ngit submodule update --remote --merge Once the submodule has been updated, rebuild your site and check everything works as expected.\nUpdate manually # Updating Congo manually requires you to download the latest copy of the theme and replace the old version in your project.\nNote that any local customisations you have made to the theme files will be lost during this process. Download the latest release of the theme source code.\nDownload from Github Extract the archive, rename the folder to congo and move it to the themes/ directory inside your Hugo project\u0026rsquo;s root folder. You will need to overwrite the existing directory to replace all the theme files.\nRebuild your site and check everything works as expected.\n","date":"16 August 2020","permalink":"/blowfish/docs/installation/","section":"Documentation","summary":"Simply follow the standard Hugo Quick Start procedure to get up and running quickly.\nDetailed installation instructions can be found below. Instructions for updating the theme are also available.\nInstallation # These instructions will get you up and running using Hugo and Congo from a completely blank state.","title":"Installation"},{"content":" This section assumes you have already installed the Congo theme. The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.\nBasic configuration # Before creating any content, there are a few things you should set for a new installation. Starting in the config.toml file, set the baseURL and languageCode parameters. The languageCode should be set to the main language that you will be using to author your content.\n# config/_default/config.toml baseURL = \u0026#34;https://your_domain.com/\u0026#34; languageCode = \u0026#34;en\u0026#34; The next step is to configure the language settings. Although Congo supports multilingual setups, for now, just configure the main language.\nLocate the languages.en.toml file in the config folder. If your main language is English you can use this file as is. Otherwise, rename it so that it includes the correct language code in the filename. For example, for French, rename the file to languages.fr.toml.\nNote that the language code in the language config filename should match the languageCode setting in config.toml. # config/_default/languages.en.toml title = \u0026#34;My awesome website\u0026#34; [author] name = \u0026#34;My name\u0026#34; image = \u0026#34;img/author.jpg\u0026#34; headline = \u0026#34;A generally awesome human\u0026#34; bio = \u0026#34;A little bit about me\u0026#34; links = [ { twitter = \u0026#34;https://twitter.com/username\u0026#34; } ] The [author] configuration determines how the author information is displayed on the website. The image should be placed in the site\u0026rsquo;s assets/ folder. Links will be displayed in the order they are listed.\nIf you need extra detail, further information about each of these configuration options, is covered in the Configuration section.\nColour schemes # Congo ships with a number of colour schemes out of the box. To change the scheme, simply set the colorScheme theme parameter. Valid options are congo (default), avocado, fire, ocean and slate.\n# config/_default/params.toml colorScheme = \u0026#34;congo\u0026#34; Congo defines a three-colour palette that is used throughout the theme. Each main colour contains ten shades which are based upon the colours that are included in Tailwind.\nCongo (default) # Avocado # Fire # Ocean # Slate # Although these are the default schemes, you can also create your own. Refer to the Advanced Customisation section for details.\nOrganising content # By default, Congo doesn\u0026rsquo;t force you to use a particular content type. In doing so you are free to define your content as you wish. You might prefer pages for a static site, posts for a blog, or projects for a portfolio.\nHere\u0026rsquo;s a quick overview of a basic Congo project. All content is placed within the content folder:\n. ├── assets │ └── img │ └── author.jpg ├── config │ └── _default ├── content │ ├── _index.md │ ├── about.md │ └── posts │ ├── _index.md │ ├── first-post.md │ └── another-post │ ├── aardvark.jpg │ └── index.md └── themes └── congo It\u0026rsquo;s important to have a firm grasp of how Hugo expects content to be organised as the theme is designed to take full advantage of Hugo page bundles. Be sure to read the official Hugo docs for more information.\nCongo is also flexible when it comes to taxonomies. Some people prefer to use tags and categories to group their content, others prefer to use topics.\nHugo defaults to using posts, tags and categories out of the box and this will work fine if that\u0026rsquo;s what you want. If you wish to customise this, however, you can do so by creating a taxonomies.toml configuration file:\n# config/_default/taxonomies.toml topic = \u0026#34;topics\u0026#34; This will replace the default tags and categories with topics. Refer to the Hugo Taxonomy docs for more information on naming taxonomies.\nWhen you create a new taxonomy, you will need to adjust the navigation links on the website to point to the correct sections, which is covered below.\nMenus # Congo has two menus that can be customised to suit the content and layout of your site. The main menu appears in the site header and the footer menu appears at the bottom of the page just above the copyright notice.\nBoth menus are configured in the menus.en.toml file. Similarly to the languages config file, if you wish to use another language, rename this file and replace en with the language code you wish to use.\n# config/_default/menus.toml [[main]] name = \u0026#34;Blog\u0026#34; pageRef = \u0026#34;posts\u0026#34; weight = 10 [[main]] name = \u0026#34;Topics\u0026#34; pageRef = \u0026#34;topics\u0026#34; weight = 20 [[footer]] name = \u0026#34;Privacy\u0026#34; url = \u0026#34;https://external-link\u0026#34; The name parameter specifies the text that is used in the menu link. You can also optionally provide a title which fills the HTML title attribute for the link.\nThe pageRef parameter allows you to easily reference Hugo content pages and taxonomies. It is the quickest way to configure the menu as you can simply refer to any Hugo content item and it will automatically build the correct link. To link to external URLs, the url parameter can be used.\nMenu links will be sorted from lowest to highest weight, and then alphabetically by name.\nBoth menus are completely optional and can be commented out if not required. Use the template provided in the file as a guide.\nDetailed configuration # The steps above are the bare minimum configuration. If you now run hugo server you will be presented with a blank Congo website. Detailed configuration is covered in the Configuration section.\n","date":"15 August 2020","permalink":"/blowfish/docs/getting-started/","section":"Documentation","summary":"This section assumes you have already installed the Congo theme. The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.","title":"Getting Started"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/config/","section":"Tags","summary":"","title":"config"},{"content":"Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.\nThe theme ships with a default configuration that gets you up and running with a basic blog or static website.\nConfiguration 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.\nThe default theme configuration is documented in each file so you can freely adjust the settings to meet your needs.\nAs outlined in the installation instructions, you should adjust your theme configuration by modifying the files in the config/_default/ folder of your Hugo project and delete the config.toml file in your project root. Site configuration # Standard Hugo configuration variables are respected throughout the theme, however there are some specific things that should be configured for the best experience.\nThe site configuration is managed through the config/_default/config.toml file. The table below outlines all the settings that the Congo takes advantage of.\nNote that the variable names provided in this table use dot notation to simplify the TOML data structure (ie. outputs.home refers to [outputs] home).\nName Default Description theme \u0026quot;congo\u0026quot; When using Hugo Modules this config value should be removed. For all other installation types, this must be set to congo for the theme to function. baseURL Not set The URL to the root of the website. defaultContentLanguage \u0026quot;en\u0026quot; This value determines the default language of theme components and content. Refer to the language and i18n section below for supported language codes. enableRobotsTXT true When enabled, a robots.txt file will be created in the site root that allows search engines to crawl the entire site. If you prefer to provide your own pre-made robots.txt, set to false and place your file in the static directory. For complete control, you may provide a custom layout to generate this file. paginate 10 The number of articles listed on each page of the article listing. summaryLength 0 The number of words that are used to generate the article summary when one is not provided in the front matter. A value of 0 will use the first sentence. This value has no effect when summaries are hidden. outputs.home [\u0026quot;HTML\u0026quot;, \u0026quot;RSS\u0026quot;, \u0026quot;JSON\u0026quot;] The output formats that are generated for the site. Congo requires HTML, RSS and JSON for all theme components to work correctly. permalinks Not set Refer to the Hugo docs for permalink configuration. taxonomies Not set Refer to the Organising content section for taxonomy configuration. Language and i18n # Congo is optimised for full multilingual websites and theme assets are translated into several languages out of the box. The language configuration allows you to generate multiple versions of your content to provide a customised experience to your visitors in their native language.\nThe theme currently supports the following languages by default:\nLanguage Code 🇬🇧 English en 🇧🇩 Bengali bn 🇨🇳 Simplified Chinese (China) zh-cn 🇹🇼 Traditional Chinese (Taiwan) zh-tw 🇫🇮 Finnish fi 🇫🇷 French fr 🇩🇪 German de 🇮🇱 Hebrew he 🇭🇺 Hungarian hu 🇮🇹 Italian it 🇯🇵 Japanese ja 🇧🇷 Portuguese (Brazil) pt-br 🇵🇹 Portuguese (Portugal) pt-pt 🇷🇴 Romanian ro 🇪🇸 Spanish (Spain) es 🇹🇷 Turkish tr The default translations can be overridden by creating a custom file in i18n/[code].yaml that contains the translation strings. You can also use this method to add new languages. If you\u0026rsquo;d like to share a new translation with the community, please open a pull request.\nConfiguration # In order to be as flexible as possible, a language configuration file needs to be created for each language on the website. By default Congo includes an English language configuration at config/_default/languages.en.toml.\nThe default file can be used as a template to create additional languages, or renamed if you wish to author your website in a language other than English. Simply name the file using the format languages.[language-code].toml.\nNote: Ensure the defaultContentLanguage parameter in the site configuration matches the language code in your language config filename. Name Default Description languageCode \u0026quot;en\u0026quot; The Hugo language code for this file. It can be a top-level language (ie. en) or a sub-variant (ie. en-au) and should match the language code in the filename. Hugo expects this value to always be in lowercase. For proper HTML compliance, set the isoCode parameter which is case-sensitive. languageName \u0026quot;English\u0026quot; The name of the language. displayName \u0026quot;EN\u0026quot; The name used when the language appears on the website. isoCode \u0026quot;en\u0026quot; The ISO language code for HTML metadata purposes. It can be a top-level language (ie. en) or a sub-variant (ie. en-AU). weight 1 The weight determines the order of languages when building multilingual sites. rtl false Whether or not this is a RTL language. Set to true to reflow content from right-to-left. Congo fully supports using RTL and LTR languages at the same time and will dynamically adjust to both. dateFormat \u0026quot;2 January 2006\u0026quot; How dates are formatted in this language. Refer to the Hugo docs for acceptable formats. title \u0026quot;Congo\u0026quot; The title of the website. This will be displayed in the site header and footer. description Not set The website description. This will be used in the site metadata. copyright Not set 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 title. author.name Not set The author\u0026rsquo;s name. This will be displayed in article footers, and on the homepage when the profile layout is used. author.image Not set Path to the image file of the author. The image should be a 1:1 aspect ratio and placed in the site\u0026rsquo;s assets/ folder. author.headline Not set A Markdown string containing the author\u0026rsquo;s headline. It will be displayed on the profile homepage under the author\u0026rsquo;s name. author.bio Not set A Markdown string containing the author\u0026rsquo;s bio. It will be displayed in article footers. author.links Not set The links to display alongside the author\u0026rsquo;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 assets/icons/. Menus # Congo also supports language-specific menu configurations. Menu config files follow the same naming format as the languages file. Simply provide the language code in the file name to tell Hugo which language the file relates to.\nMenu config files are named with the format menus.[language-code].toml. Always ensure that the language code used in the menus configuration matches the languages configuration.\nThe Getting Started section explains more about the structure of this file. You can also refer to the Hugo menu docs for more configuration examples.\nTheme parameters # Congo provides a large number of configuration parameters that control how the theme functions. The table below outlines every available parameter in the config/_default/params.toml file.\nMany of the article defaults here can be overridden on a per article basis by specifying it in the front matter. Refer to the Front Matter section for further details.\nName Default Description colorScheme \u0026quot;congo\u0026quot; The theme colour scheme to use. Valid values are congo (default), avocado, ocean, fire and slate. Refer to the Colour Schemes section for more details. defaultAppearance \u0026quot;light\u0026quot; The default theme appearance, either light or dark. autoSwitchAppearance true Whether the theme appearance automatically switches based upon the visitor\u0026rsquo;s operating system preference. Set to false to force the site to always use the defaultAppearance. enableSearch false Whether site search is enabled. Set to true to enable search functionality. Note that the search feature depends on the outputs.home setting in the site configuration being set correctly. enableCodeCopy false Whether copy-to-clipboard buttons are enabled for \u0026lt;code\u0026gt; blocks. The highlight.noClasses parameter must be set to false for code copy to function correctly. Read more about other configuration files below. logo Not set The relative path to the site logo file within the assets/ folder. The logo file should be provided at 2x resolution and supports any image dimensions. mainSections Not set The sections that should be displayed in the recent articles list. If not provided the section with the greatest number of articles is used. robots Not set String that indicates how robots should handle your site. If set, it will be output in the page head. Refer to Google\u0026rsquo;s docs for valid values. header.layout \u0026quot;basic\u0026quot; The layout of the page header and menu. Valid values are basic, hamburger or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/header/custom.html file. footer.showCopyright true Whether or not to show the copyright string in the site footer. Note that the string itself can be customised using the copyright parameter in the languages configuration. footer.showThemeAttribution true Whether or not to show the \u0026ldquo;powered by\u0026rdquo; theme attribution in the site footer. If you choose to disable this message, please consider attributing the theme somewhere else on your site (for example, on your about page). footer.showAppearanceSwitcher false Whether or not to show the appearance switcher in the site footer. The browser\u0026rsquo;s local storage is used to persist the visitor\u0026rsquo;s preference. footer.showScrollToTop true When set to true the scroll to top arrow is displayed. homepage.layout \u0026quot;page\u0026quot; The layout of the homepage. Valid values are page, profile or custom. When set to custom, you must provide your own layout by creating a /layouts/partials/home/custom.html file. Refer to the Homepage Layout section for more details. homepage.showRecent false Whether or not to display the recent articles list on the homepage. article.showDate true Whether or not article dates are displayed. article.showDateUpdated false Whether or not the dates articles were updated are displayed. article.showAuthor true Whether or not the author box is displayed in the article footer. article.showBreadcrumbs false Whether or not breadcrumbs are displayed in the article header. article.showDraftLabel true Whether or not the draft indicator is shown next to articles when site is built with --buildDrafts. article.showEdit false Whether or not the link to edit the article content should be displayed. article.editURL Not set When article.showEdit is active, the URL for the edit link. article.editAppendPath true When article.showEdit is active, whether or not the path to the current article should be appended to the URL set at article.editURL. article.showHeadingAnchors true Whether or not heading anchor links are displayed alongside headings within articles. article.showPagination true Whether or not the next/previous article links are displayed in the article footer. article.invertPagination false Whether or not to flip the direction of the next/previous article links. article.showReadingTime true Whether or not article reading times are displayed. article.showTableOfContents false Whether or not the table of contents is displayed on articles. article.showTaxonomies false Whether or not the taxonomies related to this article are displayed. article.showWordCount false Whether or not article word counts are displayed. article.showComments false Whether or not the comments partial is included after the article footer. article.sharingLinks Not set Which sharing links to display at the end of each article. When not provided, or set to false no links will be displayed. list.showBreadcrumbs false Whether or not breadcrumbs are displayed in the header on list pages. list.showTableOfContents false Whether or not the table of contents is displayed on list pages. list.showSummary false Whether or not article summaries are displayed on list pages. If a summary is not provided in the front matter, one will be auto generated using the summaryLength parameter in the site configuration. list.groupByYear true Whether or not articles are grouped by year on list pages. sitemap.excludedKinds [\u0026quot;taxonomy\u0026quot;, \u0026quot;term\u0026quot;] Kinds of content that should be excluded from the generated /sitemap.xml file. Refer to the Hugo docs for acceptable values. taxonomy.showTermCount true Whether or not the number of articles within a taxonomy term is displayed on the taxonomy listing. fathomAnalytics.site Not set The site code generated by Fathom Analytics for the website. Refer to the Analytics docs for more details. fathomAnalytics.domain Not set If using a custom domain with Fathom Analytics, provide it here to serve script.js from the custom domain. verification.google Not set The site verification string provided by Google to be included in the site metadata. verification.bing Not set The site verification string provided by Bing to be included in the site metadata. verification.pinterest Not set The site verification string provided by Pinterest to be included in the site metadata. verification.yandex Not set The site verification string provided by Yandex to be included in the site metadata. Other configuration files # The theme also includes a markup.toml configuration file. This file contains some important parameters that ensure that Hugo is correctly configured to generate sites built with Congo.\nAlways ensure this file is present in the config directory and that the required values are set. Failure to do so may cause certain features to fucntion incorrectly and could result in unintended behaviour.\n","date":"14 August 2020","permalink":"/blowfish/docs/configuration/","section":"Documentation","summary":"Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured.\nThe theme ships with a default configuration that gets you up and running with a basic blog or static website.","title":"Configuration"},{"content":" Congo brings your content to life. 😍 This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.\nSidenote: This page is just a standard Congo article listing and Hugo has been configured to generate a samples content type and display article summaries.\n","date":"14 August 2020","permalink":"/blowfish/samples/","section":"Content Samples","summary":"Congo brings your content to life. 😍 This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.","title":"Content Samples"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/icons/","section":"Tags","summary":"","title":"icons"},{"content":"Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.\nAdditionally, custom icons are also fully supported. Simply provide your own SVG icon assets by placing them in the assets/icons/ directory in the root of your project. Any icons in the icons directory will then be available to use throughout the theme.\nThe full list of built-in icons and their corresponding names can referenced below.\nIcon name Preview amazon apple bars blogger bug check circle-info codepen comment dev dribbble edit email facebook flickr foursquare github gitlab google hashnode instagram keybase kickstarter lastfm lightbulb link linkedin list mastodon medium microsoft moon orcid patreon pencil pinterest reddit researchgate search skull-crossbones slack snapchat soundcloud stack-overflow steam sun tag telegram tiktok triangle-exclamation tumblr twitch twitter whatsapp xmark youtube ","date":"14 August 2020","permalink":"/blowfish/samples/icons/","section":"Content Samples","summary":"Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.\nAdditionally, custom icons are also fully supported.","title":"Icons"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/sample/","section":"Tags","summary":"","title":"sample"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/shortcodes/","section":"Tags","summary":"","title":"shortcodes"},{"content":"","date":"14 August 2020","permalink":"/blowfish/tags/users/","section":"Tags","summary":"","title":"users"},{"content":" Real websites that are built with Congo. Website Details jamespanther.com Personal site - Theme author srisco.dev Personal site antoinesoetewey.com Personal site leif.io Personal site and Tech blog dr460nf1r3.org Personal site and Blog OCram85.com Personal site and Blog mackiser.github.io Personal site and Blog jamesmillner.dev Personal site and Blog jeremic.ca Personal site and Blog rohn.tech Personal site klimafreundlicher-kochen.de Food blog (in German) seyslee.github.io Tech blog (in Korean) datanalyze.be Professional site sneaky-potato.github.io Professional site and Blog kelset.dev Personal site docteurelsavancaster.com Professional site ruihao-li.github.io Personal site and Blog phalanxhead.dev Personal site and Blog Bible Multi Apps Personal site and Blog Jh123x Personal site and Blog sforzando LLC. and Inc. Corporate site and Blog Congo user? To add your site to this list, submit a pull request.\n","date":"14 August 2020","permalink":"/blowfish/users/","section":"Blowfish","summary":"Real websites that are built with Congo. Website Details jamespanther.com Personal site - Theme author srisco.dev Personal site antoinesoetewey.com Personal site leif.io Personal site and Tech blog dr460nf1r3.org Personal site and Blog OCram85.","title":"Users"},{"content":"","date":"13 August 2020","permalink":"/blowfish/tags/homepage/","section":"Tags","summary":"","title":"homepage"},{"content":"Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.\nThe layout of the homepage is controlled by the homepage.layout setting in the params.toml configuration file. Additionally, all layouts have the option to include a listing of recent articles.\nPage layout # The default layout is the page layout. It\u0026rsquo;s simply a normal content page that displays your Markdown content. It\u0026rsquo;s great for static websites and provides a lot of flexibility.\nTo enable the page layout, set homepage.layout = \u0026quot;page\u0026quot; in the params.toml configuration file.\nProfile layout # The profile layout is great for personal websites and blogs. It puts the author\u0026rsquo;s details front and centre by providing an image and links to social profiles.\nThe author information is provided in the languages configuration file. Refer to the Getting Started and Language Configuration sections for parameter details.\nAdditionally, any Markdown content that is provided in the homepage content will be placed below the author profile. This allows extra flexibility for displaying a bio or other custom content using shortcodes.\nTo enable the profile layout, set homepage.layout = \u0026quot;profile\u0026quot; in the params.toml configuration file.\nCustom layout # If the built-in homepage layouts aren\u0026rsquo;t sufficient for your needs, you have the option to provide your own custom layout. This allows you to have total control over the page content and essentially gives you a blank slate to work with.\nTo enable the custom layout, set homepage.layout = \u0026quot;custom\u0026quot; in the params.toml configuration file.\nWith the configuration value set, create a new custom.html file and place it in layouts/partials/home/custom.html. Now whatever is in the custom.html file will be placed in the content area of the site homepage. You may use whatever HTML, Tailwind, or Hugo templating functions you wish to define your layout.\nTo include recent articles on the custom layout, use the recent-articles.html partial.\nAs an example, the homepage on this site uses the custom layout to allow toggling between the profile and page layouts. Visit the GitHub repo to see how it works.\nRecent articles # All homepage layouts have the option of displaying recent articles below the main page content. To enable this, simply set the homepage.showRecent setting to true in the params.toml configuration file.\nThe articles listed in this section are derived from the mainSections setting which allows for whatever content types you are using on your website. For instance, if you had content sections for posts and projects you could set this setting to [\u0026quot;posts\u0026quot;, \u0026quot;projects\u0026quot;] and all the articles in these two sections would be used to populate the recent list. The theme expects this setting to be an array so if you only use one section for all your content, you should set this accordingly: [\u0026quot;blog\u0026quot;].\n","date":"13 August 2020","permalink":"/blowfish/docs/homepage-layout/","section":"Documentation","summary":"Congo provides a fully flexible homepage layout. There are two main templates to choose from with additional settings to adjust the design. Alternatively, you can also provide your own template and have complete control over the homepage content.","title":"Homepage Layout"},{"content":"","date":"13 August 2020","permalink":"/blowfish/tags/layouts/","section":"Tags","summary":"","title":"layouts"},{"content":"","date":"12 August 2020","permalink":"/blowfish/tags/front-matter/","section":"Tags","summary":"","title":"front matter"},{"content":"In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.\nFront matter parameter default values are inherited from the theme\u0026rsquo;s base configuration, so you only need to specify these parameters in your front matter when you want to override the default.\nName Default Description title Not set The name of the article. description Not set The text description for the article. It is used in the HTML metadata. externalUrl Not set If this article is published on a third-party website, the URL to this article. Providing a URL will prevent a content page being generated and any references to this article will link directly to the third-party website. editURL article.editURL When showEdit is active, the URL for the edit link. editAppendPath article.editAppendPath When showEdit is active, whether or not the path to the current article should be appended to the URL set at editURL. groupByYear list.groupByYear Whether or not articles are grouped by year on list pages. menu Not set When a value is provided, a link to this article will appear in the named menus. Valid values are main or footer. robots Not set String that indicates how robots should handle this article. If set, it will be output in the page head. Refer to Google\u0026rsquo;s docs for valid values. sharingLinks article.sharingLinks Which sharing links to display at the end of this article. When not provided, or set to false no links will be displayed. showAuthor article.showAuthor Whether or not the author box is displayed in the article footer. showBreadcrumbs article.showBreadcrumbs or list.showBreadcrumbs Whether the breadcrumbs are displayed in the article or list header. showDate article.showDate Whether or not the article date is displayed. The date is set using the date parameter. showDateUpdated article.showDateUpdated Whether or not the date the article was updated is displayed. The date is set using the lastmod parameter. showEdit article.showEdit Whether or not the link to edit the article content should be displayed. showHeadingAnchors article.showHeadingAnchors Whether or not heading anchor links are displayed alongside headings within this article. showPagination article.showPagination Whether or not the next/previous article links are displayed in the article footer. invertPagination article.invertPagination Whether or not to flip the direction of the next/previous article links. showReadingTime article.showReadingTime Whether or not the article reading time is displayed. showTaxonomies article.showTaxonomies Whether or not the taxonomies that relate to this article are displayed. showTableOfContents article.showTableOfContents Whether or not the table of contents is displayed on this article. showWordCount article.showWordCount Whether or not the article word count is displayed. showComments article.showComments Whether or not the comments partial is included after the article footer. showSummary list.showSummary Whether or not the article summary should be displayed on list pages. summary Auto generated using summaryLength (see site configuration) When showSummary is enabled, this is the Markdown string to be used as the summary for this article. xml true unless excluded by sitemap.excludedKinds Whether or not this article is included in the generated /sitemap.xml file. ","date":"12 August 2020","permalink":"/blowfish/docs/front-matter/","section":"Documentation","summary":"In addition to the default Hugo front matter parameters, Congo adds a number of additional options to customise the presentation of individual articles. All the available theme front matter parameters are listed below.","title":"Front Matter"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/icon/","section":"Tags","summary":"","title":"icon"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/lead/","section":"Tags","summary":"","title":"lead"},{"content":"","date":"11 August 2020","permalink":"/blowfish/tags/mermaid/","section":"Tags","summary":"","title":"mermaid"},{"content":"In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.\nAlert # alert outputs its contents as a stylised message box within your article. It\u0026rsquo;s useful for drawing attention to important information that you don\u0026rsquo;t want the reader to miss.\nThe input is written in Markdown so you can format it however you please.\nBy default, the alert is presented with an exclaimation triangle icon. To change the icon, include the icon name in the shortcode. Check out the icon shortcode for more details on using icons.\nExample:\n{{\u0026lt; alert \u0026gt;}} **Warning!** This action is destructive! {{\u0026lt; /alert \u0026gt;}} {{\u0026lt; alert \u0026#34;twitter\u0026#34; \u0026gt;}} Don\u0026#39;t forget to [follow me](https://twitter.com/jpanther) on Twitter. {{\u0026lt; /alert \u0026gt;}} Warning! This action is destructive! Don\u0026rsquo;t forget to follow me on Twitter. Badge # badge outputs a styled badge component which is useful for displaying metadata.\nExample:\n{{\u0026lt; badge \u0026gt;}} New article! {{\u0026lt; /badge \u0026gt;}} New article! Button # button outputs a styled button component which can be used to highlight a primary action. It has two optional variables href and target which can be used to specify the URL and target of the link.\nExample:\n{{\u0026lt; button href=\u0026#34;#button\u0026#34; target=\u0026#34;_self\u0026#34; \u0026gt;}} Call to action {{\u0026lt; /button \u0026gt;}} Call to action Chart # chart uses the Chart.js library to embed charts into articles using simple structured data. It supports a number of different chart styles and everything can be configured from within the shortcode. Simply provide the chart parameters between the shortcode tags and Chart.js will do the rest.\nRefer to the official Chart.js docs for details on syntax and supported chart types.\nExample:\n{{\u0026lt; chart \u0026gt;}} type: \u0026#39;bar\u0026#39;, data: { labels: [\u0026#39;Tomato\u0026#39;, \u0026#39;Blueberry\u0026#39;, \u0026#39;Banana\u0026#39;, \u0026#39;Lime\u0026#39;, \u0026#39;Orange\u0026#39;], datasets: [{ label: \u0026#39;# of votes\u0026#39;, data: [12, 19, 3, 5, 2, 3], }] } {{\u0026lt; /chart \u0026gt;}} You can see some additional Chart.js examples on the charts samples page.\nFigure # Congo includes a figure shortcode for adding images to content. The shortcode replaces the base Hugo functionality in order to provide additional performance benefits.\nWhen a provided image is a page resource, it will be optimised using Hugo Pipes and scaled in order to provide images appropriate to different device resolutions. If a static asset or URL to an external image is provided, it will be included as-is without any image processing by Hugo.\nThe figure shortcode accepts six parameters:\nParameter Description src Required. The local path/filename or URL of the image. When providing a path and filename, the theme will attempt to locate the image using the following lookup order: Firstly, as a page resource bundled with the page; then an asset in the assets/ directory; then finally, a static image in the static/ directory. alt Alternative text description for the image. caption Markdown for the image caption, which will be displayed below the image. class Additional CSS classes to apply to the image. href URL that the image should be linked to. default Special parameter to revert to default Hugo figure behaviour. Simply provide default=true and then use normal Hugo shortcode syntax. Congo also supports automatic conversion of images included using standard Markdown syntax. Simply use the following format and the theme will handle the rest:\n![Alt text](image.jpg \u0026#34;Image caption\u0026#34;) Example:\n{{\u0026lt; figure src=\u0026#34;abstract.jpg\u0026#34; alt=\u0026#34;Abstract purple artwork\u0026#34; caption=\u0026#34;Photo by [Jr Korpa](https://unsplash.com/@jrkorpa) on [Unsplash](https://unsplash.com/)\u0026#34; \u0026gt;}} \u0026lt;!-- OR --\u0026gt; ![Abstract purple artwork](abstract.jpg \u0026#34;Photo by [Jr Korpa](https://unsplash.com/@jrkorpa) on [Unsplash](https://unsplash.com/)\u0026#34;) Photo by Jr Korpa on Unsplash Icon # icon outputs an SVG icon and takes the icon name as its only parameter. The icon is scaled to match the current text size.\nExample:\n{{\u0026lt; icon \u0026#34;github\u0026#34; \u0026gt;}} Output: Icons are populated using Hugo pipelines which makes them very flexible. Congo includes a number of built-in icons for social, links and other purposes. Check the icon samples page for a full list of supported icons.\nCustom icons can be added by providing your own icon assets in the assets/icons/ directory of your project. The icon can then be referenced in the shortcode by using the SVG filename without the .svg extension.\nIcons can also be used in partials by calling the icon partial.\nKatex # The katex shortcode can be used to add mathematical expressions to article content using the KaTeX package. Refer to the online reference of supported TeX functions for the available syntax.\nTo include mathematical expressions in an article, simply place the shortcode anywhere with the content. It only needs to be included once per article and KaTeX will automatically render any markup on that page. Both inline and block notation are supported.\nInline notation can be generated by wrapping the expression in \\\\( and \\\\) delimiters. Alternatively, block notation can be generated using $$ delimiters.\nExample:\n{{\u0026lt; katex \u0026gt;}} \\\\(f(a,b,c) = (a^2+b^2+c^2)^3\\\\) \\(f(a,b,c) = (a^2+b^2+c^2)^3\\)\nCheck out the mathematical notation samples page for more examples.\nLead # lead is used to bring emphasis to the start of an article. It can be used to style an introduction, or to call out an important piece of information. Simply wrap any Markdown content in the lead shortcode.\nExample:\n{{\u0026lt; lead \u0026gt;}} When life gives you lemons, make lemonade. {{\u0026lt; /lead \u0026gt;}} When life gives you lemons, make lemonade. Mermaid # mermaid allows you to draw detailed diagrams and visualisations using text. It uses Mermaid under the hood and supports a wide variety of diagrams, charts and other output formats.\nSimply write your Mermaid syntax within the mermaid shortcode and let the plugin do the rest.\nRefer to the official Mermaid docs for details on syntax and supported diagram types.\nExample:\n{{\u0026lt; mermaid \u0026gt;}} graph LR; A[Lemons]--\u0026gt;B[Lemonade]; B--\u0026gt;C[Profit] {{\u0026lt; /mermaid \u0026gt;}} graph LR; A[Lemons]--\u003eB[Lemonade]; B--\u003eC[Profit] You can see some additional Mermaid examples on the diagrams and flowcharts samples page.\n","date":"11 August 2020","permalink":"/blowfish/docs/shortcodes/","section":"Documentation","summary":"In addition to all the default Hugo shortcodes, Congo adds a few extras for additional functionality.\nAlert # alert outputs its contents as a stylised message box within your article. It\u0026rsquo;s useful for drawing attention to important information that you don\u0026rsquo;t want the reader to miss.","title":"Shortcodes"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/analytics/","section":"Tags","summary":"","title":"analytics"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/comments/","section":"Tags","summary":"","title":"comments"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/favicons/","section":"Tags","summary":"","title":"favicons"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/partials/","section":"Tags","summary":"","title":"partials"},{"content":"Analytics # Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you\u0026rsquo;re interested you can use this affiliate link to receive $10 credit and try the service.\nFathom Analytics # To enable Fathom Analytics support, simply provide your Fathom site code in the config/_default/params.toml file. If you also use the custom domain feature of Fathom and would like to serve their script from your domain, you can also additionally provide the domain configuration value. If you don\u0026rsquo;t provide a domain value, the script will load directly from Fathom DNS.\n# config/_default/params.toml [fathomAnalytics] site = \u0026#34;ABC12345\u0026#34; domain = \u0026#34;llama.yoursite.com\u0026#34; Google Analytics # Google Analytics support is provided through the internal Hugo partial. Simply provide the googleAnalytics key in the config/_default/config.toml file and the script will be added automatically.\nBoth version 3 (analytics.js) and version 4 (gtag.js) are supported, based on the configuration value provided:\n# config/_default/config.toml # version 3 googleAnalytics = \u0026#34;UA-PROPERTY_ID\u0026#34; # version 4 googleAnalytics = \u0026#34;G-MEASUREMENT_ID\u0026#34; Custom analytics providers # If you wish to use a different analytics provider on your website you can also override the analytics partial and provide your own script. Simply create the file layouts/partials/analytics.html in your project and it will automatically include it in the \u0026lt;head\u0026gt; of the website.\nComments # To add comments to your articles, Congo includes support for a comments partial that is included at the base of each article page. Simply provide a layouts/partials/comments.html which contains the code required to display your chosen comments.\nYou can use either the built-in Hugo Disqus template, or provide your own custom code. Refer to the Hugo docs for further information.\nOnce the partial has been provided, finer control over where comments are displayed is then managed using the showComments parameter. This value can be set at the theme level in the params.toml config file, or on a per-article basis by including it in the front matter. The parameter defaults to false so it must be set to true in one of these locations in order for comments to be displayed.\nFavicons # Congo provides a default set of blank favicons to get started but you can provide your own assets to override them. The easiest way to obtain new favicon assets is to generate them using a third-party provider like favicon.io.\nIcon assets should be placed directly in the static/ folder of your website and named as per the listing below. If you use favicon.io, these will be the filenames that are automatically generated for you, but you can provide your own assets if you wish.\nstatic/ ├─ android-chrome-192x192.png ├─ android-chrome-512x512.png ├─ apple-touch-icon.png ├─ favicon-16x16.png ├─ favicon-32x32.png ├─ favicon.ico └─ site.webmanifest Alternatively, you can also completely override the default favicon behaviour and provide your own favicon HTML tags and assets. Simply provide a layouts/partials/favicons.html file in your project and this will be injected into the site \u0026lt;head\u0026gt; in place of the default assets.\nIcon # Similar to the icon shortcode, you can include icons in your own templates and partials by using Congo\u0026rsquo;s icon.html partial. The partial takes one parameter which is the name of the icon to be included.\nExample:\n{{ partial \u0026#34;icon.html\u0026#34; \u0026#34;github\u0026#34; }} Icons are populated using Hugo pipelines which makes them very flexible. Congo includes a number of built-in icons for social, links and other purposes. Check the icon samples page for a full list of supported icons.\nCustom icons can be added by providing your own icon assets in the assets/icons/ directory of your project. The icon can then be referenced in the partial by using the SVG filename without the .svg extension.\nIcons can also be used in article content by calling the icon shortcode.\nExtensions # Congo also provides for a number of extension partials that allow for expanding upon base functionality.\nArticle link # If you wish to insert additional code after article links, create a layouts/partials/extend-article-link.html file. This is especially powerful when combined with the badge shortcode which can be used to highlight metadata for certain articles.\nHead and Footer # The theme allows for inserting additional code directly into the \u0026lt;head\u0026gt; and \u0026lt;footer\u0026gt; sections of the template. These can be useful for providing scripts or other logic that isn\u0026rsquo;t part of the theme.\nSimply create either layouts/partials/extend-head.html or layouts/partials/extend-footer.html and these will automatically be included in your website build. Both partials are injected as the last items in \u0026lt;head\u0026gt; and \u0026lt;footer\u0026gt; so they can be used to override theme defaults.\n","date":"10 August 2020","permalink":"/blowfish/docs/partials/","section":"Documentation","summary":"Analytics # Congo provides built-in support for Fathom Analytics and Google Analytics. Fathom is a paid alternative to Google Analytics that respects user privacy. If you\u0026rsquo;re interested you can use this affiliate link to receive $10 credit and try the service.","title":"Partials"},{"content":"","date":"10 August 2020","permalink":"/blowfish/tags/privacy/","section":"Tags","summary":"","title":"privacy"},{"content":"","date":"9 August 2020","permalink":"/blowfish/tags/content/","section":"Tags","summary":"","title":"content"},{"content":"If you\u0026rsquo;ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.\nTip: If you\u0026rsquo;re new to Hugo, be sure to check out the official docs to learn more about the concept of page bundles and resources. The examples on this page can all be adapted to different scenarios but hopefully give you some ideas about how to approach formatting a particular content item for your individual project.\nBranch pages # Branch page bundles in Hugo cover items like the homepage, section listings, and taxonomy pages. The important thing to remember about branch bundles is that the filename for this content type is _index.md.\nCongo will honour the front matter parameters specified in branch pages and these will override the default settings for that particular page. For example, setting the title parameter in a branch page will allow overriding the page title.\nHomepage # Layout: layouts/index.html Content: content/_index.md The homepage in Congo is special in that it\u0026rsquo;s overarching design is controlled by the homepage layout config parameter. You can learn more about this in the Homepage Layout section.\nIf you want to add custom content to this page, you simply need to create a content/_index.md file. Anything in this file will then be included in your homepage.\nExample:\n--- title: \u0026#34;Welcome to Congo!\u0026#34; description: \u0026#34;This is a demo of adding content to the homepage.\u0026#34; --- Welcome to my website! I\u0026#39;m really happy you stopped by. This example sets a custom title and adds some additional text to the body of the page. Any Markdown formatted text is acceptable, including shortcodes, images and links.\nList pages # Layout: layouts/_default/list.html Content: content/../_index.md List pages group all the pages within into a section and provide a way for visitors to reach each page. A blog or portfolio are examples of a list page as they group together posts or projects.\nCreating a list page is as simple as making a sub-directory in the content folder. For example, to create a \u0026ldquo;Projects\u0026rdquo; section, you would create content/projects/. Then create a Markdown file for each of your projects.\nA list page will be generated by default, however to customise the content, you should also create an _index.md page in this new directory.\n. └── content └── projects ├── _index.md # /projects ├── first-project.md # /projects/first-project └── another-project ├── index.md # /projects/another-project └── project.jpg Hugo will generate URLs for the pages in your projects folder accordingly.\nJust like the homepage, content in the _index.md file will be output into the generated list index. Congo will then list any pages in this section below the content.\nExample:\n--- title: \u0026#34;Projects\u0026#34; description: \u0026#34;Learn about some of my projects.\u0026#34; cascade: showReadingTime: false --- This section contains all my current projects. In this example, the special cascade parameter is being used to hide the reading time on any sub-pages within this section. By doing this, any project pages will not have their reading time showing. This is a great way to override default theme parameters for an entire section without having to include them in every individual page.\nThe samples section of this site is an example of a list page.\nTaxonomy pages # List layout: layouts/_default/taxonomy.html Term layout: layouts/_default/term.html Content: content/../_index.md Taxonomy pages come in two forms - taxonomy lists and taxonomy terms. Lists display a listing of each of the terms within a given taxonomy, while terms display a list of pages that are related to a given term.\nThe terminology can get a little confusing so let\u0026rsquo;s explore an example using a taxonomy named animals.\nFirstly, to use taxonomies in Hugo, they have to be configured. This is done by creating a config file at config/_default/taxonomies.toml and defining the taxonomy name.\n# config/_default/taxonomies.toml animal = \u0026#34;animals\u0026#34; Hugo expects taxonomies to be listed using their singular and plural forms, so we add the singular animal equals the plural animals to create our example taxonomy.\nNow that our animals taxonomy exists, it needs to be added to individual content items. It\u0026rsquo;s as simple as inserting it into the front matter:\n--- title: \u0026#34;Into the Lion\u0026#39;s Den\u0026#34; description: \u0026#34;This week we\u0026#39;re learning about lions.\u0026#34; animals: [\u0026#34;lion\u0026#34;, \u0026#34;cat\u0026#34;] --- This has now created two terms within our animals taxonomy - lion and cat.\nAlthough it\u0026rsquo;s not obvious at this point, Hugo will now be generating list and term pages for this new taxonomy. By default the listing can be accessed at /animals/ and the term pages can be found at /animals/lion/ and /animals/cat/.\nThe list page will list all the terms contained within the taxonomy. In this example, navigating to /animals/ will show a page that has links for \u0026ldquo;lion\u0026rdquo; and \u0026ldquo;cat\u0026rdquo; which take visitors to the individual term pages.\nThe term pages will list all the pages contained within that term. These term lists are essentially the same as normal list pages and behave in much the same way.\nIn order to add custom content to taxonomy pages, simply create _index.md files in the content folder using the taxonomy name as the sub-directory name.\n. └── content └── animals ├── _index.md # /animals └── lion └── _index.md # /animals/lion Anything in these content files will now be placed onto the generated taxonomy pages. As with other content, the front matter variables can be used to override defaults. In this way you could have a tag named lion but override the title to be \u0026ldquo;Lion\u0026rdquo;.\nTo see how this looks in reality, check out the tags taxonomy listing on this site.\nLeaf pages # Layout: layouts/_default/single.html Content (standalone): content/../page-name.md Content (bundled): content/../page-name/index.md Leaf pages in Hugo are basically standard content pages. They are defined as pages that don\u0026rsquo;t contain any sub-pages. These could be things like an about page, or an individual blog post that lives in the blog section of the website.\nThe most important thing to remember about leaf pages is that unlike branch pages, leaf pages should be named index.md without an underscore. Leaf pages are also special in that they can be grouped together at the top level of the section and named with a unique name.\n. └── content └── blog ├── first-post.md # /blog/first-post ├── second-post.md # /blog/second-post └── third-post ├── index.md # /blog/third-post └── image.jpg When including assets in a page, like an image, a page bundle should be used. Page bundles are created using a sub-directory with an index.md file. Grouping the assets with the content in its own directory is important as many of the shortcodes and other theme logic assumes that resources are bundled alongside pages.\nExample:\n--- title: \u0026#34;My First Blog Post\u0026#34; date: 2022-01-25 description: \u0026#34;Welcome to my blog!\u0026#34; summary: \u0026#34;Learn more about me and why I am starting this blog.\u0026#34; tags: [\u0026#34;welcome\u0026#34;, \u0026#34;new\u0026#34;, \u0026#34;about\u0026#34;, \u0026#34;first\u0026#34;] --- _This_ is the content of my blog post. Leaf pages have a wide variety of front matter parameters that can be used to customise how they are displayed.\nExternal links # Congo has a special feature that allows links to external pages to appear alongside articles in the article listings. This is useful if you have content on third party websites like Medium, or research papers that you\u0026rsquo;d like to link to, without replicating the content in your Hugo site.\nIn order to create an external link article, some special front matter needs to be set:\n--- title: \u0026#34;My Medium post\u0026#34; date: 2022-01-25 externalUrl: \u0026#34;https://medium.com/\u0026#34; summary: \u0026#34;I wrote a post on Medium.\u0026#34; showReadingTime: false _build: render: \u0026#34;false\u0026#34; list: \u0026#34;local\u0026#34; --- Along with the normal front matter parameters like title and summary, the externalUrl parameter is used to tell Congo that this is not an ordinary article. The URL provided here will be where visitors are directed when they select this article.\nAdditionally, we use a special Hugo front matter parameter _build to prevent a normal page for this content being generated - there\u0026rsquo;s no point generating a page since we\u0026rsquo;re linking to an external URL!\nThe theme includes an archetype to make generating these external link articles simple. Just specify -k external when making new content.\nhugo new -k external posts/my-post.md Simple pages # Layout: layouts/_default/simple.html Front Matter: layout: \u0026quot;simple\u0026quot; Congo also includes a special layout for simple pages. The simple layout is a full-width template that just places Markdown content into the page without any special theme features.\nThe only features available in the simple layout are breadcrumbs and sharing links. However, the behaviour of these can still be controlled using the normal page front matter variables.\nTo enable the simple layout on a particular page, add the layout front matter variable with a value of \u0026quot;simple\u0026quot;:\n--- title: \u0026#34;My landing page\u0026#34; date: 2022-03-08 layout: \u0026#34;simple\u0026#34; --- This page content is now full-width. Custom layouts # One of the benefits of Hugo is that it makes it easy to create custom layouts for the whole site, individual sections or pages.\nLayouts follow all the normal Hugo templating rules and more information is available in the official Hugo docs.\nOverriding default layouts # Each of the content types discussed above lists the layout file that is used to generate each type of page. If this file is created in your local project it will override the theme template and thus can be used to customise the default style of the website.\nFor example, creating a layouts/_default/single.html file will allow the layout of leaf pages to be completely customised.\nCustom section layouts # It is also simple to create custom layouts for individual content sections. This is useful when you want to make a section that lists a certain type of content using a particular style.\nLet\u0026rsquo;s step through an example that creates a custom \u0026ldquo;Projects\u0026rdquo; page that lists projects using a special layout.\nIn order to do this, structure your content using the normal Hugo content rules and create a section for your projects. Additionally, create a new layout for the projects section by using the same directory name as the content and adding a list.html file.\n. └── content │ └── projects │ ├── _index.md │ ├── first-project.md │ └── second-project.md └── layouts └── projects └── list.html This list.html file will now override the default list template, but only for the projects section. Before we look at this file, lets first look at the individual project files.\n--- title: \u0026#34;Congo\u0026#34; date: 2021-08-11 icon: \u0026#34;github\u0026#34; description: \u0026#34;A theme for Hugo built with Tailwind CSS.\u0026#34; topics: [\u0026#34;Hugo\u0026#34;, \u0026#34;Web\u0026#34;, \u0026#34;Tailwind\u0026#34;] externalUrl: \u0026#34;https://github.com/jpanther/congo/\u0026#34; --- In this example we are assigning some metadata for each project that we can then use in our list template. There\u0026rsquo;s no page content, but there\u0026rsquo;s nothing stopping you from including it. It\u0026rsquo;s your own custom template after all!\nWith the projects defined, now we can create a list template that outputs the details of each project.\n{{ define \u0026#34;main\u0026#34; }} \u0026lt;section class=\u0026#34;mt-8\u0026#34;\u0026gt; {{ range .Pages }} \u0026lt;article class=\u0026#34;pb-6\u0026#34;\u0026gt; \u0026lt;a class=\u0026#34;flex\u0026#34; href=\u0026#34;{{ .Params.externalUrl }}\u0026#34;\u0026gt; \u0026lt;div class=\u0026#34;mr-3 text-3xl text-neutral-300\u0026#34;\u0026gt; \u0026lt;span class=\u0026#34;relative inline-block align-text-bottom\u0026#34;\u0026gt; {{ partial \u0026#34;icon.html\u0026#34; .Params.icon }} \u0026lt;/span\u0026gt; \u0026lt;/div\u0026gt; \u0026lt;div\u0026gt; \u0026lt;h3 class=\u0026#34;flex text-xl font-semibold\u0026#34;\u0026gt; {{ .Title }} \u0026lt;/h3\u0026gt; \u0026lt;p class=\u0026#34;text-sm text-neutral-400\u0026#34;\u0026gt; {{ .Description }} \u0026lt;/p\u0026gt; \u0026lt;/div\u0026gt; \u0026lt;/a\u0026gt; \u0026lt;/article\u0026gt; {{ end }} \u0026lt;/section\u0026gt; {{ end }} Although this is quite a straightforward example, you can see that it steps through each of the pages in this section (ie. each project), and then outputs HTML links to each project alongside an icon. The metadata in the front matter for each project is used to determine which information is displayed.\nKeep in mind that you\u0026rsquo;ll need to ensure the relevant styles and classes are available, which may require the Tailwind CSS to be recompiled. This is discussed in more detail in the Advanced Customisation section.\nWhen making custom templates like this one, it\u0026rsquo;s always easiest to take a look at how the default Congo template works and then use that as a guide. Remember, the Hugo docs are a great resource to learn more about creating templates too.\n","date":"9 August 2020","permalink":"/blowfish/docs/content-examples/","section":"Documentation","summary":"If you\u0026rsquo;ve been reading the documentation in order, you should now know about all the features and configurations available in Congo. This page is designed to pull everything together and offer some worked examples that you might like to use in your Hugo project.","title":"Content Examples"},{"content":"","date":"9 August 2020","permalink":"/blowfish/tags/example/","section":"Tags","summary":"","title":"example"},{"content":"This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing. 🚀\nYou can also use these content pages to define Hugo metadata like titles and descriptions that will be used for SEO and other purposes.\n","date":"8 August 2020","permalink":"/blowfish/tags/advanced/","section":"Tags","summary":"This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing.","title":"advanced"},{"content":"There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.\nIf you need further advice, post your questions on GitHub Discussions.\nHugo project structure # Before leaping into it, first a quick note about Hugo project structure and best practices for managing your content and theme customisations.\nIn summary: Never directly edit the theme files. Only make customisations in your Hugo project\u0026rsquo;s sub-directories, not in the themes directory itself. Congo is built to take advantage of all the standard Hugo practices. It is designed to allow all aspects of the theme to be customised and overriden without changing any of the core theme files. This allows for a seamless upgrade experience while giving you total control over the look and feel of your website.\nIn order to achieve this, you should never manually adjust any of the theme files directly. Whether you install using Hugo modules, as a git submodule or manually include the theme in your themes/ directory, you should always leave these files intact.\nThe correct way to adjust any theme behaviour is by overriding files using Hugo\u0026rsquo;s powerful file lookup order. In summary, the lookup order ensures any files you include in your project directory will automatically take precedence over any theme files.\nFor example, if you wanted to override the main article template in Congo, you can simply create your own layouts/_default/single.html file and place it in the root of your project. This file will then override the single.html from the theme without ever changing the theme itself. This works for any theme files - HTML templates, partials, shortcodes, config files, data, assets, etc.\nAs long as you follow this simple practice, you will always be able to update the theme (or test different theme versions) without worrying that you will lose any of your custom changes.\nColour schemes # Congo ships with a number of colour schemes out of the box. To change the basic colour scheme, you can set the colorScheme theme parameter. Refer to the Getting Started section to learn more about the built-in schemes.\nIn addition to the default schemes, you can also create your own and re-style the entire website to your liking. Schemes are created by by placing a \u0026lt;scheme-name\u0026gt;.css file in the assets/css/schemes/ folder. Once the file is created, simply refer to it by name in the theme configuration.\nCongo defines a three-colour palette that is used throughout the theme. The three colours are defined as neutral, primary and secondary variants, each containing ten shades of colour.\nDue to the way Tailwind CSS 3.0 calculates colour values with opacity, the colours specified in the scheme need to conform to a particular format by providing the red, green and blue colour values.\n:root { --color-primary-500: 139, 92, 246; } This example defines a CSS variable for the primary-500 colour with a red value of 139, green value of 92 and blue value of 246.\nUse one of the existing theme stylesheets as a template. You are free to define your own colours, but for some inspiration, check out the official Tailwind colour palette reference.\nOverriding the stylesheet # Sometimes you need to add a custom style to style your own HTML elements. Congo provides for this scenario by allowing you to override the default styles in your own CSS stylesheet. Simply create a custom.css file in your project\u0026rsquo;s assets/css/ folder.\nThe custom.css file will be minified by Hugo and loaded automatically after all the other theme styles which means anything in your custom file will take precedence over the defaults.\nAdjusting the font size # Changing the font size of your website is one example of overriding the default stylesheet. Congo makes this simple as it uses scaled font sizes throughout the theme which are derived from the base HTML font size. By default, Tailwind sets the default size to 12pt, but it can be changed to whatever value you prefer.\nCreate a custom.css file using the instructions above and add the following CSS declaration:\n/* Increase the default font size */ html { font-size: 13pt; } Simply by changing this one value, all the font sizes on your website will be adjusted to match this new size. Therefore, to increase the overall font sizes used, make the value greater than 12pt. Similarly, to decrease the font sizes, make the value less than 12pt.\nBuilding the theme CSS from source # If you\u0026rsquo;d like to make a major change, you can take advantage of Tailwind CSS\u0026rsquo;s JIT compiler and rebuild the entire theme CSS from scratch. This is useful if you want to adjust the Tailwind configuration or add extra Tailwind classes to the main stylesheet.\nNote: Building the theme manually is intended for advanced users. Let\u0026rsquo;s step through how building the Tailwind CSS works.\nTailwind configuration # In order to generate a CSS file that only contains the Tailwind classes that are actually being used the JIT compiler needs to scan through all the HTML templates and Markdown content files to check which styles are present in the markup. The compiler does this by looking at the tailwind.config.js file which is included in the root of the theme directory:\n// themes/congo/tailwind.config.js module.exports = { content: [ \u0026#34;./layouts/**/*.html\u0026#34;, \u0026#34;./content/**/*.{html,md}\u0026#34;, \u0026#34;./themes/congo/layouts/**/*.html\u0026#34;, \u0026#34;./themes/congo/content/**/*.{html,md}\u0026#34;, ], // and more... }; This default configuration has been included with these content paths so that you can easily generate your own CSS file without needing to modify it, provided you follow a particular project structure. Namely, you have to include Congo in your project as a subdirectory at themes/congo/. This means you cannot easily use Hugo Modules to install the theme and you must go down either the git submodule (recommended) or manual install routes. The Installation docs explain how to install the theme using either of these methods.\nProject structure # In order to take advantage of the default configuration, your project should look something like this\u0026hellip;\n. ├── assets │ └── css │ └── compiled │ └── main.css # this is the file we will generate ├── config # site config │ └── _default ├── content # site content │ ├── _index.md │ ├── projects │ │ └── _index.md │ └── blog │ └── _index.md ├── layouts # custom layouts for your site │ ├── partials │ │ └── extend-article-link.html │ ├── projects │ │ └── list.html │ └── shortcodes │ └── disclaimer.html └── themes └── congo # git submodule or manual theme install This example structure adds a new projects content type with its own custom layout along with a custom shortcode and extended partial. Provided the project follows this structure, all that\u0026rsquo;s required is to recompile the main.css file.\nInstall dependencies # In order for this to work you\u0026rsquo;ll need to change into the themes/congo/ directory and install the project dependencies. You\u0026rsquo;ll need npm on your local machine for this step.\ncd themes/congo npm install Run the Tailwind compiler # With the dependencies installed all that\u0026rsquo;s left is to use Tailwind CLI to invoke the JIT compiler. Navigate back to the root of your Hugo project and issue the following command:\ncd ../.. ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit It\u0026rsquo;s a bit of an ugly command due to the paths involved but essentially you\u0026rsquo;re calling Tailwind CLI and passing it the location of the Tailwind config file (the one we looked at above), where to find the theme\u0026rsquo;s main.css file and then where you want the compiled CSS file to be placed (it\u0026rsquo;s going into the assets/css/compiled/ folder of your Hugo project).\nThe config file will automatically inspect all the content and layouts in your project as well as all those in the theme and build a new CSS file that contains all the CSS required for your website. Due to the way Hugo handles file hierarchy, this file in your project will now automatically override the one that comes with the theme.\nEach time you make a change to your layouts and need new Tailwind CSS styles, you can simply re-run the command and generate the new CSS file. You can also add -w to the end of the command to run the JIT compiler in watch mode.\nMake a build script # To fully complete this solution, you can simplify this whole process by adding aliases for these commands, or do what I do and add a package.json to the root of your project which contains the necessary scripts\u0026hellip;\n// package.json { \u0026#34;name\u0026#34;: \u0026#34;my-website\u0026#34;, \u0026#34;version\u0026#34;: \u0026#34;1.0.0\u0026#34;, \u0026#34;description\u0026#34;: \u0026#34;\u0026#34;, \u0026#34;scripts\u0026#34;: { \u0026#34;server\u0026#34;: \u0026#34;hugo server -b http://localhost -p 8000\u0026#34;, \u0026#34;dev\u0026#34;: \u0026#34;NODE_ENV=development ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit -w\u0026#34;, \u0026#34;build\u0026#34;: \u0026#34;NODE_ENV=production ./themes/congo/node_modules/tailwindcss/lib/cli.js -c ./themes/congo/tailwind.config.js -i ./themes/congo/assets/css/main.css -o ./assets/css/compiled/main.css --jit\u0026#34; }, // and more... } Now when you want to work on designing your site, you can invoke npm run dev and the compiler will run in watch mode. When you\u0026rsquo;re ready to deploy, run npm run build and you\u0026rsquo;ll get a clean Tailwind CSS build.\n🙋‍♀️ If you need help, feel free to ask a question on GitHub Discussions.\n","date":"8 August 2020","permalink":"/blowfish/docs/advanced-customisation/","section":"Documentation","summary":"There are many ways you can make advanced changes to Congo. Read below to learn more about what can be customised and the best way of achieving your desired result.","title":"Advanced Customisation"},{"content":"","date":"8 August 2020","permalink":"/blowfish/tags/css/","section":"Tags","summary":"","title":"css"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/deployment/","section":"Tags","summary":"","title":"deployment"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/github/","section":"Tags","summary":"","title":"github"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/hosting/","section":"Tags","summary":"","title":"hosting"},{"content":"There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.\nCongo is built using relative URLs throughout the theme. This enables sites to easily be deployed to sub-folders and hosts like GitHub Pages. There\u0026rsquo;s usually no special configuration required for this to work as long as the baseURL parameter has been configured in the config.toml file.\nThe official Hugo Hosting and Deployment docs are the best place to learn how to deploy your site. The sections below contain some specific theme configuration details that can help you deploy smoothly with certain providers.\nChoose your provider:\nGitHub Pages Netlify Render Cloudflare Pages Shared hosting, VPS or private web server GitHub Pages # GitHub allows hosting on GitHub Pages using Actions. To enable this functionality, enable Pages on your repo and create a new Actions workflow to build and deploy your site.\nThe file needs to be in YAML format, placed within the .github/workflows/ directory of your GitHub repository and named with a .yml extension.\nImportant: Ensure you set the correct branch name under branches and in the deploy step if parameter to the source branch used in your project. # .github/workflows/gh-pages.yml name: GitHub Pages on: push: branches: - main jobs: build-deploy: runs-on: ubuntu-20.04 concurrency: group: ${{ github.workflow }}-${{ github.ref }} steps: - name: Checkout uses: actions/checkout@v3 with: submodules: true fetch-depth: 0 - name: Setup Hugo uses: peaceiris/actions-hugo@v2 with: hugo-version: \u0026#34;latest\u0026#34; - name: Build run: hugo --minify - name: Deploy uses: peaceiris/actions-gh-pages@v3 if: ${{ github.ref == \u0026#39;refs/heads/main\u0026#39; }} with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_branch: gh-pages publish_dir: ./public Push the config file to GitHub and the action should automatically run. It may fail the first time and you\u0026rsquo;ll need to visit the Settings \u0026gt; Pages section of your GitHub repo to check the source is correct. It should be set to use the gh-pages branch.\nOnce the settings are configured, re-run the action and the site should build and deploy correctly. You can consult the actions log to check everything deployed successfully.\nNetlify # To deploy to Netlify, create a new continuous deployment site and link it to your source code. The build settings can be left blank in the Netlify UI. You will only need to configure the domain you\u0026rsquo;ll be using.\nThen in the root of your site repository, create a netlify.toml file:\n# netlify.toml [build] command = \u0026#34;hugo mod get -u \u0026amp;\u0026amp; hugo --gc --minify -b $URL\u0026#34; publish = \u0026#34;public\u0026#34; [build.environment] NODE_ENV = \u0026#34;production\u0026#34; GO_VERSION = \u0026#34;1.16\u0026#34; TZ = \u0026#34;UTC\u0026#34; # Set to preferred timezone [context.production.environment] HUGO_VERSION = \u0026#34;0.100.2\u0026#34; HUGO_ENV = \u0026#34;production\u0026#34; [context.deploy-preview.environment] HUGO_VERSION = \u0026#34;0.100.2\u0026#34; This configuration assumes you are deploying Congo as a Hugo module. If you have installed the theme using another method, change the build command to simply hugo --gc --minify -b $URL.\nWhen you push the config file to your repo, Netlify should automatically deploy your site. You can check the deploy logs in the Netlify UI to check for any errors.\nRender # Deploying to Render is very straightforward and all configuration is via the Render UI.\nCreate a new Static Site and link it to your project\u0026rsquo;s code repository. Then simply configure the build command to be hugo --gc --minify and publish directory to be public.\nThe site will automatically build and deploy whenever you push a change to your repo.\nCloudflare Pages # Cloudflare offers the Pages service that can host Hugo blogs. It builds the site from a git repository and then hosts it on Cloudflare\u0026rsquo;s CDN. Follow their Hugo deployment guide to get started.\nThe Rocket Loader™ feature offered by Cloudflare tries to speed up rendering of web pages with JavaScript, but it breaks the appearance switcher in the theme. It can also cause an annoying light/dark screen flash when browsing your site due to scripts loading in the wrong order.\nThis problem can be fixed by disabling it:\nGo to the Cloudflare dashboard Click on your domain name in the list Click Optimization in the Speed section Scroll down to Rocket Loader™ and disable it Hugo sites built with Congo still load very quickly, even with this feature disabled.\nShared hosting, VPS or private web server # Using traditional web hosting, or deploying to your own web server, is as simple as building your Hugo site and transferring the files to your host.\nMake sure that the baseURL parameter in config.toml is set to the full URL to the root of your website (including any sub domains or sub-folders).\nThen build your site using hugo and copy the contents of the output directory to the root of your web server and you will be ready to go. By default, the output directory is named public.\nIf you need a hosting provider, check out Vultr or DigitalOcean. Signing up using these affiliate links will give you up to $100 in free credit so you can try the service.\n","date":"7 August 2020","permalink":"/blowfish/docs/hosting-deployment/","section":"Documentation","summary":"There are many ways to deploy your Hugo website built with Congo. The theme is designed to be flexible in almost any deployment scenario.\nCongo is built using relative URLs throughout the theme.","title":"Hosting \u0026 Deployment"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/netlify/","section":"Tags","summary":"","title":"netlify"},{"content":"","date":"7 August 2020","permalink":"/blowfish/tags/render/","section":"Tags","summary":"","title":"render"},{"content":"","date":"11 March 2019","permalink":"/blowfish/tags/html/","section":"Tags","summary":"","title":"html"},{"content":"","date":"11 March 2019","permalink":"/blowfish/tags/markdown/","section":"Tags","summary":"","title":"markdown"},{"content":"This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.\nHeadings # The following HTML \u0026lt;h1\u0026gt;—\u0026lt;h6\u0026gt; elements represent six levels of section headings. \u0026lt;h1\u0026gt; is the highest section level while \u0026lt;h6\u0026gt; is the lowest.\nH1 # H2 # H3 # H4 # H5 # H6 # Paragraph # Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.\nItatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.\nBlockquotes # The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a footer or cite element, and optionally with in-line changes such as annotations and abbreviations.\nBlockquote without attribution # Tiam, ad mint andaepu dandae nostion secatur sequo quae. Note that you can use Markdown syntax within a blockquote.\nBlockquote with attribution # Don\u0026rsquo;t communicate by sharing memory, share memory by communicating.\n— Rob Pike1\nTables # Tables aren\u0026rsquo;t part of the core Markdown spec, but Hugo supports supports them out-of-the-box.\nName Age Bob 27 Alice 23 Inline Markdown within tables # Italics Bold Code italics bold code Code Blocks # Code block with backticks # \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026#34;en\u0026#34;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026#34;utf-8\u0026#34; /\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; Code block indented with four spaces # \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026quot;en\u0026quot;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026quot;utf-8\u0026quot;\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; Code block with Hugo\u0026rsquo;s internal highlight shortcode # 1 2 3 4 5 6 7 8 9 10 \u0026lt;!DOCTYPE html\u0026gt; \u0026lt;html lang=\u0026#34;en\u0026#34;\u0026gt; \u0026lt;head\u0026gt; \u0026lt;meta charset=\u0026#34;utf-8\u0026#34;\u0026gt; \u0026lt;title\u0026gt;Example HTML5 Document\u0026lt;/title\u0026gt; \u0026lt;/head\u0026gt; \u0026lt;body\u0026gt; \u0026lt;p\u0026gt;Test\u0026lt;/p\u0026gt; \u0026lt;/body\u0026gt; \u0026lt;/html\u0026gt; List Types # Ordered List # First item Second item Third item Unordered List # List item Another item And another item Nested list # Fruit Apple Orange Banana Dairy Milk Cheese Other Elements — abbr, sub, sup, kbd, mark # GIF is a bitmap image format.\nH2O\nXn + Yn = Zn\nPress CTRL+ALT+Delete to end the session.\nMost salamanders are nocturnal, and hunt for insects, worms, and other small creatures.\nThe above quote is excerpted from Rob Pike\u0026rsquo;s talk about nothing during Gopherfest, November 18, 2015.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\n","date":"11 March 2019","permalink":"/blowfish/samples/markdown/","section":"Content Samples","summary":"\u003cp\u003eThis article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.\u003c/p\u003e","title":"Markdown"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/gist/","section":"Tags","summary":"","title":"gist"},{"content":"Hugo ships with several built-in shortcodes for rich content, along with a privacy config and a set of simple shortcodes that enable static and no-JS versions of various social media embeds.\nYouTube # Below is an example using the built-in youtube shortcode.\nTwitter # This example uses the twitter_simple shortcode to output a Tweet. It requires two named parameters user and id.\n“In addition to being more logical, asymmetry has the advantage that its complete appearance is far more optically effective than symmetry.”\n— Jan Tschichold pic.twitter.com/gcv7SrhvJb\n\u0026mdash; Graphic Design History (@DesignReviewed) January 17, 2019 Alternatively, the tweet shortcode can be used to embed a fully marked up Twitter card.\nGist # The gist shortcode can be used to embed a GitHub Gist. It requires two unnamed parameters: the username and ID of the Gist.\nVimeo # The vimeo_simple shortcode will embed a Vimeo video.\n","date":"10 March 2019","permalink":"/blowfish/samples/rich-content/","section":"Content Samples","summary":"This is an \u003cem\u003eexample\u003c/em\u003e of a \u003cstrong\u003erich\u003c/strong\u003e content summary.","title":"Rich Content"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/twitter/","section":"Tags","summary":"","title":"twitter"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/vimeo/","section":"Tags","summary":"","title":"vimeo"},{"content":"","date":"10 March 2019","permalink":"/blowfish/tags/youtube/","section":"Tags","summary":"","title":"youtube"},{"content":"","date":"8 March 2019","permalink":"/blowfish/tags/katex/","section":"Tags","summary":"","title":"katex"},{"content":"KaTeX can be used to render mathematical notation within articles.\nCongo will only bundle the KaTeX assets into your project if you make use of mathematical notation. In order for this to work, simply include the katex shortcode within the article. Any KaTeX syntax on that page will then be automatically rendered.\nUse the online reference of supported TeX functions for the available syntax.\nInline notation # Inline notation can be generated by wrapping the expression in \\\\( and \\\\) delimiters.\nExample:\n% KaTeX inline notation Inline notation: \\\\(\\varphi = \\dfrac{1+\\sqrt5}{2}= 1.6180339887…\\\\) Inline notation: \\(\\varphi = \\dfrac{1+\\sqrt5}{2}= 1.6180339887…\\)\nBlock notation # Alternatively, block notation can be generated using $$ delimiters. This will output the expression in its own HTML block.\nExample:\n% KaTeX block notation $$ \\varphi = 1+\\frac{1} {1+\\frac{1} {1+\\frac{1} {1+\\cdots} } } $$ $$ \\varphi = 1+\\frac{1} {1+\\frac{1} {1+\\frac{1} {1+\\cdots} } } $$\n","date":"8 March 2019","permalink":"/blowfish/samples/mathematical-notation/","section":"Content Samples","summary":"\u003cp\u003eKaTeX can be used to render mathematical notation within articles.\u003c/p\u003e","title":"Mathematical notation"},{"content":"","date":"8 March 2019","permalink":"/blowfish/tags/maths/","section":"Tags","summary":"","title":"maths"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/chart/","section":"Tags","summary":"","title":"chart"},{"content":"Congo includes support for Chart.js using the chart shortcode. Simply wrap the chart markup within the shortcode. Congo automatically themes charts to match the configured colorScheme parameter, however the colours can be customised using normal Chart.js syntax.\nRefer to the chart shortcode docs for more details.\nThe examples below are a small selection taken from the official Chart.js docs. You can also view the page source on GitHub to see the markup.\nBar chart # Line chart # Doughnut chart # ","date":"6 March 2019","permalink":"/blowfish/samples/charts/","section":"Content Samples","summary":"Congo includes Chart.js for powerful charts and data visualisations.","title":"Charts"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/diagram/","section":"Tags","summary":"","title":"diagram"},{"content":"Mermaid diagrams are supported in Congo using the mermaid shortcode. Simply wrap the diagram markup within the shortcode. Congo automatically themes Mermaid diagrams to match the configured colorScheme parameter.\nRefer to the mermaid shortcode docs for more details.\nThe examples below are a small selection taken from the official Mermaid docs. You can also view the page source on GitHub to see the markup.\nFlowchart # graph TD A[Christmas] --\u003e|Get money| B(Go shopping) B --\u003e C{Let me think} B --\u003e G[/Another/] C ==\u003e|One| D[Laptop] C --\u003e|Two| E[iPhone] C --\u003e|Three| F[Car] subgraph Section C D E F G end Sequence diagram # sequenceDiagram autonumber par Action 1 Alice-\u003e\u003eJohn: Hello John, how are you? and Action 2 Alice-\u003e\u003eBob: Hello Bob, how are you? end Alice-\u003e\u003e+John: Hello John, how are you? Alice-\u003e\u003e+John: John, can you hear me? John--\u003e\u003e-Alice: Hi Alice, I can hear you! Note right of John: John is perceptive John--\u003e\u003e-Alice: I feel great! loop Every minute John--\u003eAlice: Great! end Class diagram # classDiagram Animal \"1\" \u003c|-- Duck Animal \u003c|-- Fish Animal \u003c--o Zebra Animal : +int age Animal : +String gender Animal: +isMammal() Animal: +mate() class Duck{ +String beakColor +swim() +quack() } class Fish{ -int sizeInFeet -canEat() } class Zebra{ +bool is_wild +run() } Entity relationship diagram # erDiagram CUSTOMER }|..|{ DELIVERY-ADDRESS : has CUSTOMER ||--o{ ORDER : places CUSTOMER ||--o{ INVOICE : \"liable for\" DELIVERY-ADDRESS ||--o{ ORDER : receives INVOICE ||--|{ ORDER : covers ORDER ||--|{ ORDER-ITEM : includes PRODUCT-CATEGORY ||--|{ PRODUCT : contains PRODUCT ||--o{ ORDER-ITEM : \"ordered in\" ","date":"6 March 2019","permalink":"/blowfish/samples/diagrams-flowcharts/","section":"Content Samples","summary":"It\u0026rsquo;s easy to add diagrams and flowcharts to articles using Mermaid.","title":"Diagrams and Flowcharts"},{"content":"","date":"6 March 2019","permalink":"/blowfish/tags/graph/","section":"Tags","summary":"","title":"graph"},{"content":"","date":"5 March 2019","permalink":"/blowfish/tags/emoji/","section":"Tags","summary":"","title":"emoji"},{"content":"Emoji is supported throughout Congo by default. Emoji can be used in titles, menu items and article content.\nNote: The rendering of these glyphs depends on the browser and the platform. To style the emoji you can either use a third party emoji font or a font stack. Emoji replacements are automatic throughout Congo, so you can use shorthand codes in your content and front matter and they will be converted to their corresponding symbols at build time.\nExample: see_no_evil 🙈, hear_no_evil 🙉, speak_no_evil 🙊.\nThe Emoji cheat sheet is a useful reference for emoji shorthand codes.\n","date":"5 March 2019","permalink":"/blowfish/samples/emoji/","section":"Content Samples","summary":"📖🏞️🧗🏽🐉🧙🏽‍♂️🧚🏽👸","title":"Emoji 🪂"},{"content":"","date":"1 January 0001","permalink":"/blowfish/categories/","section":"Categories","summary":"","title":"Categories"},{"content":" A powerful, lightweight theme for Hugo built with Tailwind CSS. This is a demo site built entirely using Congo. It also contains a complete set of theme documentation. Congo is flexible and is great for both static page-based content (like this demo) or a traditional blog with a feed of recent posts.\nThis is a demo of the page layout. Switch layout \u0026orarr; Explore the sample pages to get a feel for what Congo can do. If you like what you see, check out the project on Github or read the Installation guide to get started.\nPhoto by Jippe Joosten on Unsplash. ","date":"1 January 0001","permalink":"/blowfish/s_index/","section":"Blowfish","summary":"A powerful, lightweight theme for Hugo built with Tailwind CSS. This is a demo site built entirely using Congo. It also contains a complete set of theme documentation. Congo is flexible and is great for both static page-based content (like this demo) or a traditional blog with a feed of recent posts.","title":"Welcome to Congo! 🎉"}] \ No newline at end of file diff --git a/docs/index.xml b/docs/index.xml index 57afe6e0..615b759e 100644 --- a/docs/index.xml +++ b/docs/index.xml @@ -1,5 +1,5 @@ -Blowfishhttps://nunocoracao.github.io/blowfish/Recent content on BlowfishHugo -- gohugo.ioenSun, 04 Sep 2022 00:00:00 +0000Streaming Wars and What Comes After…https://nunocoracao.github.io/blowfish/posts/202209-streaming-wars/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202209-streaming-wars/Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?Bulk User Add for Docker Business and Teamshttps://nunocoracao.github.io/blowfish/posts/202207-docker-bulk-add/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202207-docker-bulk-add/Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!How I Created My Homepage (for free) Using Docker, Hugo, and Firebasehttps://nunocoracao.github.io/blowfish/posts/202206-homepage-guide/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-homepage-guide/Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results.Nuno Coração – Meet the Mentorhttps://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview-copy/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview-copy/Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.Nuno Coração – Meet the Mentorhttps://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview/Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.Resumehttps://nunocoracao.github.io/blowfish/resume/Mon, 13 Jun 2022 21:28:51 +0100https://nunocoracao.github.io/blowfish/resume/Experience Company Link Role Dates Location Docker Staff Product Manager 2022 - Present Full Remote Lisbon, PT AWS Startup Loft Startup Advisor 2022 - Present Full Remote Lisbon, PT Truphone Group Product Manager 2021 - 2022 Hybrid Lisbon, PT Senior Product Manager 2020 - 2021 Vodafone Group Analytics Squad Lead 2019 - 2020 Lisbon, PT London, UK Senior Product Manager 2018 - 2019 Sky Deutschland Senior Product Architect 2016 - 2018 Munich, DE Skimic Founder 2016 - 2017 Munich, DE Vodafone Group Product Manager 2015 - 2016 Lisbon, PTLondon, UK NOS Product Manager 2014 - 2015 Lisbon, PT Solutions Architect 2012 - 2014 Inesc-ID Junior Researcher 2011 - 2012 Lisbon, PT Education School Link Degree Date Harvard Business School Online Entrepreneurship Essentials 2022 Disruptive Strategy 2022 Tecnico Lisboa MSc in Computer Science - Distributed Systems 2012 BSc, Computer Science 2010Abouthttps://nunocoracao.github.io/blowfish/about/Mon, 13 Jun 2022 20:55:37 +0100https://nunocoracao.github.io/blowfish/about/I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.Musichttps://nunocoracao.github.io/blowfish/music/Mon, 13 Jun 2022 20:55:37 +0100https://nunocoracao.github.io/blowfish/music/I started learning music by myself at the age of 14. I play several instruments and I love to record, compose and produce my own music. I&rsquo;ve been releasing my songs under the name &ldquo;Doppler Effect&rdquo; in the usual streaming services.Upgrading from Congo 1.xhttps://nunocoracao.github.io/blowfish/docs/version-2/upgrade/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/version-2/upgrade/Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release. -That said, there are some changes that require adjustments to existing sites that are built with Congo version 1.The Future of the Nintendo Switchhttps://nunocoracao.github.io/blowfish/posts/202109-the-future-of-nintendo/Thu, 09 Sep 2021 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202109-the-future-of-nintendo/Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?Installationhttps://nunocoracao.github.io/blowfish/docs/installation/Sun, 16 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/installation/Simply follow the standard Hugo Quick Start procedure to get up and running quickly. +Blowfishhttps://nunocoracao.github.io/blowfish/Recent content on BlowfishHugo -- gohugo.ioenMon, 13 Jun 2022 20:55:37 +0100Abouthttps://nunocoracao.github.io/blowfish/about/Mon, 13 Jun 2022 20:55:37 +0100https://nunocoracao.github.io/blowfish/about/I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. As a product person, my main goal is to understand my users and their specific needs, in order to deliver a product that truly improves their lives.Upgrading from Congo 1.xhttps://nunocoracao.github.io/blowfish/docs/version-2/upgrade/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/version-2/upgrade/Although Congo 2.0 contains a large number of changes, the theme has been designed to minimise the effort required to upgrade to the latest release. +That said, there are some changes that require adjustments to existing sites that are built with Congo version 1.Installationhttps://nunocoracao.github.io/blowfish/docs/installation/Sun, 16 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/installation/Simply follow the standard Hugo Quick Start procedure to get up and running quickly. Detailed installation instructions can be found below. Instructions for updating the theme are also available. Installation # These instructions will get you up and running using Hugo and Congo from a completely blank state.Getting Startedhttps://nunocoracao.github.io/blowfish/docs/getting-started/Sat, 15 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/getting-started/This section assumes you have already installed the Congo theme. The config files that ship with Congo contain all of the possible settings that the theme recognises. By default, many of these are commented out but you can simply uncomment them to activate or change a specific feature.Configurationhttps://nunocoracao.github.io/blowfish/docs/configuration/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/docs/configuration/Congo is a highly customisable theme and uses some of the latest Hugo features to simplify how it is configured. The theme ships with a default configuration that gets you up and running with a basic blog or static website.Iconshttps://nunocoracao.github.io/blowfish/samples/icons/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/samples/icons/Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. diff --git a/docs/posts/index.html b/docs/posts/index.html index 25206da9..740efef5 100644 --- a/docs/posts/index.html +++ b/docs/posts/index.html @@ -1,20 +1,21 @@ Posts · Blowfish - + - - + + -
Blowfish +

Posts

2022

Streaming Wars and What Comes After…

·1387 words·7 mins·0 views
Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?

Bulk User Add for Docker Business and Teams -↗ -↖

·290 words·0 views
Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!

How I Created My Homepage (for free) Using Docker, Hugo, and Firebase

·2892 words·14 mins·0 views
Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results.

Nuno Coração – Meet the Mentor -↗ -↖

·855 words·0 views
Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.

Nuno Coração – Meet the Mentor -↗ -↖

·855 words·0 views
Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.

2021

The Future of the Nintendo Switch

·1945 words·10 mins·0 views
Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?

Posts

There's no articles to list here yet.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/posts/index.xml b/docs/posts/index.xml index e4a8c7d8..154847e4 100644 --- a/docs/posts/index.xml +++ b/docs/posts/index.xml @@ -1 +1 @@ -Posts on Blowfishhttps://nunocoracao.github.io/blowfish/posts/Recent content in Posts on BlowfishHugo -- gohugo.ioenMon, 13 Jun 2022 20:55:37 +0100Streaming Wars and What Comes After…https://nunocoracao.github.io/blowfish/posts/202209-streaming-wars/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202209-streaming-wars/Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?Bulk User Add for Docker Business and Teamshttps://nunocoracao.github.io/blowfish/posts/202207-docker-bulk-add/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202207-docker-bulk-add/Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!How I Created My Homepage (for free) Using Docker, Hugo, and Firebasehttps://nunocoracao.github.io/blowfish/posts/202206-homepage-guide/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-homepage-guide/Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results.Nuno Coração – Meet the Mentorhttps://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview-copy/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview-copy/Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.Nuno Coração – Meet the Mentorhttps://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview/Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker.The Future of the Nintendo Switchhttps://nunocoracao.github.io/blowfish/posts/202109-the-future-of-nintendo/Thu, 09 Sep 2021 00:00:00 +0000https://nunocoracao.github.io/blowfish/posts/202109-the-future-of-nintendo/Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story? \ No newline at end of file +Posts on Blowfishhttps://nunocoracao.github.io/blowfish/posts/Recent content in Posts on BlowfishHugo -- gohugo.ioenMon, 13 Jun 2022 20:55:37 +0100 \ No newline at end of file diff --git a/docs/s_index/index.html b/docs/s_index/index.html index 6a51809c..276fe005 100644 --- a/docs/s_index/index.html +++ b/docs/s_index/index.html @@ -1,16 +1,22 @@ Welcome to Congo! 🎉 · Blowfish - + - - + + -

Welcome to Congo! 🎉

·102 words·1 min·0 views· +

banner

A powerful, lightweight theme for Hugo built with Tailwind CSS.

This is a demo site built entirely using Congo. It also contains a complete set of theme documentation. Congo is flexible and is great for both static page-based content (like this demo) or a traditional blog with a feed of recent posts.

This is a demo of the page layout. @@ -20,4 +26,5 @@ Switch layout ↻

Explore the → ←

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/charts/index.html b/docs/samples/charts/index.html index bb631428..8ccfe7ce 100644 --- a/docs/samples/charts/index.html +++ b/docs/samples/charts/index.html @@ -1,19 +1,25 @@ Charts · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Charts

·81 words·1 min·0 views
Table of Contents

Congo includes support for Chart.js using the chart shortcode. Simply wrap the chart markup within the shortcode. Congo automatically themes charts to match the configured colorScheme parameter, however the colours can be customised using normal Chart.js syntax.

Refer to the chart shortcode docs for more details.

The examples below are a small selection taken from the official Chart.js docs. You can also view the page source on GitHub to see the markup.

Bar chart #

-

Line chart #

-

Doughnut chart #

-
  1. Content Samples/

Charts

·81 words·1 min·0 views
Table of Contents

Congo includes support for Chart.js using the chart shortcode. Simply wrap the chart markup within the shortcode. Congo automatically themes charts to match the configured colorScheme parameter, however the colours can be customised using normal Chart.js syntax.

Refer to the chart shortcode docs for more details.

The examples below are a small selection taken from the official Chart.js docs. You can also view the page source on GitHub to see the markup.

Bar chart #

+

Line chart #

+

Doughnut chart #

+
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/diagrams-flowcharts/index.html b/docs/samples/diagrams-flowcharts/index.html index 97d414ad..0b84b653 100644 --- a/docs/samples/diagrams-flowcharts/index.html +++ b/docs/samples/diagrams-flowcharts/index.html @@ -1,16 +1,22 @@ Diagrams and Flowcharts · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Diagrams and Flowcharts

·250 words·2 mins·0 views
Table of Contents

Mermaid diagrams are supported in Congo using the mermaid shortcode. Simply wrap the diagram markup within the shortcode. Congo automatically themes Mermaid diagrams to match the configured colorScheme parameter.

Refer to the mermaid shortcode docs for more details.

The examples below are a small selection taken from the official Mermaid docs. You can also view the page source on GitHub to see the markup.

Flowchart #

graph TD + +
+ +
  1. Content Samples/

Diagrams and Flowcharts

·250 words·2 mins·0 views
Table of Contents

Mermaid diagrams are supported in Congo using the mermaid shortcode. Simply wrap the diagram markup within the shortcode. Congo automatically themes Mermaid diagrams to match the configured colorScheme parameter.

Refer to the mermaid shortcode docs for more details.

The examples below are a small selection taken from the official Mermaid docs. You can also view the page source on GitHub to see the markup.

Flowchart #

graph TD A[Christmas] -->|Get money| B(Go shopping) B --> C{Let me think} B --> G[/Another/] @@ -74,4 +80,5 @@ PRODUCT ||--o{ ORDER-ITEM : "ordered in"
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/emoji/index.html b/docs/samples/emoji/index.html index 8782db64..0ce15592 100644 --- a/docs/samples/emoji/index.html +++ b/docs/samples/emoji/index.html @@ -1,17 +1,24 @@ Emoji 🪂 · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Emoji 🪂

·97 words·1 min·0 views

Emoji is supported throughout Congo by default. Emoji can be used in titles, menu items and article content.

Note: The rendering of these glyphs depends on the browser and the platform. To style the emoji you can either use a third party emoji font or a font stack.

Emoji replacements are automatic throughout Congo, so you can use shorthand codes in your content and front matter and they will be converted to their corresponding symbols at build time.

Example: see_no_evil 🙈, hear_no_evil 🙉, speak_no_evil 🙊.

The Emoji cheat sheet is a useful reference for emoji shorthand codes.

  1. Content Samples/

Emoji 🪂

·97 words·1 min·0 views

Emoji is supported throughout Congo by default. Emoji can be used in titles, menu items and article content.

Note: The rendering of these glyphs depends on the browser and the platform. To style the emoji you can either use a third party emoji font or a font stack.

Emoji replacements are automatic throughout Congo, so you can use shorthand codes in your content and front matter and they will be converted to their corresponding symbols at build time.

Example: see_no_evil 🙈, hear_no_evil 🙉, speak_no_evil 🙊.

The Emoji cheat sheet is a useful reference for emoji shorthand codes.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/external/index.html b/docs/samples/external/index.html index d6dd06fe..b89b9413 100644 --- a/docs/samples/external/index.html +++ b/docs/samples/external/index.html @@ -1,14 +1,21 @@ An External Article · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

An External Article

·40 words·0 views

This page uses the externalUrl front matter parameter to link to an article outside of this Hugo website.

It’s great for things like linking to posts on Medium or to research papers you may have hosted on third party websites.

Blowfish
Author
Blowfish
  1. Content Samples/

An External Article

·40 words·0 views

This page uses the externalUrl front matter parameter to link to an article outside of this Hugo website.

It’s great for things like linking to posts on Medium or to research papers you may have hosted on third party websites.

Blowfish
Author
Blowfish
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/icons/index.html b/docs/samples/icons/index.html index 6138d3fd..f7649c61 100644 --- a/docs/samples/icons/index.html +++ b/docs/samples/icons/index.html @@ -1,18 +1,25 @@ Icons · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Icons

··140 words·1 min·0 views

Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.

Additionally, custom icons are also fully supported. Simply provide your own SVG icon assets by placing them in the assets/icons/ directory in the root of your project. Any icons in the icons directory will then be available to use throughout the theme.

The full list of built-in icons and their corresponding names can referenced below.

Icon namePreview
amazon
apple
bars
blogger
bug
check
circle-info
codepen
comment
dev
dribbble
edit
email
facebook
flickr
foursquare
github
gitlab
google
hashnode
instagram
keybase
kickstarter
lastfm
lightbulb
link
linkedin
list
mastodon
medium
microsoft
moon
orcid
patreon
pencil
pinterest
reddit
researchgate
search
skull-crossbones
slack
snapchat
soundcloud
stack-overflow
steam
sun
tag
telegram
tiktok
triangle-exclamation
tumblr
twitch
twitter
whatsapp
xmark
youtube
  1. Content Samples/

Icons

··140 words·1 min·0 views

Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode.

Additionally, custom icons are also fully supported. Simply provide your own SVG icon assets by placing them in the assets/icons/ directory in the root of your project. Any icons in the icons directory will then be available to use throughout the theme.

The full list of built-in icons and their corresponding names can referenced below.

Icon namePreview
amazon
apple
bars
blogger
bug
check
circle-info
codepen
comment
dev
dribbble
edit
email
facebook
flickr
foursquare
github
gitlab
google
hashnode
instagram
keybase
kickstarter
lastfm
lightbulb
link
linkedin
list
mastodon
medium
microsoft
moon
orcid
patreon
pencil
pinterest
reddit
researchgate
search
skull-crossbones
slack
snapchat
soundcloud
stack-overflow
steam
sun
tag
telegram
tiktok
triangle-exclamation
tumblr
twitch
twitter
whatsapp
xmark
youtube
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/index.html b/docs/samples/index.html index bf3e687e..15a90c3e 100644 --- a/docs/samples/index.html +++ b/docs/samples/index.html @@ -1,17 +1,24 @@ Content Samples · Blowfish - + - - + + -
Blowfish +

Content Samples

Congo brings your content to life. 😍

This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.

Sidenote: This page is just a standard Congo article listing and Hugo has been configured to generate a samples content type and display article summaries.

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. + +
+ +

Content Samples

Congo brings your content to life. 😍

This section contains some demo pages that show how Congo renders different types of content. You can also see an example taxonomy listing page.

Sidenote: This page is just a standard Congo article listing and Hugo has been configured to generate a samples content type and display article summaries.

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. Additionally, custom icons are also fully supported.

2019

Markdown

·472 words·3 mins·0 views

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.

Mathematical notation

·145 words·1 min·0 views

KaTeX can be used to render mathematical notation within articles.

Diagrams and Flowcharts

·250 words·2 mins·0 views
It’s easy to add diagrams and flowcharts to articles using Mermaid.

Charts

·81 words·1 min·0 views
Congo includes Chart.js for powerful charts and data visualisations.

Emoji 🪂

·97 words·1 min·0 views
📖🏞️🧗🏽🐉🧙🏽‍♂️🧚🏽👸

An External Article ↗ ↖

·40 words·0 views
The externalUrl front matter parameter can link to any URL.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/markdown/index.html b/docs/samples/markdown/index.html index 8c9b236a..7dfdf7d9 100644 --- a/docs/samples/markdown/index.html +++ b/docs/samples/markdown/index.html @@ -1,15 +1,21 @@ Markdown · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Markdown

·472 words·3 mins·0 views
Table of Contents

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

Headings #

The following HTML <h1>—<h6> elements represent six levels of section headings. <h1> is the highest section level while <h6> is the lowest.

H1 #

H2 #

H3 #

H4 #

H5 #
H6 #

Paragraph #

Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.

Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.

Blockquotes #

The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a footer or cite element, and optionally with in-line changes such as annotations and abbreviations.

Blockquote without attribution #

Tiam, ad mint andaepu dandae nostion secatur sequo quae. + +

+ +
  1. Content Samples/

Markdown

·472 words·3 mins·0 views
Table of Contents

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

Headings #

The following HTML <h1>—<h6> elements represent six levels of section headings. <h1> is the highest section level while <h6> is the lowest.

H1 #

H2 #

H3 #

H4 #

H5 #
H6 #

Paragraph #

Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.

Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.

Blockquotes #

The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a footer or cite element, and optionally with in-line changes such as annotations and abbreviations.

Blockquote without attribution #

Tiam, ad mint andaepu dandae nostion secatur sequo quae. Note that you can use Markdown syntax within a blockquote.

Blockquote with attribution #

Don’t communicate by sharing memory, share memory by communicating.
— Rob Pike1

Tables #

Tables aren’t part of the core Markdown spec, but Hugo supports supports them out-of-the-box.

NameAge
Bob27
Alice23

Inline Markdown within tables #

ItalicsBoldCode
italicsboldcode

Code Blocks #

Code block with backticks #

<!DOCTYPE html>
 <html lang="en">
   <head>
@@ -58,4 +64,5 @@
 →
 ←
↑
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/mathematical-notation/index.html b/docs/samples/mathematical-notation/index.html index 7356eb17..dee3399b 100644 --- a/docs/samples/mathematical-notation/index.html +++ b/docs/samples/mathematical-notation/index.html @@ -1,17 +1,23 @@ Mathematical notation · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Mathematical notation

·145 words·1 min·0 views
Table of Contents

KaTeX can be used to render mathematical notation within articles.

Congo will only bundle the KaTeX assets into your project if you make use of mathematical notation. In order for this to work, simply include the katex shortcode within the article. Any KaTeX syntax on that page will then be automatically rendered.

Use the online reference of supported TeX functions for the available syntax.

Inline notation #

Inline notation can be generated by wrapping the expression in \\( and \\) delimiters.

Example:

% KaTeX inline notation
+
+
+ +
  1. Content Samples/

Mathematical notation

·145 words·1 min·0 views
Table of Contents

KaTeX can be used to render mathematical notation within articles.

Congo will only bundle the KaTeX assets into your project if you make use of mathematical notation. In order for this to work, simply include the katex shortcode within the article. Any KaTeX syntax on that page will then be automatically rendered.

Use the online reference of supported TeX functions for the available syntax.

Inline notation #

Inline notation can be generated by wrapping the expression in \\( and \\) delimiters.

Example:

% KaTeX inline notation
 Inline notation: \\(\varphi = \dfrac{1+\sqrt5}{2}= 1.6180339887…\\)

Inline notation: \(\varphi = \dfrac{1+\sqrt5}{2}= 1.6180339887…\)

Block notation #

Alternatively, block notation can be generated using $$ delimiters. This will output the expression in its own HTML block.

Example:

% KaTeX block notation
 $$
@@ -28,4 +34,5 @@ $$
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/samples/rich-content/index.html b/docs/samples/rich-content/index.html index 4f35c70e..141affd8 100644 --- a/docs/samples/rich-content/index.html +++ b/docs/samples/rich-content/index.html @@ -1,15 +1,21 @@ Rich Content · Blowfish - + - - + + -
Blowfish +
  1. Content Samples/

Rich Content

·145 words·1 min·0 views
Table of Contents

Hugo ships with several built-in shortcodes for rich content, along with a privacy config and a set of simple shortcodes that enable static and no-JS versions of various social media embeds.

YouTube #

Below is an example using the built-in youtube shortcode.

Twitter #

This example uses the twitter_simple shortcode to output a Tweet. It requires two named parameters user and id.

Alternatively, the tweet shortcode can be used to embed a fully marked up Twitter card.

Gist #

The gist shortcode can be used to embed a GitHub Gist. It requires two unnamed parameters: the username and ID of the Gist.

Vimeo #

The vimeo_simple shortcode will embed a Vimeo video.

Sing Jan Swing - Kinetic Type
  1. Content Samples/

Rich Content

·145 words·1 min·0 views
Table of Contents

Hugo ships with several built-in shortcodes for rich content, along with a privacy config and a set of simple shortcodes that enable static and no-JS versions of various social media embeds.

YouTube #

Below is an example using the built-in youtube shortcode.

Twitter #

This example uses the twitter_simple shortcode to output a Tweet. It requires two named parameters user and id.

Alternatively, the tweet shortcode can be used to embed a fully marked up Twitter card.

Gist #

The gist shortcode can be used to embed a GitHub Gist. It requires two unnamed parameters: the username and ID of the Gist.

Vimeo #

The vimeo_simple shortcode will embed a Vimeo video.

Sing Jan Swing - Kinetic Type
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/sitemap.xml b/docs/sitemap.xml index 8a56df58..3cdbcfea 100644 --- a/docs/sitemap.xml +++ b/docs/sitemap.xml @@ -1 +1 @@ -https://nunocoracao.github.io/blowfish/tags/amazon/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/apple/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/disney/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/netflix/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/prediction/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/product/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/product/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/strategy/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/strategy/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/streaming/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202209-streaming-wars/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/wars/2022-09-04T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202207-docker-bulk-add/2022-07-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/docker/2022-07-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/docker/2022-07-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/docker-hub/2022-07-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/feature/2022-07-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/congo/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/development/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/development/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/environment/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/go/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202206-homepage-guide/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/hugo/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/tutorial/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/tutorial/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/vscode/2022-06-27T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/interview/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/interview/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/mentorcruise/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/mentorship/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/mentorship/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview-copy/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202206-mentorcruise-interview/2022-06-26T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/resume/2022-06-13T21:28:51+01:00daily0.5https://nunocoracao.github.io/blowfish/about/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/music/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/posts/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/tags/docs/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/new/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/version-2/upgrade/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/version-2/2022-01-19T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/disruption/2021-09-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/nintendo/2021-09-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/switch/2021-09-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/posts/202109-the-future-of-nintendo/2021-09-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/installation/2020-08-16T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/installation/2020-08-16T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/getting-started/2020-08-15T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/config/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/configuration/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/icons/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/icons/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/sample/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/shortcodes/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/users/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/users/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/homepage/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/homepage-layout/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/layouts/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/front-matter/2020-08-12T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/front-matter/2020-08-12T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/icon/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/lead/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/mermaid/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/shortcodes/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/analytics/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/comments/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/favicons/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/partials/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/partials/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/privacy/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/content/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/content-examples/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/example/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/advanced/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/advanced-customisation/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/css/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/deployment/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/github/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/hosting/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/hosting-deployment/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/netlify/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/render/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/html/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/markdown/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/markdown/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/gist/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/rich-content/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/twitter/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/vimeo/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/youtube/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/katex/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/mathematical-notation/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/maths/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/chart/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/charts/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/diagram/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/diagrams-flowcharts/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/graph/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/emoji/2019-03-05T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/emoji/2019-03-05T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/s_index/daily0.5 \ No newline at end of file +https://nunocoracao.github.io/blowfish/about/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/posts/2022-06-13T20:55:37+01:00daily0.5https://nunocoracao.github.io/blowfish/tags/docs/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/new/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/version-2/upgrade/2022-01-20T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/version-2/2022-01-19T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/installation/2020-08-16T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/installation/2020-08-16T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/getting-started/2020-08-15T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/config/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/configuration/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/icons/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/icons/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/sample/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/shortcodes/2022-03-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/users/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/users/2020-08-14T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/homepage/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/homepage-layout/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/layouts/2020-08-13T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/front-matter/2020-08-12T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/front-matter/2020-08-12T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/icon/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/lead/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/mermaid/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/shortcodes/2020-08-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/analytics/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/comments/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/favicons/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/partials/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/partials/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/privacy/2020-08-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/content/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/content-examples/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/example/2020-08-09T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/advanced/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/advanced-customisation/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/css/2020-08-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/deployment/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/github/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/hosting/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/docs/hosting-deployment/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/netlify/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/render/2020-08-07T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/html/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/markdown/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/markdown/2019-03-11T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/gist/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/rich-content/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/twitter/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/vimeo/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/youtube/2019-03-10T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/katex/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/mathematical-notation/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/maths/2019-03-08T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/chart/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/charts/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/diagram/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/diagrams-flowcharts/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/graph/2019-03-06T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/tags/emoji/2019-03-05T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/samples/emoji/2019-03-05T00:00:00+00:00daily0.5https://nunocoracao.github.io/blowfish/categories/daily0.5https://nunocoracao.github.io/blowfish/s_index/daily0.5 \ No newline at end of file diff --git a/docs/tags/advanced/index.html b/docs/tags/advanced/index.html index 93f454a7..d035acda 100644 --- a/docs/tags/advanced/index.html +++ b/docs/tags/advanced/index.html @@ -1,14 +1,21 @@ advanced · Blowfish - + - - + + -
Blowfish +

advanced

This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing. 🚀

You can also use these content pages to define Hugo metadata like titles and descriptions that will be used for SEO and other purposes.

2020

Advanced Customisation

1519 words·8 mins·0 views

advanced

This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing. 🚀

You can also use these content pages to define Hugo metadata like titles and descriptions that will be used for SEO and other purposes.

2020

Advanced Customisation

1519 words·8 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/analytics/index.html b/docs/tags/analytics/index.html index 185a1934..8b7b1cf2 100644 --- a/docs/tags/analytics/index.html +++ b/docs/tags/analytics/index.html @@ -1,14 +1,21 @@ analytics · Blowfish - + - - + + -

analytics

2020

Partials

751 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/chart/index.html b/docs/tags/chart/index.html index 6e00c5e8..89807a83 100644 --- a/docs/tags/chart/index.html +++ b/docs/tags/chart/index.html @@ -1,14 +1,21 @@ chart · Blowfish - + - - + + -

chart

2019

Charts

·81 words·1 min·0 views
Congo includes Chart.js for powerful charts and data visualisations.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/comments/index.html b/docs/tags/comments/index.html index 8b4d9b20..8c2341e3 100644 --- a/docs/tags/comments/index.html +++ b/docs/tags/comments/index.html @@ -1,14 +1,21 @@ comments · Blowfish - + - - + + -

comments

2020

Partials

751 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/config/index.html b/docs/tags/config/index.html index 162e3675..7b60cee4 100644 --- a/docs/tags/config/index.html +++ b/docs/tags/config/index.html @@ -1,14 +1,21 @@ config · Blowfish - + - - + + -

config

2020

Configuration

2127 words·10 mins·0 views

Front Matter

508 words·3 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/content/index.html b/docs/tags/content/index.html index ffbea332..d338dee3 100644 --- a/docs/tags/content/index.html +++ b/docs/tags/content/index.html @@ -1,14 +1,21 @@ content · Blowfish - + - - + + -

content

2020

Content Examples

2005 words·10 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/css/index.html b/docs/tags/css/index.html index 3fc57398..f7ff0307 100644 --- a/docs/tags/css/index.html +++ b/docs/tags/css/index.html @@ -1,14 +1,21 @@ css · Blowfish - + - - + + -

css

2020

Advanced Customisation

1519 words·8 mins·0 views

2019

Markdown

·472 words·3 mins·0 views

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/deployment/index.html b/docs/tags/deployment/index.html index ef187b2c..fe69b0a2 100644 --- a/docs/tags/deployment/index.html +++ b/docs/tags/deployment/index.html @@ -1,14 +1,21 @@ deployment · Blowfish - + - - + + -

deployment

2020

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/diagram/index.html b/docs/tags/diagram/index.html index b7be3f1a..c11ea40c 100644 --- a/docs/tags/diagram/index.html +++ b/docs/tags/diagram/index.html @@ -1,14 +1,21 @@ diagram · Blowfish - + - - + + -

diagram

2019

Diagrams and Flowcharts

·250 words·2 mins·0 views
It’s easy to add diagrams and flowcharts to articles using Mermaid.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/docs/index.html b/docs/tags/docs/index.html index 36920876..09bf9425 100644 --- a/docs/tags/docs/index.html +++ b/docs/tags/docs/index.html @@ -1,14 +1,21 @@ docs · Blowfish - + - - + + -
Blowfish +

docs

2022

Upgrading from Congo 1.x

1382 words·7 mins·0 views

What's New in 2.0 ✨

771 words·4 mins·0 views

2020

Installation

976 words·5 mins·0 views

Getting Started

897 words·5 mins·0 views

Configuration

2127 words·10 mins·0 views

Homepage Layout

478 words·3 mins·0 views

Front Matter

508 words·3 mins·0 views

Shortcodes

954 words·5 mins·0 views

Partials

751 words·4 mins·0 views

Advanced Customisation

1519 words·8 mins·0 views

Hosting & Deployment

822 words·4 mins·0 views

docs

2022

Upgrading from Congo 1.x

1382 words·7 mins·0 views

What's New in 2.0 ✨

771 words·4 mins·0 views

2020

Installation

976 words·5 mins·0 views

Getting Started

897 words·5 mins·0 views

Configuration

2127 words·10 mins·0 views

Homepage Layout

478 words·3 mins·0 views

Front Matter

508 words·3 mins·0 views

Shortcodes

954 words·5 mins·0 views

Partials

751 words·4 mins·0 views

Advanced Customisation

1519 words·8 mins·0 views

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/emoji/index.html b/docs/tags/emoji/index.html index fc8195c5..33eccef1 100644 --- a/docs/tags/emoji/index.html +++ b/docs/tags/emoji/index.html @@ -1,14 +1,21 @@ emoji · Blowfish - + - - + + -

emoji

2019

Emoji 🪂

·97 words·1 min·0 views
📖🏞️🧗🏽🐉🧙🏽‍♂️🧚🏽👸
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/example/index.html b/docs/tags/example/index.html index eb2e6b31..5a4624a8 100644 --- a/docs/tags/example/index.html +++ b/docs/tags/example/index.html @@ -1,14 +1,21 @@ example · Blowfish - + - - + + -

example

2020

Content Examples

2005 words·10 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/favicons/index.html b/docs/tags/favicons/index.html index 3c2cb695..8bf8c042 100644 --- a/docs/tags/favicons/index.html +++ b/docs/tags/favicons/index.html @@ -1,14 +1,21 @@ favicons · Blowfish - + - - + + -

favicons

2020

Partials

751 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/front-matter/index.html b/docs/tags/front-matter/index.html index 18bb24c3..0be5ddd2 100644 --- a/docs/tags/front-matter/index.html +++ b/docs/tags/front-matter/index.html @@ -1,14 +1,21 @@ front matter · Blowfish - + - - + + -

front matter

2020

Front Matter

508 words·3 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/gist/index.html b/docs/tags/gist/index.html index b0b271b3..acdc8517 100644 --- a/docs/tags/gist/index.html +++ b/docs/tags/gist/index.html @@ -1,14 +1,21 @@ gist · Blowfish - + - - + + -

gist

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/github/index.html b/docs/tags/github/index.html index 7b6b56d6..6b3de78f 100644 --- a/docs/tags/github/index.html +++ b/docs/tags/github/index.html @@ -1,14 +1,21 @@ github · Blowfish - + - - + + -

github

2020

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/graph/index.html b/docs/tags/graph/index.html index 68e27c5d..bf0f44dc 100644 --- a/docs/tags/graph/index.html +++ b/docs/tags/graph/index.html @@ -1,14 +1,21 @@ graph · Blowfish - + - - + + -

graph

2019

Charts

·81 words·1 min·0 views
Congo includes Chart.js for powerful charts and data visualisations.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/homepage/index.html b/docs/tags/homepage/index.html index ba29ee47..459ccb30 100644 --- a/docs/tags/homepage/index.html +++ b/docs/tags/homepage/index.html @@ -1,14 +1,21 @@ homepage · Blowfish - + - - + + -

homepage

2020

Homepage Layout

478 words·3 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/hosting/index.html b/docs/tags/hosting/index.html index 3603fea7..e11ac0c2 100644 --- a/docs/tags/hosting/index.html +++ b/docs/tags/hosting/index.html @@ -1,14 +1,21 @@ hosting · Blowfish - + - - + + -

hosting

2020

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/html/index.html b/docs/tags/html/index.html index b5bbb828..1d53a372 100644 --- a/docs/tags/html/index.html +++ b/docs/tags/html/index.html @@ -1,14 +1,21 @@ html · Blowfish - + - - + + -

html

2019

Markdown

·472 words·3 mins·0 views

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/icon/index.html b/docs/tags/icon/index.html index 111d19a8..ef1eb7d1 100644 --- a/docs/tags/icon/index.html +++ b/docs/tags/icon/index.html @@ -1,14 +1,21 @@ icon · Blowfish - + - - + + -

icon

2020

Shortcodes

954 words·5 mins·0 views

Partials

751 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/icons/index.html b/docs/tags/icons/index.html index 65dadf4c..b9c20600 100644 --- a/docs/tags/icons/index.html +++ b/docs/tags/icons/index.html @@ -1,15 +1,22 @@ icons · Blowfish - + - - + + -
Blowfish +

icons

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. + +
+ +

icons

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. Additionally, custom icons are also fully supported.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/index.html b/docs/tags/index.html index 4c87dbcb..798801f7 100644 --- a/docs/tags/index.html +++ b/docs/tags/index.html @@ -1,68 +1,52 @@ Tags · Blowfish - + - - + + -
Blowfish +

Tags

Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.

This area could be used to add some extra decriptive text to each taxonomy. Check out the advanced tag below to see how to take this concept even further.

+ +

Tags

Congo has full support for Hugo taxonomies and will adapt to any taxonomy set up. Taxonomy listings like this one also support custom content to be displayed above the list of terms.

This area could be used to add some extra decriptive text to each taxonomy. Check out the advanced tag below to see how to take this concept even further.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/index.xml b/docs/tags/index.xml index 6928b0ce..cfd17335 100644 --- a/docs/tags/index.xml +++ b/docs/tags/index.xml @@ -1 +1 @@ -Tags on Blowfishhttps://nunocoracao.github.io/blowfish/tags/Recent content in Tags on BlowfishHugo -- gohugo.ioenSun, 04 Sep 2022 00:00:00 +0000Amazonhttps://nunocoracao.github.io/blowfish/tags/amazon/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/amazon/Applehttps://nunocoracao.github.io/blowfish/tags/apple/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/apple/Disneyhttps://nunocoracao.github.io/blowfish/tags/disney/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/disney/Netflixhttps://nunocoracao.github.io/blowfish/tags/netflix/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/netflix/Predictionhttps://nunocoracao.github.io/blowfish/tags/prediction/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/prediction/Producthttps://nunocoracao.github.io/blowfish/tags/product/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/product/Strategyhttps://nunocoracao.github.io/blowfish/tags/strategy/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/strategy/Streaminghttps://nunocoracao.github.io/blowfish/tags/streaming/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/streaming/Warshttps://nunocoracao.github.io/blowfish/tags/wars/Sun, 04 Sep 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/wars/Dockerhttps://nunocoracao.github.io/blowfish/tags/docker/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/docker/Docker Hubhttps://nunocoracao.github.io/blowfish/tags/docker-hub/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/docker-hub/Featurehttps://nunocoracao.github.io/blowfish/tags/feature/Wed, 27 Jul 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/feature/Congohttps://nunocoracao.github.io/blowfish/tags/congo/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/congo/Developmenthttps://nunocoracao.github.io/blowfish/tags/development/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/development/Environmenthttps://nunocoracao.github.io/blowfish/tags/environment/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/environment/Gohttps://nunocoracao.github.io/blowfish/tags/go/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/go/Hugohttps://nunocoracao.github.io/blowfish/tags/hugo/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/hugo/Tutorialhttps://nunocoracao.github.io/blowfish/tags/tutorial/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/tutorial/VSCodehttps://nunocoracao.github.io/blowfish/tags/vscode/Mon, 27 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/vscode/Interviewhttps://nunocoracao.github.io/blowfish/tags/interview/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/interview/Mentorcruisehttps://nunocoracao.github.io/blowfish/tags/mentorcruise/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/mentorcruise/Mentorshiphttps://nunocoracao.github.io/blowfish/tags/mentorship/Sun, 26 Jun 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/mentorship/docshttps://nunocoracao.github.io/blowfish/tags/docs/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/docs/newhttps://nunocoracao.github.io/blowfish/tags/new/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/new/Disruptionhttps://nunocoracao.github.io/blowfish/tags/disruption/Thu, 09 Sep 2021 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/disruption/Nintendohttps://nunocoracao.github.io/blowfish/tags/nintendo/Thu, 09 Sep 2021 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/nintendo/Switchhttps://nunocoracao.github.io/blowfish/tags/switch/Thu, 09 Sep 2021 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/switch/installationhttps://nunocoracao.github.io/blowfish/tags/installation/Sun, 16 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/installation/confighttps://nunocoracao.github.io/blowfish/tags/config/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/config/iconshttps://nunocoracao.github.io/blowfish/tags/icons/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/icons/samplehttps://nunocoracao.github.io/blowfish/tags/sample/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/sample/shortcodeshttps://nunocoracao.github.io/blowfish/tags/shortcodes/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/shortcodes/usershttps://nunocoracao.github.io/blowfish/tags/users/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/users/homepagehttps://nunocoracao.github.io/blowfish/tags/homepage/Thu, 13 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/homepage/layoutshttps://nunocoracao.github.io/blowfish/tags/layouts/Thu, 13 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/layouts/front matterhttps://nunocoracao.github.io/blowfish/tags/front-matter/Wed, 12 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/front-matter/iconhttps://nunocoracao.github.io/blowfish/tags/icon/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/icon/leadhttps://nunocoracao.github.io/blowfish/tags/lead/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/lead/mermaidhttps://nunocoracao.github.io/blowfish/tags/mermaid/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/mermaid/analyticshttps://nunocoracao.github.io/blowfish/tags/analytics/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/analytics/commentshttps://nunocoracao.github.io/blowfish/tags/comments/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/comments/faviconshttps://nunocoracao.github.io/blowfish/tags/favicons/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/favicons/partialshttps://nunocoracao.github.io/blowfish/tags/partials/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/partials/privacyhttps://nunocoracao.github.io/blowfish/tags/privacy/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/privacy/contenthttps://nunocoracao.github.io/blowfish/tags/content/Sun, 09 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/content/examplehttps://nunocoracao.github.io/blowfish/tags/example/Sun, 09 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/example/advancedhttps://nunocoracao.github.io/blowfish/tags/advanced/Sat, 08 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/advanced/This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing.csshttps://nunocoracao.github.io/blowfish/tags/css/Sat, 08 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/css/deploymenthttps://nunocoracao.github.io/blowfish/tags/deployment/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/deployment/githubhttps://nunocoracao.github.io/blowfish/tags/github/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/github/hostinghttps://nunocoracao.github.io/blowfish/tags/hosting/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/hosting/netlifyhttps://nunocoracao.github.io/blowfish/tags/netlify/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/netlify/renderhttps://nunocoracao.github.io/blowfish/tags/render/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/render/htmlhttps://nunocoracao.github.io/blowfish/tags/html/Mon, 11 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/html/markdownhttps://nunocoracao.github.io/blowfish/tags/markdown/Mon, 11 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/markdown/gisthttps://nunocoracao.github.io/blowfish/tags/gist/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/gist/twitterhttps://nunocoracao.github.io/blowfish/tags/twitter/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/twitter/vimeohttps://nunocoracao.github.io/blowfish/tags/vimeo/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/vimeo/youtubehttps://nunocoracao.github.io/blowfish/tags/youtube/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/youtube/katexhttps://nunocoracao.github.io/blowfish/tags/katex/Fri, 08 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/katex/mathshttps://nunocoracao.github.io/blowfish/tags/maths/Fri, 08 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/maths/charthttps://nunocoracao.github.io/blowfish/tags/chart/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/chart/diagramhttps://nunocoracao.github.io/blowfish/tags/diagram/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/diagram/graphhttps://nunocoracao.github.io/blowfish/tags/graph/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/graph/emojihttps://nunocoracao.github.io/blowfish/tags/emoji/Tue, 05 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/emoji/ \ No newline at end of file +Tags on Blowfishhttps://nunocoracao.github.io/blowfish/tags/Recent content in Tags on BlowfishHugo -- gohugo.ioenThu, 20 Jan 2022 00:00:00 +0000docshttps://nunocoracao.github.io/blowfish/tags/docs/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/docs/newhttps://nunocoracao.github.io/blowfish/tags/new/Thu, 20 Jan 2022 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/new/installationhttps://nunocoracao.github.io/blowfish/tags/installation/Sun, 16 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/installation/confighttps://nunocoracao.github.io/blowfish/tags/config/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/config/iconshttps://nunocoracao.github.io/blowfish/tags/icons/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/icons/samplehttps://nunocoracao.github.io/blowfish/tags/sample/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/sample/shortcodeshttps://nunocoracao.github.io/blowfish/tags/shortcodes/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/shortcodes/usershttps://nunocoracao.github.io/blowfish/tags/users/Fri, 14 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/users/homepagehttps://nunocoracao.github.io/blowfish/tags/homepage/Thu, 13 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/homepage/layoutshttps://nunocoracao.github.io/blowfish/tags/layouts/Thu, 13 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/layouts/front matterhttps://nunocoracao.github.io/blowfish/tags/front-matter/Wed, 12 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/front-matter/iconhttps://nunocoracao.github.io/blowfish/tags/icon/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/icon/leadhttps://nunocoracao.github.io/blowfish/tags/lead/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/lead/mermaidhttps://nunocoracao.github.io/blowfish/tags/mermaid/Tue, 11 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/mermaid/analyticshttps://nunocoracao.github.io/blowfish/tags/analytics/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/analytics/commentshttps://nunocoracao.github.io/blowfish/tags/comments/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/comments/faviconshttps://nunocoracao.github.io/blowfish/tags/favicons/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/favicons/partialshttps://nunocoracao.github.io/blowfish/tags/partials/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/partials/privacyhttps://nunocoracao.github.io/blowfish/tags/privacy/Mon, 10 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/privacy/contenthttps://nunocoracao.github.io/blowfish/tags/content/Sun, 09 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/content/examplehttps://nunocoracao.github.io/blowfish/tags/example/Sun, 09 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/example/advancedhttps://nunocoracao.github.io/blowfish/tags/advanced/Sat, 08 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/advanced/This is the advanced tag. Just like other listing pages in Congo, you can add custom content to individual taxonomy terms and it will be displayed at the top of the term listing.csshttps://nunocoracao.github.io/blowfish/tags/css/Sat, 08 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/css/deploymenthttps://nunocoracao.github.io/blowfish/tags/deployment/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/deployment/githubhttps://nunocoracao.github.io/blowfish/tags/github/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/github/hostinghttps://nunocoracao.github.io/blowfish/tags/hosting/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/hosting/netlifyhttps://nunocoracao.github.io/blowfish/tags/netlify/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/netlify/renderhttps://nunocoracao.github.io/blowfish/tags/render/Fri, 07 Aug 2020 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/render/htmlhttps://nunocoracao.github.io/blowfish/tags/html/Mon, 11 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/html/markdownhttps://nunocoracao.github.io/blowfish/tags/markdown/Mon, 11 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/markdown/gisthttps://nunocoracao.github.io/blowfish/tags/gist/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/gist/twitterhttps://nunocoracao.github.io/blowfish/tags/twitter/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/twitter/vimeohttps://nunocoracao.github.io/blowfish/tags/vimeo/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/vimeo/youtubehttps://nunocoracao.github.io/blowfish/tags/youtube/Sun, 10 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/youtube/katexhttps://nunocoracao.github.io/blowfish/tags/katex/Fri, 08 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/katex/mathshttps://nunocoracao.github.io/blowfish/tags/maths/Fri, 08 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/maths/charthttps://nunocoracao.github.io/blowfish/tags/chart/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/chart/diagramhttps://nunocoracao.github.io/blowfish/tags/diagram/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/diagram/graphhttps://nunocoracao.github.io/blowfish/tags/graph/Wed, 06 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/graph/emojihttps://nunocoracao.github.io/blowfish/tags/emoji/Tue, 05 Mar 2019 00:00:00 +0000https://nunocoracao.github.io/blowfish/tags/emoji/ \ No newline at end of file diff --git a/docs/tags/installation/index.html b/docs/tags/installation/index.html index 18b9fb25..26a27fc1 100644 --- a/docs/tags/installation/index.html +++ b/docs/tags/installation/index.html @@ -1,14 +1,21 @@ installation · Blowfish - + - - + + -

installation

2020

Installation

976 words·5 mins·0 views

Getting Started

897 words·5 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/katex/index.html b/docs/tags/katex/index.html index e89f8c55..9753f6d6 100644 --- a/docs/tags/katex/index.html +++ b/docs/tags/katex/index.html @@ -1,14 +1,21 @@ katex · Blowfish - + - - + + -

katex

2019

Mathematical notation

·145 words·1 min·0 views

KaTeX can be used to render mathematical notation within articles.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/layouts/index.html b/docs/tags/layouts/index.html index b3d7cc34..17a8cc88 100644 --- a/docs/tags/layouts/index.html +++ b/docs/tags/layouts/index.html @@ -1,14 +1,21 @@ layouts · Blowfish - + - - + + -

layouts

2020

Homepage Layout

478 words·3 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/lead/index.html b/docs/tags/lead/index.html index ae6c077f..42f969e2 100644 --- a/docs/tags/lead/index.html +++ b/docs/tags/lead/index.html @@ -1,14 +1,21 @@ lead · Blowfish - + - - + + -

lead

2020

Shortcodes

954 words·5 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/markdown/index.html b/docs/tags/markdown/index.html index 59882d6f..8202abda 100644 --- a/docs/tags/markdown/index.html +++ b/docs/tags/markdown/index.html @@ -1,14 +1,21 @@ markdown · Blowfish - + - - + + -

markdown

2019

Markdown

·472 words·3 mins·0 views

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/maths/index.html b/docs/tags/maths/index.html index ad0fbbff..4020857b 100644 --- a/docs/tags/maths/index.html +++ b/docs/tags/maths/index.html @@ -1,14 +1,21 @@ maths · Blowfish - + - - + + -

maths

2019

Mathematical notation

·145 words·1 min·0 views

KaTeX can be used to render mathematical notation within articles.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/mermaid/index.html b/docs/tags/mermaid/index.html index 085997a1..34bbffcf 100644 --- a/docs/tags/mermaid/index.html +++ b/docs/tags/mermaid/index.html @@ -1,14 +1,21 @@ mermaid · Blowfish - + - - + + -

mermaid

2020

Shortcodes

954 words·5 mins·0 views

2019

Diagrams and Flowcharts

·250 words·2 mins·0 views
It’s easy to add diagrams and flowcharts to articles using Mermaid.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/netlify/index.html b/docs/tags/netlify/index.html index 03f1ec3e..5b9a9f13 100644 --- a/docs/tags/netlify/index.html +++ b/docs/tags/netlify/index.html @@ -1,14 +1,21 @@ netlify · Blowfish - + - - + + -

netlify

2020

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/new/index.html b/docs/tags/new/index.html index 6b5dcfea..1b27878f 100644 --- a/docs/tags/new/index.html +++ b/docs/tags/new/index.html @@ -1,14 +1,21 @@ new · Blowfish - + - - + + -

new

2022

Upgrading from Congo 1.x

1382 words·7 mins·0 views

What's New in 2.0 ✨

771 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/partials/index.html b/docs/tags/partials/index.html index e29db434..7a678b9a 100644 --- a/docs/tags/partials/index.html +++ b/docs/tags/partials/index.html @@ -1,14 +1,21 @@ partials · Blowfish - + - - + + -

partials

2020

Partials

751 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/privacy/index.html b/docs/tags/privacy/index.html index 4bd0265c..ec54e666 100644 --- a/docs/tags/privacy/index.html +++ b/docs/tags/privacy/index.html @@ -1,14 +1,21 @@ privacy · Blowfish - + - - + + -

privacy

2020

Partials

751 words·4 mins·0 views

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/render/index.html b/docs/tags/render/index.html index fb503a44..db620efc 100644 --- a/docs/tags/render/index.html +++ b/docs/tags/render/index.html @@ -1,14 +1,21 @@ render · Blowfish - + - - + + -

render

2020

Hosting & Deployment

822 words·4 mins·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/sample/index.html b/docs/tags/sample/index.html index f979673a..3512b696 100644 --- a/docs/tags/sample/index.html +++ b/docs/tags/sample/index.html @@ -1,15 +1,22 @@ sample · Blowfish - + - - + + -
Blowfish +

sample

2020

Users

122 words·0 views

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. + +
+ +

sample

2020

Users

122 words·0 views

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. Additionally, custom icons are also fully supported.

2019

Markdown

·472 words·3 mins·0 views

This article offers a sample of basic Markdown formatting that can be used in Congo, also it shows how some basic HTML elements are decorated.

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.

Mathematical notation

·145 words·1 min·0 views

KaTeX can be used to render mathematical notation within articles.

Diagrams and Flowcharts

·250 words·2 mins·0 views
It’s easy to add diagrams and flowcharts to articles using Mermaid.

Charts

·81 words·1 min·0 views
Congo includes Chart.js for powerful charts and data visualisations.

Emoji 🪂

·97 words·1 min·0 views
📖🏞️🧗🏽🐉🧙🏽‍♂️🧚🏽👸
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/shortcodes/index.html b/docs/tags/shortcodes/index.html index 34a2be46..de3e24dd 100644 --- a/docs/tags/shortcodes/index.html +++ b/docs/tags/shortcodes/index.html @@ -1,15 +1,22 @@ shortcodes · Blowfish - + - - + + -
Blowfish +

shortcodes

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. + +
+ +

shortcodes

2020

Icons

··140 words·1 min·0 views
Congo has built-in support for a number of FontAwesome 6 icons. These can be included in your website through either the icon partial or icon shortcode. Additionally, custom icons are also fully supported.

Shortcodes

954 words·5 mins·0 views

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.

Mathematical notation

·145 words·1 min·0 views

KaTeX can be used to render mathematical notation within articles.

Diagrams and Flowcharts

·250 words·2 mins·0 views
It’s easy to add diagrams and flowcharts to articles using Mermaid.

Charts

·81 words·1 min·0 views
Congo includes Chart.js for powerful charts and data visualisations.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/twitter/index.html b/docs/tags/twitter/index.html index bc158d24..f291335d 100644 --- a/docs/tags/twitter/index.html +++ b/docs/tags/twitter/index.html @@ -1,14 +1,21 @@ twitter · Blowfish - + - - + + -

twitter

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/users/index.html b/docs/tags/users/index.html index f0cef58a..7eec1683 100644 --- a/docs/tags/users/index.html +++ b/docs/tags/users/index.html @@ -1,14 +1,21 @@ users · Blowfish - + - - + + -

users

2020

Users

122 words·0 views
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/vimeo/index.html b/docs/tags/vimeo/index.html index 74724466..5a052981 100644 --- a/docs/tags/vimeo/index.html +++ b/docs/tags/vimeo/index.html @@ -1,14 +1,21 @@ vimeo · Blowfish - + - - + + -

vimeo

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/tags/youtube/index.html b/docs/tags/youtube/index.html index 342714cd..a7951ad8 100644 --- a/docs/tags/youtube/index.html +++ b/docs/tags/youtube/index.html @@ -1,14 +1,21 @@ youtube · Blowfish - + - - + + -

youtube

2019

Rich Content

·145 words·1 min·0 views
This is an example of a rich content summary.
\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/docs/users/index.html b/docs/users/index.html index 133c7b34..a56ec533 100644 --- a/docs/users/index.html +++ b/docs/users/index.html @@ -1,19 +1,26 @@ Users · Blowfish - + - - + + -
Blowfish +

Users

122 words·0 views
Real websites that are built with Congo.
WebsiteDetails
jamespanther.comPersonal site - Theme author
srisco.devPersonal site
antoinesoetewey.comPersonal site
leif.ioPersonal site and Tech blog
dr460nf1r3.orgPersonal site and Blog
OCram85.comPersonal site and Blog
mackiser.github.ioPersonal site and Blog
jamesmillner.devPersonal site and Blog
jeremic.caPersonal site and Blog
rohn.techPersonal site
klimafreundlicher-kochen.deFood blog (in German)
seyslee.github.ioTech blog (in Korean)
datanalyze.beProfessional site
sneaky-potato.github.ioProfessional site and Blog
kelset.devPersonal site
docteurelsavancaster.comProfessional site
ruihao-li.github.ioPersonal site and Blog
phalanxhead.devPersonal site and Blog
Bible Multi AppsPersonal site and Blog
Jh123xPersonal site and Blog
sforzando LLC. and Inc.Corporate site and Blog

Congo user? To add your site to this list, submit a pull request.

Users

122 words·0 views
Real websites that are built with Congo.
WebsiteDetails
jamespanther.comPersonal site - Theme author
srisco.devPersonal site
antoinesoetewey.comPersonal site
leif.ioPersonal site and Tech blog
dr460nf1r3.orgPersonal site and Blog
OCram85.comPersonal site and Blog
mackiser.github.ioPersonal site and Blog
jamesmillner.devPersonal site and Blog
jeremic.caPersonal site and Blog
rohn.techPersonal site
klimafreundlicher-kochen.deFood blog (in German)
seyslee.github.ioTech blog (in Korean)
datanalyze.beProfessional site
sneaky-potato.github.ioProfessional site and Blog
kelset.devPersonal site
docteurelsavancaster.comProfessional site
ruihao-li.github.ioPersonal site and Blog
phalanxhead.devPersonal site and Blog
Bible Multi AppsPersonal site and Blog
Jh123xPersonal site and Blog
sforzando LLC. and Inc.Corporate site and Blog

Congo user? To add your site to this list, submit a pull request.

\ No newline at end of file +Blowfish

Powered by Hugo & Blowfish

\ No newline at end of file diff --git a/exampleSite/config/_default/params.toml b/exampleSite/config/_default/params.toml index f11513df..09dfb583 100644 --- a/exampleSite/config/_default/params.toml +++ b/exampleSite/config/_default/params.toml @@ -9,7 +9,7 @@ colorScheme = "ocean" defaultAppearance = "dark" # valid options: light or dark autoSwitchAppearance = false -enableSearch = false +enableSearch = true enableCodeCopy = true mainSections = ["posts", "suggest", "external"] @@ -18,7 +18,7 @@ mainSections = ["posts", "suggest", "external"] [footer] showCopyright = true showThemeAttribution = true - showAppearanceSwitcher = false + showAppearanceSwitcher = true showScrollToTop = true [homepage] @@ -33,7 +33,7 @@ mainSections = ["posts", "suggest", "external"] showBreadcrumbs = true showDraftLabel = true showEdit = true - # editURL = "https://github.com/nunocoracao/homepage/tree/main/content" + editURL = "https://github.com/nunocoracao/blowfish/tree/dev/content" editAppendPath = true showHeadingAnchors = true showPagination = true diff --git a/exampleSite/content/.DS_Store b/exampleSite/content/.DS_Store index 8b4e2230..2eff4624 100644 Binary files a/exampleSite/content/.DS_Store and b/exampleSite/content/.DS_Store differ diff --git a/exampleSite/content/mentor/index.md b/exampleSite/content/mentor/index.md deleted file mode 100644 index 0d32818e..00000000 --- a/exampleSite/content/mentor/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: "Mentor" -date: 2022-06-19T13:08:25+01:00 -draft: true - -showDate : false -showDateUpdated : false -showHeadingAnchors : false -showPagination : false -showReadingTime : false -showTableOfContents : true -showTaxonomies : false -showWordCount : false -showSummary : false -sharingLinks : false -showEdit: false - - ---- - -Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas Lorem ipsum alkdas - - - MentorCruise \ No newline at end of file diff --git a/exampleSite/content/music/addifferentkindoftango.jpg b/exampleSite/content/music/addifferentkindoftango.jpg deleted file mode 100644 index b833bf9c..00000000 Binary files a/exampleSite/content/music/addifferentkindoftango.jpg and /dev/null differ diff --git a/exampleSite/content/music/anotherbeginning.jpg b/exampleSite/content/music/anotherbeginning.jpg deleted file mode 100644 index 2bd0515a..00000000 Binary files a/exampleSite/content/music/anotherbeginning.jpg and /dev/null differ diff --git a/exampleSite/content/music/apple.png b/exampleSite/content/music/apple.png deleted file mode 100644 index cdad1d18..00000000 Binary files a/exampleSite/content/music/apple.png and /dev/null differ diff --git a/exampleSite/content/music/bellucciscatwalk.jpg b/exampleSite/content/music/bellucciscatwalk.jpg deleted file mode 100644 index f7a7ec26..00000000 Binary files a/exampleSite/content/music/bellucciscatwalk.jpg and /dev/null differ diff --git a/exampleSite/content/music/blueingreen.jpg b/exampleSite/content/music/blueingreen.jpg deleted file mode 100644 index 042e0fc2..00000000 Binary files a/exampleSite/content/music/blueingreen.jpg and /dev/null differ diff --git a/exampleSite/content/music/burka.jpg b/exampleSite/content/music/burka.jpg deleted file mode 100644 index 05e78368..00000000 Binary files a/exampleSite/content/music/burka.jpg and /dev/null differ diff --git a/exampleSite/content/music/dreamingincolor.jpg b/exampleSite/content/music/dreamingincolor.jpg deleted file mode 100644 index 421c6b7e..00000000 Binary files a/exampleSite/content/music/dreamingincolor.jpg and /dev/null differ diff --git a/exampleSite/content/music/index.md b/exampleSite/content/music/index.md deleted file mode 100644 index 8e096c0d..00000000 --- a/exampleSite/content/music/index.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: "Music" -date: 2022-06-13T20:55:37+01:00 -draft: false - -showDate : false -showDateUpdated : false -showHeadingAnchors : false -showPagination : false -showReadingTime : false -showTableOfContents : true -showTaxonomies : false -showWordCount : false -showSummary : false -sharingLinks : false -showEdit: false - -#groupByYear : false - ---- - -I started learning music by myself at the age of 14. I play several instruments and I love to record, compose and produce my own music. I've been releasing my songs under the name "Doppler Effect" in the usual streaming services. Here are the links if you want to listen. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CoverTitleReleasedListen
Remember a New DayAugust 2022 - - - -
TeardropJuly 2022 - - - -
The Devil Dances TonightJuly 2022 - - - -
Bellucci's CatwalkJune 2022 - - - -
Another BeginningJune 2022 - - - -
Blue in GreenJune 2022 - - - -
Dreaming in ColorJanuary 2022 - - - -
Sweet JuneSeptember 2021 - - - -
Walking MilesApril 2021 - - - -
A Different Kind of TangoApril 2021 - - - -
BurkaApril 2021 - - - -
Smoking with a NinjaApril 2021 - - - -
\ No newline at end of file diff --git a/exampleSite/content/music/rememberanewday.jpg b/exampleSite/content/music/rememberanewday.jpg deleted file mode 100644 index ddbd92a5..00000000 Binary files a/exampleSite/content/music/rememberanewday.jpg and /dev/null differ diff --git a/exampleSite/content/music/smokingwithaninja.jpg b/exampleSite/content/music/smokingwithaninja.jpg deleted file mode 100644 index cff515f9..00000000 Binary files a/exampleSite/content/music/smokingwithaninja.jpg and /dev/null differ diff --git a/exampleSite/content/music/spotify.svg.png b/exampleSite/content/music/spotify.svg.png deleted file mode 100644 index b7fc7876..00000000 Binary files a/exampleSite/content/music/spotify.svg.png and /dev/null differ diff --git a/exampleSite/content/music/sweetjune.jpg b/exampleSite/content/music/sweetjune.jpg deleted file mode 100644 index 146773c5..00000000 Binary files a/exampleSite/content/music/sweetjune.jpg and /dev/null differ diff --git a/exampleSite/content/music/teardrop.jpg b/exampleSite/content/music/teardrop.jpg deleted file mode 100644 index 818f045d..00000000 Binary files a/exampleSite/content/music/teardrop.jpg and /dev/null differ diff --git a/exampleSite/content/music/thedevildancestonight.jpg b/exampleSite/content/music/thedevildancestonight.jpg deleted file mode 100644 index 2caf7b6c..00000000 Binary files a/exampleSite/content/music/thedevildancestonight.jpg and /dev/null differ diff --git a/exampleSite/content/music/walkingmiles.jpg b/exampleSite/content/music/walkingmiles.jpg deleted file mode 100644 index c71cccd1..00000000 Binary files a/exampleSite/content/music/walkingmiles.jpg and /dev/null differ diff --git a/exampleSite/content/music/youtube.png b/exampleSite/content/music/youtube.png deleted file mode 100644 index 56580049..00000000 Binary files a/exampleSite/content/music/youtube.png and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/chart.png b/exampleSite/content/posts/202109-the-future-of-nintendo/chart.png deleted file mode 100644 index af02c87c..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/chart.png and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/console.jpeg b/exampleSite/content/posts/202109-the-future-of-nintendo/console.jpeg deleted file mode 100644 index c6a01139..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/console.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/end.jpeg b/exampleSite/content/posts/202109-the-future-of-nintendo/end.jpeg deleted file mode 100644 index b9dc3865..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/end.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/feature.jpeg b/exampleSite/content/posts/202109-the-future-of-nintendo/feature.jpeg deleted file mode 100644 index aa22fab7..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/feature.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/index.md b/exampleSite/content/posts/202109-the-future-of-nintendo/index.md deleted file mode 100644 index 52ee2b8f..00000000 --- a/exampleSite/content/posts/202109-the-future-of-nintendo/index.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: "The Future of the Nintendo Switch" -description: "Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?" -summary: "Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story?" -categories: ["Strategy", "Product"] -tags: ["Strategy", "Product", "Nintendo", "Switch", "Disruption"] -#externalUrl: "" -showSummary: true -date: 2021-09-09 -draft: false ---- - - - - -Nintendo achieved something truly amazing with the launch of the Switch. It was able to disrupt itself and the entire gaming industry while saving itself from doom. How exactly was Nintendo able to do it and what comes next in that story? - -## A Little History... - - - -Nintendo is a Japanese multinational consumer electronics and video game company with headquarters in Kyoto, Japan. In its annual report for 2021, the company reported a revenue of $16 billion (¥1,759 trillion) and it currently employs around six thousand people around the world across several different business units. - -Nintendo was founded in 1889 as a company that produced and distributed hanafuda, a traditional Japanese card game. During the first half of the 1900s, the company tried to diversify into several different markets with little to no success (e.g. instant rice, love hotels, and a taxi service). During the 60s to 80s, Nintendo started investing in games, electronic toys, and gaming entertainment. - -All of these investments culminated in the 90s with the launch of the Super Nintendo Entertainment System which sold around 50 million units worldwide and helped the company enter the US market. By then Nintendo had built several valuable assets in hardware, software, and intellectual property (including the most famous plumber that ever lived, Mario). - -After the Super Nintendo, the company continued to release new games and gaming devices throughout the 90s and into the 00s, including the Gameboy, Nintendo 64, GameCube, and the Wii in 2006, which contributed to make Nintendo a force to be reckoned in the gaming industry with net sales that peaked at $18 billion in 2009. - - - -In 2010, the previous generation of hardware Wii was approaching the end of its life cycle and coincidentally the company’s annual net sales started dropping. At the end of 2012 the company launched its next-generation gaming console that would replace the Wii, the Wii U. However, the Wii U was a commercial failure and never got a real foothold in the console market selling less than 15 million units worldwide. The platform was described as expensive, confusing and was never able to attract support from either hardcore nor casual customers leading to Nintendo's sales eventually plummeting to just $4 billion in 2017. - -2017 was also the same year the company was able to disrupt itself and the entire gaming industry with the launch of the Nintendo Switch which until today sold more than 89 million units worldwide, led to a reported $16 billion net sales in 2021, and ultimately contributed to save Nintendo and establish it once again as one of the biggest players in the game industry. - -## The Switch's Disruption - - - -The Switch entered the market as the first console that was built from the ground up to provide a hybrid experience between mobile and living room gaming (or at least the first one that was actually able to deliver that experience). This hybrid setup allowed Nintendo to create different gaming modes from connecting the Switch to a TV using a dock, to connecting the controls to the main unit and taking it to play on the go. Additionally, the actual remote of the console can be used as two separate controlling devices which allows two players to enjoy a game at once. All these different modes and combinations made the switch a super attractive console for families and casual gamers since it was an affordable and flexible option when compared to the rest of the hardware available. - -A problem that Nintendo had to solve was the fact that launching a gaming console entails an interdependency between the actual hardware and its games. Or in other words, a console is only as valuable as the catalog of games available for it. To solve this problem, Nintendo adopted an integrated strategy in order to launch the Switch with a great catalog of games focusing on the same segment that the hardware features of the console were targeting. Nintendo developed several of the initial games and leveraged its valuable intellectual property of characters and stories to sell the Switch i.e. Mario, Zelda, etc. - -The Switch is a traditional example of a new-market disruption. Nintendo was targeting casual gamers (non-consumption for the traditional gaming industry) by offering a product that was inferior when compared to the other consoles in the market using the metrics from that time (graphics power, storage, etc) but superior when using the new set of metrics important to the new segment (fun, flexible, casual, affordable, etc). The fact that the Switch was not a super powerful device led to Sony and Microsoft not seeing Nintendo as a real competitor since their performance metrics were focused on high-end gamers and AAA titles. This created an asymmetric motivation, meaning that the incumbent companies simply conceded that market to Nintendo as it was not interesting for them. Ultimately, Nintendo gained market share with the Switch selling over 80 million units worldwide. At the moment other players still do not have the incentives to compete in that market and even if they did, they would not be able to because neither of them is competing on the same performance metrics as the Switch nor with the same organization and business structure that would allow them to succeed. - - - -In July 2019, Nintendo decided to launch a cheaper version of the product called the Switch Lite, this was a clear example of the company disrupting itself. Namely, Nintendo created a low-end disruption over its own product by creating a cheaper “good enough” product that targets over-served customers of the original Switch. This created a strong foothold on the low-end market for video games which is hard to compete against. - -Currently, Nintendo and the Switch are in a phase of sustaining innovation where incremental performance improvements in attributes are provided to the more valuable/demanding customers in the market. The proof of this is the next version of the console, due to launch in October 2021, the Nintendo Switch OLED, which is basically the same as the current Switch with a bigger screen, bigger battery, and more internal storage. This makes complete sense from a strategic point of view, after defining and deploying such a successful product, Nintendo is focusing on a deliberate strategy to grow its market share and meet the needs of its best customers in order to beat the competition, not that there is actually one at the time. - -## What's Next for Nintendo and the Switch? - - - -Currently, the Switch is already the 7th best selling console of all time and the 2nd best selling handheld gaming device of all time with 89 million units sold worldwide. Considering just the consoles still in the market, the Switch has already become the number 2 device in just 4 years. - - - -It is expected that, for the time being, Nintendo will retain its position in the market and keep evolving the Switch and its ecosystem with new incremental improvements. Companies like Sony and Microsoft which are targeting the high-end gamer segment will not be able to compete with Nintendo due to the humongous differences in the structures of their businesses and organization. Moreover, the other organizations also do not have any incentive to try to compete in the same market as Nintendo because, from their point of view, it is a lower margin market than the one they already have which creates an asymmetric motivation for them to flee up, conceding the low-end without fighting over it. Finally, Nintendo will have a huge advantage over new competitors that tackle its segment and it has every motivation to fight the entrance of new players into its space. - -However, there are still points that might require course correction to avoid potential future problems. The first one is the lack of traction from other game developers and publishers in respect to the Switch. Looking at the list of the top 10 best-selling games for the platform only 2 were not developed by Nintendo or one of its subsidiaries. The Switch developer experience has a low barrier to entry (each dev kit costing around $450) but there is a 30% “tax” on each game sold taken from the developers/publishers by Nintendo. The company could potentially look at their developer relationships and explore ways to improve the business model to get a bigger catalog of games faster. A couple of examples would be to help promote games via their channels, or the creation of an indie games program to help and promote smaller companies. Ultimately, this means that in order to grow Nintendo needs to move away from its integrated strategy into a specialized one where it focuses on the most important pieces of the system and in delivering it perfectly i.e. the console, the store, and its IP. But for that, it needs to ensure the right level of modularity so that other developers and publishers can thrive in that space. - -Another issue with the Switch is the lack of non-gaming applications available in the device that leads to a clash with the main Job-To-Be-Done for the product, “I want entertainment for me and my family”. The Switch has the potential to be the central hub for family entertainment, however, only three video streaming applications are available on the platform: Hulu, Youtube, and Funimation. Working with companies that provide other types of entertainment like Netflix and Disney and helping them launch those services on the Switch would be a great opportunity for Nintendo to improve the feature set of the device and better serve its users. - - - -Regarding the future, Nintendo is clearly betting on game streaming as a way to move up in the market and disrupt yet again the other players. This would be a great technology to drive the next round of low-end disruption by offering a cheaper way to play AAA games without having to own expensive hardware and upgrade it every one or two years. However, creating its own streaming service might not be the best strategy, Nintendo should look into making its system more modular and potentially partnering with other companies like Google Stadia to get access to streaming capabilities and an existing catalog of games right away. - -Ultimately, the common factor across all of Nintendo’s decisions and actions has been the ability to focus on understanding and delivering against the underlying Job-To-Be-Done for its customers. The company was able to understand that the gaming experience could solve the problem (or “job”) of family or party entertainment as well as the standard problems customers hire a gaming device to solve (i.e. play games). By organizing the entire company around these jobs, Nintendo created the ability to target non-consumption and attract a completely different segment of users to its products. Moreover, by implementing an integrated strategy that delivered new hardware, developed new games, and leveraged family-friendly characters known around the world, Nintendo was able to deliver a perfect solution for the job and completely disrupt the gaming industry. In my view, this relentless focus on the customer and how to best solve its problem is why Nintendo has become a Purpose Brand that focuses on providing great family fun and entertainment using technology. - - - -## References - -[Henderson, Rik. “What is Nintendo Switch Cloud Streaming, how does it work and what Cloud Version games are there?” Pocket-Lint](https://www.pocket-lint.com/games/news/nintendo/155391-nintendo-switch-cloud-version-streaming-explained-games-list) - -[Herold, Charles. “10 Reasons the Wii U Was a Failure.” Lifewire.](https://www.lifewire.com/reasons-the-wii-u-is-a-failure-2498588) - -[Nintendo. “Nintendo Annual Report FY 2021.”](https://www.nintendo.co.jp/ir/pdf/2021/annual2103e.pdf) - -[Orland, Kyle. “What the “OLED Model” means for the future of Nintendo Switch.” ARS Technica.](https://arstechnica.com/gaming/2021/07/what-the-oled-model-means-for-the-future-of-nintendo-switch/) - -[Peckham, Matt. “19 Things Nintendo's President Told Us About Switch and More.” Time.](https://time.com/4662446/nintendo-president-switch-interview/) - -[Statista. “Nintendo's net sales from fiscal 2008 to 2021.”](https://www.statista.com/statistics/216622/net-sales-of-nintendo-since-2008/) - -[Wikipedia. “List of best-selling game consoles.”](https://en.wikipedia.org/wiki/List_of_best-selling_game_consoles) - -[Wikipedia. “List of best-selling Nintendo Switch video games.”](https://en.wikipedia.org/wiki/List_of_best-selling_Nintendo_Switch_video_games) \ No newline at end of file diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/lite.png b/exampleSite/content/posts/202109-the-future-of-nintendo/lite.png deleted file mode 100644 index 4b2c3893..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/lite.png and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/netflix.jpeg b/exampleSite/content/posts/202109-the-future-of-nintendo/netflix.jpeg deleted file mode 100644 index 29d05cb5..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/netflix.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/netsales.png b/exampleSite/content/posts/202109-the-future-of-nintendo/netsales.png deleted file mode 100644 index 54f0c7ff..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/netsales.png and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/olde.jpeg b/exampleSite/content/posts/202109-the-future-of-nintendo/olde.jpeg deleted file mode 100644 index 07007df7..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/olde.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202109-the-future-of-nintendo/supernintendo.jpg b/exampleSite/content/posts/202109-the-future-of-nintendo/supernintendo.jpg deleted file mode 100644 index fb8b7e45..00000000 Binary files a/exampleSite/content/posts/202109-the-future-of-nintendo/supernintendo.jpg and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/Install/docker.png b/exampleSite/content/posts/202206-homepage-guide/Install/docker.png deleted file mode 100644 index 32fab03f..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/Install/docker.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/Install/remote.png b/exampleSite/content/posts/202206-homepage-guide/Install/remote.png deleted file mode 100644 index 16d1c671..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/Install/remote.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/Install/vscode.png b/exampleSite/content/posts/202206-homepage-guide/Install/vscode.png deleted file mode 100644 index 1516bf6e..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/Install/vscode.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/banner.png b/exampleSite/content/posts/202206-homepage-guide/banner.png deleted file mode 100644 index f508b0f5..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/banner.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/configure/config.png b/exampleSite/content/posts/202206-homepage-guide/configure/config.png deleted file mode 100644 index 903681e3..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/configure/config.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/configure/final.png b/exampleSite/content/posts/202206-homepage-guide/configure/final.png deleted file mode 100644 index f508b0f5..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/configure/final.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/configure/languages.png b/exampleSite/content/posts/202206-homepage-guide/configure/languages.png deleted file mode 100644 index a361ae61..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/configure/languages.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/configure/params.png b/exampleSite/content/posts/202206-homepage-guide/configure/params.png deleted file mode 100644 index e095c8cb..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/configure/params.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/configure/profile.jpg b/exampleSite/content/posts/202206-homepage-guide/configure/profile.jpg deleted file mode 100644 index 19d50c68..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/configure/profile.jpg and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/createfbproj.png b/exampleSite/content/posts/202206-homepage-guide/deploy/createfbproj.png deleted file mode 100644 index 4648d2eb..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/createfbproj.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/fbhostingep.png b/exampleSite/content/posts/202206-homepage-guide/deploy/fbhostingep.png deleted file mode 100644 index 13e36def..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/fbhostingep.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/final.png b/exampleSite/content/posts/202206-homepage-guide/deploy/final.png deleted file mode 100644 index 1582ae49..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/final.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseconfig.png b/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseconfig.png deleted file mode 100644 index d83f852d..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseconfig.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/firebasedeploy.png b/exampleSite/content/posts/202206-homepage-guide/deploy/firebasedeploy.png deleted file mode 100644 index b0117e0e..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/firebasedeploy.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/firebasehosting.png b/exampleSite/content/posts/202206-homepage-guide/deploy/firebasehosting.png deleted file mode 100644 index ed202fbb..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/firebasehosting.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaselogin.png b/exampleSite/content/posts/202206-homepage-guide/deploy/firebaselogin.png deleted file mode 100644 index ef8d8833..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaselogin.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseproj.png b/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseproj.png deleted file mode 100644 index eb59fc97..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/deploy/firebaseproj.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/devenvs/step1.png b/exampleSite/content/posts/202206-homepage-guide/devenvs/step1.png deleted file mode 100644 index f0989e93..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/devenvs/step1.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/devenvs/step2.png b/exampleSite/content/posts/202206-homepage-guide/devenvs/step2.png deleted file mode 100644 index 353eddb7..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/devenvs/step2.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/devenvs/step3.png b/exampleSite/content/posts/202206-homepage-guide/devenvs/step3.png deleted file mode 100644 index 0763b83d..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/devenvs/step3.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/devenvs/step4.png b/exampleSite/content/posts/202206-homepage-guide/devenvs/step4.png deleted file mode 100644 index 21fc00f0..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/devenvs/step4.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/devenvs/step5.png b/exampleSite/content/posts/202206-homepage-guide/devenvs/step5.png deleted file mode 100644 index 14074ad6..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/devenvs/step5.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/feature.png b/exampleSite/content/posts/202206-homepage-guide/feature.png deleted file mode 100644 index f508b0f5..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/feature.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/index.md b/exampleSite/content/posts/202206-homepage-guide/index.md deleted file mode 100644 index 665113ba..00000000 --- a/exampleSite/content/posts/202206-homepage-guide/index.md +++ /dev/null @@ -1,347 +0,0 @@ ---- -title: "How I Created My Homepage (for free) Using Docker, Hugo, and Firebase" -description: "Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results." -summary: "Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results." -categories: ["Development", "Tutorial"] -tags: ["Development", "Environment", "Tutorial", "Hugo", "Congo", "Docker", "VSCode", "Go"] -#externalUrl: "" -showSummary: true -date: 2022-06-27 -draft: false ---- - - - - -## TL;DR - -Currently, there are several solutions to build and host your personal website. I wanted to challenge myself to see if I could do it with the same set of features as some of the paid solutions out there and for free. Here are the results. - -## Why would a PM build their own homepage from scratch… - -A couple of months ago I decided that I wanted to start writing more in order to a) exercise my writing skills and b) get feedback on some of my ideas. With this goal in mind, I started researching tools/platforms that would help me publish without creating too much friction for me, or for the people wanting to read what I have to say e.g. having to pay. Ultimately I decided upon creating my own website. - -I had a couple of reasons for wanting to try this: - -- challenge me to see if I, a previous software engineering student, could still bodge something together that would work and feel good about not having forgotten everything I ever learned about programming, - -- find a flexible free solution that would allow me to kickstart my website without investing money right away into it, aka avoiding operational costs with platforms and services that would lock me in the future, - -- have my content hosted in a place that will not require people to pay for reading it, - -- play around with Docker's developer environments and Microsoft's developer containers to get myself familiar with both solutions. - -## Let’s get started… - -After some research, I decided to choose a website generator framework and a free hosting service. For the website framework, I choose Hugo with Congo as the theme, and for the hosting service Firebase. And for obvious reasons, I decided to set up my development environment using Docker in order to put myself in the user's shoes for this experiment. - -I didn't go into a deep analysis of which framework was the best for my problem as I wanted to get an MVP out fast so I went through a couple of options and picked the first one that I liked. There are several other options with different features and approaches from the one I picked. If you want to explore other options these are some you can explore: Docussaurus, Gatsby, Jekyll, Ghost, and even WordPress. The same is applicable to the hosting part, even though I chose Firebase there are other solutions like Cloudflare Pages, GitHub Pages, Digital Ocean, Netlify, Vercel, and others that you might consider exploring. If you have any suggestions for this guide feel free to reach out, always happy to chat and learn. - - -## Tools - -For this guide, I will use the following tools, which should be installed on your machine. Here is a small explanation of what each component is going to be used for and a link to the installation instructions. - -- **Docker** - I will use Docker to configure a development environment for this project so that we can skip the need to install all the software required to run Hugo and Firebase CLI i.e. cURL, Go, Hugo, Node, NPM, etc. This will allow you to start from a git repository, start the environment and go straight into writing code instead of spending hours figuring out how to install a specific compiler for your CPU architecture. Install Docker - -- **Visual Studio Code** - I'm using Visual Studio Code as my code editor at the moment, and all the material in the guide assumes that this is what you're using. If you have a different preference you’ll need to adapt some parts of this guide to achieve the same results. Install Visual Studio Code - -## Setup the Development Environment - -Let's start by configuring your development environment using Docker. This will allow you to create a container with all the tools you need inside of it without having to mess with your system configurations. Moreover, it will also make it easier to just delete the container and rebuild it whenever you need it instead of keeping old versions of software you don't require daily in your personal machine. - -{{< alert >}} -Note: If you just want to clone a repo with the final skeleton feel free to clone this repo and skip to the deploy section - - -{{}} - -I'll provide two ways of setting up your development environment feel free to choose the one you prefer or try both to explore the differences between them. Both options rely on a `Dockerfile` built by me which uses `klakegg/hugo:0.93.2-ubuntu` as the base image, even though this is not Hugo's official image (since there isn't one at the moment) it's the one recommended on their website,. - -### Using Docker - -To spin up a Dev Environment just open Docker Dashboard and select the "Dev Environments" tab on the left. If you don't have any dev environments setup select "Create New Environment" otherwise use the button on the upper right side "Create". Proceed to the setup step. - - - - -Here choose the "Existing Git repo" option and use the following GitHub URL: - -``` -https://github.com/nunocoracao/homepage-kickstart -``` - -{{< alert >}} -**Note:** If you clone the repo locally you can also start from the local folder -{{< /alert >}} - -Once the container is running you should see something similar to the images below. - - - - -In both situations, you will be able to see and click the button "Open in VSCode" which will open the editor and will allow you to start working. From there open a terminal and proceed to [create the site skeleton](#create-site-skeleton) - -### Using Visual Studio Code - -Start by cloning the GitHub repository with the development environment configurations. - -``` -git clone https://github.com/nunocoracao/homepage-kickstart -``` - -This method requires the installation of an extra VSCode extension in order to spin up the containers. Please search for **Remote - Containers** and install the extension to continue this guide. - -After successfully installing the extension, open your source folder in VSCode and open the “Remote - Containers” extension panel on the left. Select "Open Folder in Container" to spin up a container with the development environment. - - - -Wait a couple of minutes while the image is built. Docker is creating an image with all the required software for the development of the website. This will only happen the first time you spin the environment. - - - - -Once the image is built, VSCode will spin the container and will place your working environment inside of it (information available in the bottom left corner of the window). You now have a development environment with Go, Hugo, Firebase CLI, and all the tools you will need for this guide. Just open a new terminal and you’re ready to begin creating your site. - - - -### ...but I really want to run everything locally - -If you either prefer or need to run your environment locally follow the guides below to install everything you need for your setup: - -- **Homebrew** - Install homebrew -- **Hugo** - Install Hugo -- **Node.js and NPM** - Install node.js & NPM (easier to install Firebase CLI) -- **Firebase CLI** - Install Firebase CLI - -## Create Site Skeleton - -Now that we have a development environment running the first step is to create the base version of your website. For this let’s use **Hugo** to generate the folder template and configuration files we need by running the following command (`--force` parameter is required to run Hugo on a non-empty directory): - -``` -hugo new site . --force -``` -This should have created a set of folders inside your workspace that you don’t need to worry about for now. The next step is to install a theme for Hugo. I choose Congo as it had all the features I required for my website and it seemed to be easy to change if I ever need it to. If you want to try a different theme there are several available in Hugo’s documentation, each with documentation and examples. - -Install Congo using git submodules by running the following command: - -``` -git submodule add -b stable https://github.com/jpanther/congo.git themes/congo -``` - -Now we need to make some changes to the directory and file structure so that Congo can work properly. I will not get into the details of what is happening in this guide (you can consult Congo’s documentation if you want to learn more), the main takeaway is that we’re creating and configuring a folder in config/_default/ which will contain all the important configuration files for Hugo and Congo. - -Please run the following commands in order: - -``` -mkdir -p config/_default -rm config.toml -cp themes/congo/config/_default/*.toml config/_default/ -echo 'theme = "congo"' | cat - config/_default/config.toml > temp && mv temp config/_default/config.toml -``` - -Congratulations, you should have your site up and running now. Let's try it out by running Hugo's debug server: - -``` -hugo server -D -``` - -Please open your favorite browser and navigate to localhost:1313 to see your page. - - - -You should see something similar to the image above. Doesn’t look that exciting, does it? Let’s configure the theme in the next sections and learn how to create your first article. - - -## Configure Theme - -Now I’ll be covering how to change the look and feel of your website, add some personal information, and activate the dark mode toggle (aka the most important feature in any website these days). - -{{< alert >}} -A note, I am covering a very simple configuration for this theme please check Congo’s theme documentation to understand everything you can do with this theme. -{{< /alert >}} - -### Profile picture - -Let’s start by adding a profile picture to your site. Create a folder called “assets” at the root of your project. Choose a profile picture and place it inside the assets folder. The rest of the guide will assume the final picture is named "profile.jpg", so please rename your picture or take that into account when configuring some of the other files. - -
- -
If you still need to take a proper awesome picture for this feel free to download this one to proceed with the tutorial.
-
- - - -### Configuration Files - -Let’s open a couple of configuration files and start updating them. All the files we are going to change are inside config/_default/ folder. - -#### config.toml - -Uncomment the baseURL parameter and replace it with the final domain of your website. This value will be used to create the robots.txt file for any search engines to successfully crawl and index your website. - - - -{{< alert >}} -Note: if you want to configure Google Analytics please add the following line with your id to this file `googleAnalytics = "G-XXXXXX"` - -{{}} - -#### languages.en.toml - -This file will drive the main information for the website and the author of the page (you). Replace the title and description for the ones you want for your page, these values will drive the HTML title and description tags. - -Within the [author] block you can update the details that you wish to highlight in your profile. The bare minimum would be name, image, headline, and links. For the links parameter don't forget to uncomment the last line of the file as this is a json array. Update each entry with your personal links. - - - -#### params.toml - -This file defines much of the overall behavior across the entire framework. For this tutorial I changed some of the overall values and one for the homepage, if you want to learn more about the other available configurations please consult Congo’s theme documentation. - -I've changed colorScheme to "ocean" which changes the global UI theme. Congo defines a three-color palette that is used throughout the theme. Valid values are congo (default), avocado, ocean, fire, and slate. Although these are the default schemes, you can also create your own. Refer to the theme's main documentation to learn how. - -Activated showAppearanceSwitcher to enable the light/dark mode toggle. Activated enableSearch which indexes all future posts each time you build the site and provides a simple search feature. I've also changed the value of layout, inside [homepage], to "profile" which changes the way the landing page is rendered. Finally, the last interesting value here is showRecent, which when turned on shows the recent posts on the homepage. - - - -### Final - -Let’s see how it looks, run the Hugo again: - -``` -hugo server -D -``` - -And navigate to localhost:1313 you should see something similar to the page below. - - - -Congrats it’s looking great, let’s learn how to generate your first articles. - -## How to generate articles - -Hugo provides some tools to generate your articles (markdown files) with a base set of tags already in them. Run the following command to create your first post - -``` -hugo new posts/my-first-post.md -``` - -replace the contents of the file with the following: - -``` ---- -title: "My Published Post" -date: 2022-06-19T20:10:29Z -draft: false -categories: ["published", "test"] -tags: ["first", "awesome"] ---- - -This is my first blog post -``` - -This just created your first blog post. We've added a couple of categories and tags, which will be indexed by Hugo during build time. These tags will be used to create the Categories and Tags section of the website automatically for you. Notice that I've changed the draft to false to simulate a published post. - -Run the following command to create your second post - -``` -hugo new posts/my-draft-post.md -``` -and replace the contents of that file with the following: - -```markdown ---- -title: "My Draft Post" -date: 2022-06-19T20:20:39Z -draft: true -categories: ["draft", "test"] -tags: ["second", "awesome"] ---- - -This is my second blog post -``` -For the second post, I've left the draft parameter true to simulate a draft post. - -Hugo automatically hides draft posts from the final site generation. You can keep working on articles leaving the draft label true and they will be ignored by the engine. If you want to run in DEBUG mode just use the command: - -``` -hugo server -D -``` - -If you go to the posts on the site you should be able to see both entries. If you then run the server in normal mode the draft articles will disappear. You can use the command below to do so: - - -``` -hugo server -``` - -You can use this command to test the final version of the website or an article before generating the final build. When you're ready just use the command 'Hugo' to generate the final website inside the /public folder. - -``` -hugo -``` - -All files are written in Markdown which Hugo then uses to generate the final pages. I'll not teach you how to write markdown files in this guide but I can recommend this "getting started" tutorial and this "cheat sheet" to get you started. - -## Deploy - -Ok, you’ve configured your website and created a couple of articles, but we still need to deploy it somewhere. As I mentioned before I chose Firebase for this guide, even though I know that it offers much more than just a simple hosting service it allows me to host my site for free without much of a hassle. - -### Create Firebase Project - -Let’s start by going to https://firebase.google.com and creating an account. Once that is done you can create a project for free. The process should be straightforward and when you finish you should be in Firebase's project dashboard. - -### Setup Firebase - -Now you can go back to your environment which already has Firebase CLI tools installed and ready to go. Let’s start by authenticating using: - -``` -firebase login -``` -Once you are successfully logged in you need to initiate the project configurations for firebase. For that please use: - -``` -firebase init -``` - -The tool will offer you a wide variety of different options in order to configure your Firebase project. For now, we just want to configure hosting. If you are using GitHub, you might want to consider configuring GitHub action deploys which can automatically build and deploy your site every time there is a push to a specific branch or a merged pull request. - - - -Choose the Firebase project created before as the hosting destination. And select the configurations you wish for the deployment process. The important one here is the folder where the final files to the server will be placed and this is the public folder. For the other parameters you experiment with what better matches your use-case, the image below shows you what I picked (*Note: for this tutorial I didn't configure GitHub actions but I am using that in my real setup*). - - - -### Deploy - -Ok, now for the long and boring process of deployment… joking! Once you are ready and have all your files generated by the hugo command in the public folder just use the following command to deploy: - -``` -firebase deploy -``` - - - -The process should take a couple of seconds and there you go your site is deployed. The final line of the CLI tool will give you a URL to see for yourself, otherwise, you can explore your Firebase dashboard hosting section which will have more information regarding the deployment. - - - -## Conclusion - -By now you should have a simple version of your website which you can configure to your needs. The main advantage of this solution is that it is flexible and extensible to a variety of different needs especially if you take the time to explore Hugo's theme catalog. True that it might require some coding to implement complex but I would guess that this solves the problem for almost everyone. - -Above all, it’s a completely free solution if you're looking to start and can't (or don't want to) spend money. Hope this guide helps you, feel free to share it with your network and give me feedback so that I can make it better over time. - -## Resources - -- GitHub Repo for development environment -- GitHub Repo for base Hugo and Congo configuration -- GitHub Repo for base image -- Docker Hub image URL -- Hugo\'s Documentation -- Congo\'s Documentation -- Firebase Documentation -- Markdown Guide -- Markdown Getting Started" -- Markdown Cheat Sheet \ No newline at end of file diff --git a/exampleSite/content/posts/202206-homepage-guide/setup/extension.png b/exampleSite/content/posts/202206-homepage-guide/setup/extension.png deleted file mode 100644 index c9af7e11..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/setup/extension.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/setup/folder.png b/exampleSite/content/posts/202206-homepage-guide/setup/folder.png deleted file mode 100644 index 3363b324..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/setup/folder.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/setup/imagebuild.png b/exampleSite/content/posts/202206-homepage-guide/setup/imagebuild.png deleted file mode 100644 index d8e2daa0..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/setup/imagebuild.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/setup/newterminal.png b/exampleSite/content/posts/202206-homepage-guide/setup/newterminal.png deleted file mode 100644 index 272a68ba..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/setup/newterminal.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/setup/selectfolder.png b/exampleSite/content/posts/202206-homepage-guide/setup/selectfolder.png deleted file mode 100644 index 93264768..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/setup/selectfolder.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-homepage-guide/theme/vanilla.png b/exampleSite/content/posts/202206-homepage-guide/theme/vanilla.png deleted file mode 100644 index 1963ed59..00000000 Binary files a/exampleSite/content/posts/202206-homepage-guide/theme/vanilla.png and /dev/null differ diff --git a/exampleSite/content/posts/202206-mentorcruise-interview copy/index.md b/exampleSite/content/posts/202206-mentorcruise-interview copy/index.md deleted file mode 100644 index b7bb5975..00000000 --- a/exampleSite/content/posts/202206-mentorcruise-interview copy/index.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: "Nuno Coração – Meet the Mentor" -description: "Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker." -summary: "Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker." -categories: ["Product", "Mentorship", "Interview"] -tags: ["Product", "Mentorship", "Interview", "Mentorcruise"] -externalUrl: "https://mentorcruise.com/blog/nuno-coracao-meet-the-mentor-01006/" -showSummary: true -date: 2022-06-26 -draft: false -showReadingTime: false ---- - -{{< alert >}} -This article was originally published externally, read the original here. -{{}} - - -I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. - -# Why did you decide to become a mentor? -Throughout my career, I was fortunate enough to find (or be found by) amazing mentors that helped me in several different ways. Some provided advice for professional decisions and career management, others access to opportunities, and some just took me along for the ride to “watch & learn”. All of those contributed so much to make me a better professional and gave me some really interesting opportunities in my career. In the last few years, I started being a mentor myself and I am really enjoying the experience of helping others grow and fulfill their career dreams. - -# What benefits did you gain from working with mentors early on? -The main benefit was the ability to tap into someone else’s experience and seniority and learn from their past experiences. It allowed me to get a glimpse of the future and accelerate some career milestones I wanted for myself. As an example, I never had the dream of working or living abroad, but after talking about it with my mentors (that had that experience) I learned so much about what it could bring me professionally and personally that when that opportunity came I was better prepared to make the right decision. Overall, it gave me the chance to learn how to become a better professional by watching how my mentors did it on a professional setting. Moreover, it gave me the chance to manage my career by tapping into their advice and experience in order to achieve my goals. - -# How did you get your career start? -My career started as a trainee in a telco company here in Portugal. I just left university and a junior researcher position to become a solutions architect for the TV department. It was amazing to get the first job with such responsibility and exposure to the entire organization. However, I have to say that the best part of that role was my manager who made an extra effort to coach and teach me so many invaluable lessons that I do still remember after so many years. - -> Good advice is not “one-size-fits-all” - -# How do you usually set up mentorships? -I usually like to understand what are the person’s goals for the mentorship and depending on those design a specific plan. Independently of the goal, I aim to have a weekly 1:1 with each mentee to catch up on progress and see if there is anything that I can do to help with. I also like to have a log file in docs to track questions/actions/open points. What we do within this framework highly depends on the goals themselves. For example, if the mentee is looking for help in switching into a product role, I might help review the CV and LinkedIn profile and prepare them for interviews with material and mock sessions. - -# What benefit can you provide to mentees over self-studying? -As with my own personal experience, the best benefit I can provide my mentees is to allow them to tap into my experiences, and the rational behind them, so that they can learn from it. I don’t mean to say they should do exactly as I did, no advice comes in a “one-size-fits-all” package. Moreover, I definitely made some mistakes along the way. But with that insight, each person can decide what resonates with them and what doesn’t in order to make their own decisions. In summary, I’m here to help with product topics and career management, specially people that want to get into product and don’t know where to start. - -# What’s been your favourite mentorship story so far? -In one of my previous role I was managing two young professionals that joined the product team as QA Engineers. Both of them wanted to become Product Managers and were looking for ways to make that move happen. During one year I made an extra effort to share my experiences, give advice, and try to get them as many opportunities to have a “taste” of what PM is by getting them into meetings and brainstormings with my dev teams, shadow customer calls, attend meetings with management, etc. I was really happy the day I was able to sponsor both of them into their first PM roles still within the company. Since then it has been even more fulfilling to watch them grow and have their own successful careers in Product. - -# What are you getting out of being a mentor? -From my experience, having access to mentors, allowed me to grow and improve at a professional and personal level faster than by myself. At this stage in my life, I feel like I’ve experienced enough to have something valuable to share with others and maybe help them achieve their goals. Ultimately, that is what I am aiming to get out of this experience, to be able to have the same impact as a mentor as my mentors had on me. \ No newline at end of file diff --git a/exampleSite/content/posts/202206-mentorcruise-interview/featured.jpeg b/exampleSite/content/posts/202206-mentorcruise-interview/featured.jpeg deleted file mode 100644 index d2a949da..00000000 Binary files a/exampleSite/content/posts/202206-mentorcruise-interview/featured.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202206-mentorcruise-interview/index.md b/exampleSite/content/posts/202206-mentorcruise-interview/index.md deleted file mode 100644 index b7bb5975..00000000 --- a/exampleSite/content/posts/202206-mentorcruise-interview/index.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: "Nuno Coração – Meet the Mentor" -description: "Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker." -summary: "Nuno Coração is one of our professional mentors on MentorCruise and works as Staff Product Manager at Docker." -categories: ["Product", "Mentorship", "Interview"] -tags: ["Product", "Mentorship", "Interview", "Mentorcruise"] -externalUrl: "https://mentorcruise.com/blog/nuno-coracao-meet-the-mentor-01006/" -showSummary: true -date: 2022-06-26 -draft: false -showReadingTime: false ---- - -{{< alert >}} -This article was originally published externally, read the original here. -{{}} - - -I’ve been building and shipping products across multiple roles and industries, from video streaming applications to API platforms. - -# Why did you decide to become a mentor? -Throughout my career, I was fortunate enough to find (or be found by) amazing mentors that helped me in several different ways. Some provided advice for professional decisions and career management, others access to opportunities, and some just took me along for the ride to “watch & learn”. All of those contributed so much to make me a better professional and gave me some really interesting opportunities in my career. In the last few years, I started being a mentor myself and I am really enjoying the experience of helping others grow and fulfill their career dreams. - -# What benefits did you gain from working with mentors early on? -The main benefit was the ability to tap into someone else’s experience and seniority and learn from their past experiences. It allowed me to get a glimpse of the future and accelerate some career milestones I wanted for myself. As an example, I never had the dream of working or living abroad, but after talking about it with my mentors (that had that experience) I learned so much about what it could bring me professionally and personally that when that opportunity came I was better prepared to make the right decision. Overall, it gave me the chance to learn how to become a better professional by watching how my mentors did it on a professional setting. Moreover, it gave me the chance to manage my career by tapping into their advice and experience in order to achieve my goals. - -# How did you get your career start? -My career started as a trainee in a telco company here in Portugal. I just left university and a junior researcher position to become a solutions architect for the TV department. It was amazing to get the first job with such responsibility and exposure to the entire organization. However, I have to say that the best part of that role was my manager who made an extra effort to coach and teach me so many invaluable lessons that I do still remember after so many years. - -> Good advice is not “one-size-fits-all” - -# How do you usually set up mentorships? -I usually like to understand what are the person’s goals for the mentorship and depending on those design a specific plan. Independently of the goal, I aim to have a weekly 1:1 with each mentee to catch up on progress and see if there is anything that I can do to help with. I also like to have a log file in docs to track questions/actions/open points. What we do within this framework highly depends on the goals themselves. For example, if the mentee is looking for help in switching into a product role, I might help review the CV and LinkedIn profile and prepare them for interviews with material and mock sessions. - -# What benefit can you provide to mentees over self-studying? -As with my own personal experience, the best benefit I can provide my mentees is to allow them to tap into my experiences, and the rational behind them, so that they can learn from it. I don’t mean to say they should do exactly as I did, no advice comes in a “one-size-fits-all” package. Moreover, I definitely made some mistakes along the way. But with that insight, each person can decide what resonates with them and what doesn’t in order to make their own decisions. In summary, I’m here to help with product topics and career management, specially people that want to get into product and don’t know where to start. - -# What’s been your favourite mentorship story so far? -In one of my previous role I was managing two young professionals that joined the product team as QA Engineers. Both of them wanted to become Product Managers and were looking for ways to make that move happen. During one year I made an extra effort to share my experiences, give advice, and try to get them as many opportunities to have a “taste” of what PM is by getting them into meetings and brainstormings with my dev teams, shadow customer calls, attend meetings with management, etc. I was really happy the day I was able to sponsor both of them into their first PM roles still within the company. Since then it has been even more fulfilling to watch them grow and have their own successful careers in Product. - -# What are you getting out of being a mentor? -From my experience, having access to mentors, allowed me to grow and improve at a professional and personal level faster than by myself. At this stage in my life, I feel like I’ve experienced enough to have something valuable to share with others and maybe help them achieve their goals. Ultimately, that is what I am aiming to get out of this experience, to be able to have the same impact as a mentor as my mentors had on me. \ No newline at end of file diff --git a/exampleSite/content/posts/202207-docker-bulk-add/Old.jpeg b/exampleSite/content/posts/202207-docker-bulk-add/Old.jpeg deleted file mode 100644 index cd52db83..00000000 Binary files a/exampleSite/content/posts/202207-docker-bulk-add/Old.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202207-docker-bulk-add/featured.jpeg b/exampleSite/content/posts/202207-docker-bulk-add/featured.jpeg deleted file mode 100644 index 36d407e7..00000000 Binary files a/exampleSite/content/posts/202207-docker-bulk-add/featured.jpeg and /dev/null differ diff --git a/exampleSite/content/posts/202207-docker-bulk-add/image1.webp b/exampleSite/content/posts/202207-docker-bulk-add/image1.webp deleted file mode 100644 index 885de5c7..00000000 Binary files a/exampleSite/content/posts/202207-docker-bulk-add/image1.webp and /dev/null differ diff --git a/exampleSite/content/posts/202207-docker-bulk-add/image2.png.webp b/exampleSite/content/posts/202207-docker-bulk-add/image2.png.webp deleted file mode 100644 index 9bc587ac..00000000 Binary files a/exampleSite/content/posts/202207-docker-bulk-add/image2.png.webp and /dev/null differ diff --git a/exampleSite/content/posts/202207-docker-bulk-add/index.md b/exampleSite/content/posts/202207-docker-bulk-add/index.md deleted file mode 100644 index c9f5a795..00000000 --- a/exampleSite/content/posts/202207-docker-bulk-add/index.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Bulk User Add for Docker Business and Teams" -description: "Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!" -summary: "Forget manually inviting team members to Docker Desktop. With Bulk Add for Docker Business, invite your entire team with a CSV file or their Docker IDs!" -categories: ["Product", "Docker"] -tags: ["Product", "Docker", "Feature", "Docker Hub"] -externalUrl: "https://www.docker.com/blog/bulk-user-add-for-docker-business-and-teams/" -showSummary: true -date: 2022-07-27 -draft: false -showReadingTime: false ---- - -{{< alert >}} -This article was originally published externally, read the original here. -{{}} - -Docker’s goal is to create a world-class product experience for our customers. We want to build a robust product that will help all teams achieve their goals. In line with that, we’ve tried to simplify the process of onboarding your team into the Docker ecosystem with our Bulk User Add feature for Docker Business and Docker Team subscriptions. - -You can invite your team to their accounts by uploading a file including their email addresses to Docker Hub. The CSV file can either be a file you create for this specific purpose, or one that’s extracted from another in-house system. The sole requirement is that the file contains a column with the email addresses of the users that will be invited into Docker. Once the CSV file is uploaded using Docker Hub, each team member in the file will receive an invitation to use their account. - - - -We’ve also updated Docker Hub’s web interface to add multiple members at once. We hope this is useful for smaller teams that can just copy and paste a list of emails directly in the web interface and onboard everyone they need. Once your team is invited, you can see both the pending and accepted invites through Docker Hub. - - - -Bulk User Add can be used without needing to have SSO setup for your organization. This feature allows you to get the most out of your Docker Team or Business subscription, and it greatly simplifies the onboarding process. - -Learn more about the feature on our docs page, and sign in to your Docker Hub account to try it for yourself. - -And if you have any questions or would like to discuss this feature, please attend our upcoming \ No newline at end of file diff --git a/exampleSite/content/posts/202209-streaming-wars/feature.jpg b/exampleSite/content/posts/202209-streaming-wars/feature.jpg deleted file mode 100644 index ea021bbc..00000000 Binary files a/exampleSite/content/posts/202209-streaming-wars/feature.jpg and /dev/null differ diff --git a/exampleSite/content/posts/202209-streaming-wars/index.md b/exampleSite/content/posts/202209-streaming-wars/index.md deleted file mode 100644 index 038f4ca0..00000000 --- a/exampleSite/content/posts/202209-streaming-wars/index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: "Streaming Wars and What Comes After… " -description: "Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?" -summary: "Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches. What will happen next?" -categories: ["Product","Strategy",] -tags: ["Streaming","Wars","Product","Strategy","Netflix","Disney","Amazon","Apple","Prediction"] -#externalUrl: "" -showSummary: true -date: 2022-09-04 -draft: false ---- - - - -Last July and for the first time ever, streaming viewership surpassed cable. The streaming wars began around 2010 when Netflix introduced their first streaming-only plan with no DVD rentals, other players (cough, cough… Blockbuster) laughed at the time… little did they know. A decade after, there’s a multitude of streaming services available for mainstream entertainment and also for specific niches (e.g., Curiosity Stream - documentaries, Crunchyroll - anime, etc.). - - -## How Did We Get Here? -This question could turn into its series of posts, aka a very long and boring answer. The short version, Netflix hit gold when they launched their streaming-only subscription service that allowed customers to watch what they wanted when they wanted. This was a massive shift from the linear TV experience where you either had to wait in front of the TV to watch your favorite show, record and watch it later, or wait for a rerun (_fun fact: there was another option to set a reminder to watch your shows :D_). Not only did Netflix launch a way better product to **consume** content, but it also changed the way users **discovered** new series and movies by recommending new shows based on previous history. Users flocked to this service, which was significantly better than the alternatives and also cheaper than the average cable subscription at the time (i.e., _cutting the chord_). - - - - -After Netflix showed everyone how people really wanted to consume content, several players were interested in replicating that model themselves. Traditional content producers (e.g., HBO, Disney, etc.) saw a way to control their distribution channel and get a direct relationship with their customers. Other players, like Apple and Amazon, saw a good opportunity to expand their _service subscription_ strategy by offering yet-another-service to their user-base. This year, most of these services reached hundreds of millions of paying users, and the competition in this industry was never been this strong. - -## Massive Investment in Content - -
- -One of the strong signals of this competition is the huge amounts of money being spent in content production. HBO just released _House of the Dragon_, a prequel to their hit series _Game of Thrones_. The first season had an estimated production cost of just under $20 million per episode, making the 10 episode run cost a full $200 million. In comparison, _Game of Thrones_ cost around $100 million per season, with the average cost per episode starting around $6 million in season 1 and going up to $15 million in the final season. This means HBO just invested roughly double what it did in the last season of _Game of Thrones_. - -Amazon, coincidentally, also decided to launch its _prequel_ of a super-loved property in the fantasy drama space, _Lord of the Rings_. Investment in the new series, called _Lord of the Rings: The Rings of Power_, is estimated to be around $1 billion. Amazon bought the franchise rights to _Lord of the Rings_ for $250 million and invested $465 million to produce the eight-episode first season of the show. In comparison, the entire trilogy of the _Lord of the Rings_ was produced for roughly $300 million, $100 million for each movie. - -Netflix has been increasing its costs with content production in the last years, arriving at $17 billion this year. Disney is set to spend even more than that, $32 billion (even after cuts). In a different space, big tech companies are also getting into _live sports_. All of this spending creates a super competitive environment across all services, which is not necessarily in the best interest of the viewers. - -## Quality is Decreasing - -
- -One could argue that all the investment and all the money being thrown at content production will bring the golden age of entertainment. However, as most big investments, they are made to make someone money. In the entertainment industry, one of the ways to reduce risk is to invest in properties that have already proven their value in opposition to new Intellectual Property (IP). - -The levels of “content pumping” that we are seeing nowadays lead to a massive decrease in quality, and worse, viewer fatigue. Especially since it is focused on a minimal set of genres (i.e., fantasy, hero movies, etc.) and franchises (i.e., Marvel Cinematic Universe, DC Cinematic Universe, Star Wars, Fast and the Furious, etc.) - -## More Money In… More Money Out -When a company increases costs, usually the aim is to increase revenue and profit. Streaming services charge a fixed fee per month. Therefore, it doesn’t really matter how much or how little you loved the next big _fantasy drama_ series from your favorite streaming provider – they will make the same amount of money from you. - -Unless… streaming companies increase subscription prices and find new ways to monetize content. Aided by the excuse of inflation, most services have increased their prices in the last year. Specifically, Disney+ subscription in the U.S. will rise from $7.99 to $10.99, while Hulu's ad-free offering will jump from $12.99 per month to $14.99 per month. Netflix cheapest plan increased to $9.99, with the top one at $20.00. Additionally, executives from most of these big companies are also planning to roll out ads for their services. Yes, even Netflix that resisted for years - cannot keep ignoring that option when faced with competition. - -Ultimately, this is a worse product for the user. Price increases could make the overall cost of streaming services too high for some users, which will force a choice of which services to keep. Furthermore, you will get ads again, or you can pay more if you would rather not see them. - -## What Happens Next? -The high levels of competition have begun to generate frustration among users. Users are starting to get _fatigued_ with the low-quality and constant recycling of content (I swear, I am uncertain whether I can handle yet another Marvel Movie or Star Wars trilogy). The increase in prices, especially in the current economic situation, will force users to choose which services to pay for, if any. And ultimately, competition for user’s attention has never been so high. Social networks like Twitter, Instagram, and TikTok take hours of engagement daily out of each user. Video game investment has never been so high, with so many options of games and consoles. - -In my opinion, the streaming wars have already peaked, and we’ll see a change in the upcoming years before getting to a new equilibrium. I think that one out of three things will happen: - -- **Horizontal Expansion** - current streaming services would need to expand to provide additional services and bundle them together. This would increase the _value for money_ and could be interesting to some users depending on what is being bundled. Netflix has begun doing this with games. Companies like Amazon and Apple came into streaming exactly for this reason, expanding into streaming even if it was not their core business. -- **Aggregation** - One service to rule them all… If one of the existing services, or a new player, can aggregate content from several players at a lower price point, this could create a captivating value proposition for customers on the lower end. This option seems highly unlikely, this was Netflix play years ago, and it didn’t work, potentially because they were greedy. Nevertheless, in the current scenario, it is highly unlikely that big players would share rights with another VS getting exclusivity on those. -- **Merges and Acquisitions** - Big fish eats smaller fish. This is bound to happen at some point, it’s just a matter of time and which company will acquire which company for what amount of money. It’s not clear if this will be good or bad for customers, depending on who starts playing together. - -My prediction is that ultimately, big tech companies like Amazon or Apple will begin acquiring other smaller players. These companies come into streaming as a horizontal expansion from their core businesses. Both are armed with an order of magnitude more revenues than their _content only_ counterparts. As an example, in 2021 Disney’s revenue was $81.10 billion and Netflix's was $24.9 billion. In comparison, Apple’s revenue in the same year was $378.32 billion and Amazon’s was $468.82 billion. With this kind of “war chest” plus their own core business (Apple devices, and Amazon e-commerce business) it will be way easier for these companies to step in when they want to. diff --git a/exampleSite/content/posts/202209-streaming-wars/pexels-amateur-hub-3571503.jpg b/exampleSite/content/posts/202209-streaming-wars/pexels-amateur-hub-3571503.jpg deleted file mode 100644 index e35ef492..00000000 Binary files a/exampleSite/content/posts/202209-streaming-wars/pexels-amateur-hub-3571503.jpg and /dev/null differ diff --git a/exampleSite/content/posts/202209-streaming-wars/players.png b/exampleSite/content/posts/202209-streaming-wars/players.png deleted file mode 100644 index 0d804b4c..00000000 Binary files a/exampleSite/content/posts/202209-streaming-wars/players.png and /dev/null differ diff --git a/exampleSite/content/recommendations/index.md b/exampleSite/content/recommendations/index.md deleted file mode 100644 index 62068030..00000000 --- a/exampleSite/content/recommendations/index.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: "Recommendations" -date: 2022-06-19T13:03:09+01:00 -draft: true - -showDate : false -showDateUpdated : false -showHeadingAnchors : true -showPagination : false -showReadingTime : false -showTableOfContents : true -showTaxonomies : false -showWordCount : false -showSummary : false -sharingLinks : false -showEdit: false - - ---- - -## Books - -### Design of Everyday Things -asdasd - -### Design of Everyday Things -asdasd - -### Design of Everyday Things -asdasd - -### Zero to One -asdasd - -### Lean Startup -asdasd - -### Zero to One -asdasd - - -## Articles -### blabla -asdasd - -## Online Publications - -### Stratechery -asdasd - -### HBR -asdasd - - -## Podcasts - -### bla bal diff --git a/exampleSite/content/resume/aws.png b/exampleSite/content/resume/aws.png deleted file mode 100644 index aa4d5332..00000000 Binary files a/exampleSite/content/resume/aws.png and /dev/null differ diff --git a/exampleSite/content/resume/docker.png b/exampleSite/content/resume/docker.png deleted file mode 100644 index 31491db6..00000000 Binary files a/exampleSite/content/resume/docker.png and /dev/null differ diff --git a/exampleSite/content/resume/hbs.svg b/exampleSite/content/resume/hbs.svg deleted file mode 100644 index 32ebb348..00000000 --- a/exampleSite/content/resume/hbs.svg +++ /dev/null @@ -1,265 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/exampleSite/content/resume/index.md b/exampleSite/content/resume/index.md deleted file mode 100644 index bca375db..00000000 --- a/exampleSite/content/resume/index.md +++ /dev/null @@ -1,147 +0,0 @@ ---- -title: "Resume" -date: 2022-06-13T21:28:51+01:00 -draft: false - -showDate : false -showDateUpdated : false -showHeadingAnchors : false -showPagination : false -showReadingTime : false -showTableOfContents : true -showTaxonomies : false -showWordCount : false -showSummary : false -sharingLinks : false -showEdit: false - - ---- - -## Experience - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CompanyLinkRoleDatesLocation
DockerStaff Product Manager2022 - PresentFull Remote
Lisbon, PT
AWS Startup LoftStartup Advisor2022 - PresentFull Remote
Lisbon, PT
TruphoneGroup Product Manager2021 - 2022Hybrid
Lisbon, PT
Senior Product Manager2020 - 2021
Vodafone GroupAnalytics Squad Lead 2019 - 2020Lisbon, PT
London, UK
Senior Product Manager2018 - 2019
Sky DeutschlandSenior Product Architect2016 - 2018Munich, DE
Skimic Founder2016 - 2017Munich, DE
Vodafone GroupProduct Manager2015 - 2016Lisbon, PT
London, UK
NOSProduct Manager2014 - 2015Lisbon, PT
Solutions Architect2012 - 2014
Inesc-IDJunior Researcher2011 - 2012Lisbon, PT
- ---- - -## Education - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SchoolLinkDegreeDate
Harvard Business School OnlineEntrepreneurship Essentials2022
Disruptive Strategy2022
Tecnico LisboaMSc in Computer Science - Distributed Systems2012
BSc, Computer Science2010
\ No newline at end of file diff --git a/exampleSite/content/resume/inesc.png b/exampleSite/content/resume/inesc.png deleted file mode 100644 index 3172d44f..00000000 Binary files a/exampleSite/content/resume/inesc.png and /dev/null differ diff --git a/exampleSite/content/resume/ist.png b/exampleSite/content/resume/ist.png deleted file mode 100644 index 17607fc3..00000000 Binary files a/exampleSite/content/resume/ist.png and /dev/null differ diff --git a/exampleSite/content/resume/nos.png b/exampleSite/content/resume/nos.png deleted file mode 100644 index 6f1c73c0..00000000 Binary files a/exampleSite/content/resume/nos.png and /dev/null differ diff --git a/exampleSite/content/resume/skimic.png b/exampleSite/content/resume/skimic.png deleted file mode 100644 index 871c14e0..00000000 Binary files a/exampleSite/content/resume/skimic.png and /dev/null differ diff --git a/exampleSite/content/resume/sky.png b/exampleSite/content/resume/sky.png deleted file mode 100644 index 98651dd9..00000000 Binary files a/exampleSite/content/resume/sky.png and /dev/null differ diff --git a/exampleSite/content/resume/truphone.png b/exampleSite/content/resume/truphone.png deleted file mode 100644 index 2f946ced..00000000 Binary files a/exampleSite/content/resume/truphone.png and /dev/null differ diff --git a/exampleSite/content/resume/vodafone.png b/exampleSite/content/resume/vodafone.png deleted file mode 100644 index 6bd886f4..00000000 Binary files a/exampleSite/content/resume/vodafone.png and /dev/null differ