\ No newline at end of file
diff --git a/content/about/index.zh-cn.md b/content/about/index.zh-cn.md
new file mode 100755
index 0000000..e018766
--- /dev/null
+++ b/content/about/index.zh-cn.md
@@ -0,0 +1,122 @@
+---
+title: "关于"
+date: 2024-09-25T01:05:34+08:00
+draft: false
+description: All about the nerd from China that really geeks out to computers and full-stack development
+showEdit: false
+---
+
+我总是尽力挤出时间工作和学习新技能。不过我的大多数*小项目*最终都没产生什么影响。然而，它们确实让我学到了不少，帮我在现实世界得到了更多机会。
+
+---
+
+## 项目经历
+
+
\ No newline at end of file
diff --git a/content/about/owl.png b/content/about/owl.png
new file mode 100755
index 0000000..9307796
Binary files /dev/null and b/content/about/owl.png differ
diff --git a/content/goods/_index.en.md b/content/goods/_index.en.md
new file mode 100755
index 0000000..72dd424
--- /dev/null
+++ b/content/goods/_index.en.md
@@ -0,0 +1,18 @@
+---
+title: "Goods"
+layout: "goods"
+layoutBackgroundHeaderSpace: false
+sharingLinks: false
+showAuthor: false
+showComments: false
+showDate: false
+showEdit: false
+showPagination: false
+showReadingTime: false
+showRelatedContent: false
+showTableOfContents: false
+showWordCount: false
+showZenMode: false
+---
+
+The various products that have left a deep impression on me through personal experience, some of which are still in use, while others may have already **met their end**, or have been **resold**, or have been discontinued for various reasons, but all of them are recorded here (in reverse order of acquisition), as a **cybernetic memorial hall** 😄.
\ No newline at end of file
diff --git a/content/goods/_index.zh-cn.md b/content/goods/_index.zh-cn.md
new file mode 100755
index 0000000..4a48a47
--- /dev/null
+++ b/content/goods/_index.zh-cn.md
@@ -0,0 +1,18 @@
+---
+title: "好物分享"
+layout: "goods"
+layoutBackgroundHeaderSpace: false
+showDate: false
+showAuthor: false
+showEdit: false
+showPagination: false
+showReadingTime: false
+showRelatedContent: false
+showWordCount: false
+showComments: false
+sharingLinks: false
+showZenMode: false
+showTableOfContents: false
+---
+
+亲身体验过的各类让我印象深刻的产品，有的产品还在使用，另一些可能已经**寿终正寝**，异或是**转手卖出**，也可能出于各种原因没有继续使用，但全部记录在此（按入手时间倒序），作为**赛博纪念馆**😄。
diff --git a/content/goods/background.jpg b/content/goods/background.jpg
new file mode 100755
index 0000000..b86d59c
Binary files /dev/null and b/content/goods/background.jpg differ
diff --git a/content/posts/_index.en.md b/content/posts/_index.en.md
new file mode 100755
index 0000000..039db52
--- /dev/null
+++ b/content/posts/_index.en.md
@@ -0,0 +1,15 @@
+---
+title: "Documentation"
+description: "Learn how to use Blowfish and its features."
+
+cascade:
+ showDate: false
+ showAuthor: false
+ invertPagination: true
+---
+
+{{< lead >}}
+Simple, yet powerful. Learn how to use Blowfish and its features.
+{{< /lead >}}
+
+---
diff --git a/content/posts/getting-started/index.ja.md b/content/posts/getting-started/index.en.md
similarity index 87%
rename from content/posts/getting-started/index.ja.md
rename to content/posts/getting-started/index.en.md
index 25002c2..b82b184 100644
--- a/content/posts/getting-started/index.ja.md
+++ b/content/posts/getting-started/index.en.md
@@ -9,10 +9,6 @@ series: ["Documentation"]
series_order: 3
---
-{{< alert >}}
-This section assumes you have already [installed the Blowfish theme]({{< ref "docs/installation" >}}).
-{{< /alert >}}
-
{{< alert "fire" >}}
We just launched a CLI tool to help you get started with Blowfish. It will help you with installation and configuration. Install the CLI tool globally using:
@@ -60,8 +56,6 @@ links = [
The `[author]` configuration determines how the author information is displayed on the website. The image should be placed in the site's `assets/` folder. Links will be displayed in the order they are listed.
-If you need extra detail, further information about each of these configuration options, is covered in the [Configuration]({{< ref "configuration" >}}) section.
-
## Colour schemes
Blowfish ships with a number of colour schemes out of the box. To change the scheme, simply set the `colorScheme` theme parameter. Valid options are `blowfish` (default), `avocado`, `fire`, `ocean`, `forest`, `princess`, `neon`, `bloody`, `terminal`, `marvel`, `noir`, `autumn`, `congo`, and`slate`.
@@ -117,7 +111,6 @@ Blowfish defines a three-colour palette that is used throughout the theme. Each
{{< swatches "#6B7280" "#64748b" "#6B7280" >}}
-Although these are the default schemes, you can also create your own. Refer to the [Advanced Customisation]({{< ref "advanced-customisation#colour-schemes" >}}) section for details.
## Organising content
@@ -201,7 +194,6 @@ The `name` parameter specifies the text that is used in the menu link. You can a
The `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.
-The `pre` parameter allows you to place an icon from [Blowfish's icon set]({{< ref "samples/icons" >}}) on the menu entry. This parameter can be used with `name` parameter or by itself. If you want to use multiple menu entries with just icons please set the `identifier`parameter otherwise Hugo will default to the naming tag as the id and probably not display all the menu entries.
Menu links will be sorted from lowest to highest `weight`, and then alphabetically by `name`.
@@ -261,12 +253,9 @@ The default `name` is the `pageRef` title cased.
## Thumbnails & Backgrounds
-Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article structure, you just need to place an image file (almost all formats are supported but we recommend `.png` or `.jpg`) that starts with `feature*` inside your article folder. And that's it, Blowfish will then be able to both use the image as a thumbnail within your website as well as for oEmbed cards across social platforms.
+Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article structure, you just need to place an image file (almost all formats are supported but we recommend `.png` or `.jpg`) that starts with `feature*` inside your article folder. And that's it, Blowfish will then be able to both use the image as a thumbnail within your website as well as for oEmbed cards across social platforms.
-[Here]({{< ref "thumbnails" >}}) is also a guide with more info and a [sample]({{< ref "thumbnail_sample" >}}) if you want to see how you can do it.
Additionally, Blowfish also supports background hero images in articles and lists. In order to use a different image than the featured one, add an image file in which the name starts with `background*`.
## Detailed configuration
-
-The steps above are the bare minimum configuration. If you now run `hugo server` you will be presented with a blank Blowfish website. Detailed configuration is covered in the [Configuration]({{< ref "configuration" >}}) section.
diff --git a/content/posts/getting-started/index.it.md b/content/posts/getting-started/index.it.md
deleted file mode 100644
index cb20912..0000000
--- a/content/posts/getting-started/index.it.md
+++ /dev/null
@@ -1,276 +0,0 @@
----
-title: "Per iniziare"
-weight: 3
-draft: false
-description: "Tutte le variabili del front matter sono disponibili in Blowfish."
-slug: "per-iniziare"
-tags: ["installazione", "documenti"]
-series: ["Documentazione"]
-series_order: 3
----
-
-{{< alert >}}
-Questa sezione presuppone che tu abbia già [installato il tema Blowfish]({{< ref "docs/installation" >}}).
-{{< /alert >}}
-
-
-{{< alert "fire" >}}
-Abbiamo appena lanciato uno strumento CLI per aiutarvi a iniziare con Blowfish. Vi aiuterà con l'installazione e la configurazione. Installate lo strumento CLI a livello globale utilizzando:
-```bash
-npx blowfish-tools
-```
-{{< /alert >}}
-
-
-I file di configurazione forniti con Blowfish contengono tutte le possibili impostazioni riconosciute dal tema. Per impostazione predefinita, molti di questi sono commentati ma puoi semplicemente decommentarli per attivare o modificare una funzionalità specifica.
-
-## Configurazione di base
-
-Prima di creare qualsiasi contenuto, è necessario impostare alcune cose per una nuova installazione. Iniziando dal file `config.toml`, imposta i parametri `baseURL` e `lingualCode`. Il `lingualCode` dovrebbe essere impostato sulla lingua principale che utilizzerai per creare i tuoi contenuti.
-=======
-
-```toml
-# config/_default/hugo.toml
-
-baseURL = "https://your_domain.com/"
-languageCode = "en"
-```
-
-Il passo successivo è configurare le impostazioni della lingua. Sebbene Blowfish supporti le configurazioni multilingue, per ora basta configurare la lingua principale.
-
-Individua il file "languages.en.toml" nella cartella di configurazione. Se la tua lingua principale è l'inglese puoi utilizzare questo file così com'è. Altrimenti, rinominalo in modo che includa il codice della lingua corretto nel nome del file. Ad esempio, per il francese, rinominare il file in "languages.fr.toml".
-
-{{< alert >}}
-
-Tieni presente che il codice della lingua nel nome del file di configurazione della lingua deve corrispondere all'impostazione "languageCode" in "config.toml".
-
-{{< /alert >}}
-
-```toml
-# config/_default/languages.en.toml
-
-title = "My awesome website"
-
-[author]
-name = "My name"
-image = "img/author.jpg"
-headline = "A generally awesome human"
-bio = "A little bit about me"
-links = [
- { twitter = "https://twitter.com/username" }
-]
-```
-La configurazione `[author]` determina il modo in cui le informazioni sull'autore vengono visualizzate sul sito web. L'immagine deve essere posizionata nella cartella `assets/`. I link verranno visualizzati nell'ordine in cui sono elencati.
-
-Se hai bisogno di ulteriori dettagli, ulteriori informazioni su ciascuna di queste opzioni di configurazione sono trattate nella sezione [Configurazione]({{< ref "configuration" >}}).
-
-## Schemi di colori
-
-Blowfish viene fornito con una serie di schemi di colori già pronti. Per cambiare lo schema, è sufficiente impostare il parametro del tema `colorScheme`. Le opzioni valide sono `blowfish` (default), `avocado`, `fire`, `ocean`, `forest`, `princess`, `neon`, `bloody`, `terminal`, `marvel`, `noir`, `autumn`, `congo`, and`slate`.
-
-```toml
-# config/_default/params.toml
-
-colorScheme = "blowfish"
-```
-Blowfish definisce una palette di tre colori che viene utilizzata in tutto il tema. Ogni colore principale contiene dieci sfumature basate sui colori inclusi in [Tailwind](https://tailwindcss.com/docs/customizing-colors#color-palette-reference). I tre colori principali sono utilizzati per l'intestazione, il piè di pagina e i colori d'accento. Ecco i colori per ogni schema:
-
-#### Blowfish (default)
-{{< swatches "#64748b" "#3b82f6" "#06b6d4" >}}
-
-#### Avocado
-{{< swatches "#78716c" "#84cc16" "#10b981" >}}
-
-#### Fire
-{{< swatches "#78716c" "#f97316" "#f43f5e" >}}
-
-#### Ocean
-{{< swatches "#64748b" "#3b82f6" "#06b6d4" >}}
-
-#### Forest
-{{< swatches "#658c86" "#3bf5df" "#06d45c" >}}
-
-#### Princess
-{{< swatches "#8c658c" "#f53bf2" "#7706d4" >}}
-
-#### Neon
-{{< swatches "#8338ec" "#ff006e" "#3a86ff" >}}
-
-#### Bloody
-{{< swatches "#d90429" "#8d99ae" "#457b9d" >}}
-
-#### Terminal
-{{< swatches "#004b23" "#38b000" "#1a759f" >}}
-
-#### Marvel
-{{< swatches "#2541b2" "#d81159" "#ffbc42" >}}
-
-#### Noir
-{{< swatches "#5c6b73" "#9db4c0" "#00a5cf" >}}
-
-#### Autumn
-{{< swatches "#0a9396" "#ee9b00" "#bb3e03" >}}
-
-#### Congo
-{{< swatches "#71717a" "#8b5cf6" "#d946ef" >}}
-
-#### Slate
-{{< swatches "#6B7280" "#64748b" "#6B7280" >}}
-
-
-Sebbene questi siano gli schemi predefiniti, è possibile crearne di propri. Per maggiori informazioni, consultare la sezione [Personalizzazione avanzata]({{< ref "advanced-customisation#colour-schemes" >}}).
-
-## Organizzazione dei contenuti
-
-Per impostazione predefinita, Blowfish non obbliga a utilizzare un particolare tipo di contenuto. In questo modo si è liberi di definire il contenuto come si desidera. Potreste preferire _pages_ per un sito statico, _posts_ per un blog o _projects_ per un portfolio.
-
-Ecco una rapida panoramica di un progetto base di Blowfish. Tutti i contenuti sono inseriti nella cartella `content`:
-
-```shell
-.
-├── assets
-│ └── img
-│ └── author.jpg
-├── config
-│ └── _default
-├── content
-│ ├── _index.md
-│ ├── about.md
-│ └── posts
-│ ├── _index.md
-│ ├── first-post.md
-│ └── another-post
-│ ├── aardvark.jpg
-│ └── index.md
-└── themes
- └── blowfish
-```
-È importante avere una conoscenza approfondita di come Hugo si aspetta che il contenuto sia organizzato, poiché il tema è progettato per sfruttare appieno i pacchetti di pagine di Hugo. Si consiglia di leggere i [documentazione ufficiale di Hugo](https://gohugo.io/content-management/organization/) per maggiori informazioni.
-
-
-Blowfish è flessibile anche per quanto riguarda le tassonomie. Alcuni preferiscono usare _tags_ e _categories_ per raggruppare i loro contenuti, altri preferiscono usare _topics_.
-
-Hugo usa di default post, tag e categorie e questo funziona bene se è quello che vuoi. Tuttavia, se desideri personalizzare questo aspetto, è possibile farlo creando un file di configurazione `taxonomies.toml`:
-
-```toml
-# config/_default/taxonomies.toml
-
-topic = "topics"
-```
-
-Sostituirà i predefiniti _tags_ e _categorie_ con _topics_. Fare riferimento a [Hugo Taxonomy docs](https://gohugo.io/content-management/taxonomies/) per ulteriori informazioni sulla denominazione delle tassonomie.
-
-Quando crei una nuova tassonomia, è necessario sistemare i collegamenti di navigazione sul sito web per puntare alle sezioni corrette, come spiegato di seguito.
-
-## Menu
-
-Blowfish dispone di due menu che possono essere personalizzati per adattarsi al contenuto e al layout del sito. Il menu `main` appare nell'intestazione del sito e il menu `footer` appare in fondo alla pagina, appena sopra la nota di copyright.
-
-Entrambi i menu sono configurati nel file `menus.en.toml`. Simile al file di configurazione delle lingue, se desideri utilizzare un'altra lingua, rinomina questo file e sostituisci `en` con il codice della lingua che si vuole utilizzare.
-
-
-```toml
-# config/_default/menus.toml
-
-[[main]]
- name = "Blog"
- pageRef = "posts"
- weight = 10
-
-[[main]]
- name = "Topics"
- pageRef = "topics"
- weight = 20
-
-[[main]]
- pre = "github"
- name = "GitHub"
- url = "https://github.com/nunocoracao/blowfish"
- weight = 30
-
-[[main]]
- identifier = "github2"
- pre = "github"
- url = "https://github.com/nunocoracao/blowfish"
- weight = 40
-
-[[footer]]
- name = "Privacy"
- url = "https://external-link"
-```
-
-Il parametro `name` specifica il testo utilizzato nel collegamento al menu. Si può anche fornire facoltativamente un `title` che riempie l'attributo HTML title per il collegamento.
-
-Il parametro `pageRef` consente di fare facilmente riferimento alle pagine di contenuto e alle tassonomie di Hugo. È il modo più rapido per configurare il menu, in quanto è sufficiente fare riferimento a qualsiasi elemento di contenuto di Hugo per creare automaticamente il collegamento corretto. Per collegarsi a URL esterni, si può usare il parametro `url`.
-
-Il parametro `pre` consente di inserire un'icona dal [Set di icone di Blowfish] ({{< ref "samples/icons" >}}) nella voce di menu. Questo parametro può essere usato con il parametro `name` o da solo. Se si vogliono usare più voci di menu con le sole icone, imposta il parametro `identifier`, altrimenti Hugo sceglierà come id il tag di denominazione e probabilmente non visualizzerà tutte le voci di menu.
-
-I collegamenti al menu saranno ordinati dal più basso al più alto `peso`, e poi in ordine alfabetico per `name`.
-
-Entrambi i menu sono completamente opzionali e possono essere commentati se non sono necessari. Utilizzare il modello fornito nel file come guida.
-
-### Nested Menu
-
-Il tema supporta anche i menu nidificati. Per usarli devi solo definire una voce genitore in `menu.toml` e i suoi sottomenu utilizzando il parametro `parent` per fare riferimento al genitore. Tutte le proprietà possono essere utilizzate per i sottomenu. `pageRef` e `url` possono essere utilizzati anche nella voce principale. I menu nidificati sono disponibili solo nel menu principale e non nel footer.
-
-
-```toml
-# config/_default/menus.toml
-
-[[main]]
- name = "Parent"
- weight = 20
-
-[[main]]
- name = "sub-menu 1"
- parent = "Parent"
- pageRef = "samples"
- weight = 20
-
-[[main]]
- name = "sub-menu 2"
- parent = "Parent"
- pageRef = "samples"
- weight = 20
-
-[[main]]
- name = "sub-menu 3"
- parent = "Parent"
- pre = "github"
- pageRef = "samples"
- weight = 20
-```
-
-### Menu di navigazione secondario
-
-Inoltre, è possibile configurare un menu di sotto-navigazione. Basta definire nuove voci di menu come `subnavigation` in `menus.toml`.
-Questo renderà una seconda riga con le sottocategorie sotto il menu principale dell'intestazione.
-
-```toml
-# config/_default/menus.toml
-
-[[subnavigation]]
- name = "An interesting topic"
- pageRef = "tags/interesting-topic"
- weight = 10
-
-[[subnavigation]]
- name = "My Awesome Category"
- pageRef = "categories/awesome"
- weight = 20
-```
-
-Il `name` predefinito è il titolo di `pageRef`, con le caselle.
-
-## Thumbnails & Backgrounds
-
-Blowfish è stato creato in modo che sia facile aggiungere supporto visivo ai tuoi articoli. Se hai familiarità con la struttura degli articoli di Hugo, devi solo inserire un file immagine (quasi tutti i formati sono supportati ma consigliamo `.png` o `.jpg`) che inizi con `feature*` all'interno della cartella dell'articolo. E questo è tutto, Blowfish sarà quindi in grado di utilizzare l'immagine sia come miniatura all'interno del tuo sito web sia per le schede oEmbed attraverso le piattaforme social.
-
-[Qui]({{< ref "thumbnails" >}}) è anche una guida con maggiori informazioni e un [esempio]({{< ref "thumbnail_sample" >}}) se vuoi vedere come puoi farlo.
-
-Additionally, Blowfish also supports background hero images in articles and lists. In order to use a different image than the featured one, add an image file in which the name starts with `background*`.
-Inoltre, Blowfish supporta anche una background hero image in articoli ed elenchi. Per utilizzare un'immagine diversa da quella in primo piano, aggiungi un file immagine il cui nome inizia con `background*`.
-
-## Dettagli di configurazione
-
-I passaggi precedenti rappresentano la configurazione minima. Se ora esegui `hugo server` ti verrà presentato un sito web Blowfish vuoto. La configurazione dettagliata è trattata nella sezione [Configurazione]({{< ref "configuration" >}}).
diff --git a/content/posts/getting-started/index.md b/content/posts/getting-started/index.md
deleted file mode 100644
index 25002c2..0000000
--- a/content/posts/getting-started/index.md
+++ /dev/null
@@ -1,272 +0,0 @@
----
-title: "Getting Started"
-weight: 3
-draft: false
-description: "All the front matter variables available in Blowfish."
-slug: "getting-started"
-tags: ["installation", "docs"]
-series: ["Documentation"]
-series_order: 3
----
-
-{{< alert >}}
-This section assumes you have already [installed the Blowfish theme]({{< ref "docs/installation" >}}).
-{{< /alert >}}
-
-
-{{< alert "fire" >}}
-We just launched a CLI tool to help you get started with Blowfish. It will help you with installation and configuration. Install the CLI tool globally using:
-```bash
-npx blowfish-tools
-```
-{{< /alert >}}
-
-
-The config files that ship with Blowfish 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 `hugo.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.
-
-```toml
-# config/_default/hugo.toml
-
-baseURL = "https://your_domain.com/"
-languageCode = "en"
-```
-
-The next step is to configure the language settings. Although Blowfish supports multilingual setups, for now, just configure the main language.
-
-Locate 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`.
-
-{{< alert >}}
-Note that the language code in the language config filename should match the `languageCode` setting in `hugo.toml`.
-{{< /alert >}}
-
-```toml
-# config/_default/languages.en.toml
-
-title = "My awesome website"
-
-[author]
-name = "My name"
-image = "img/author.jpg"
-headline = "A generally awesome human"
-bio = "A little bit about me"
-links = [
- { twitter = "https://twitter.com/username" }
-]
-```
-
-The `[author]` configuration determines how the author information is displayed on the website. The image should be placed in the site's `assets/` folder. Links will be displayed in the order they are listed.
-
-If you need extra detail, further information about each of these configuration options, is covered in the [Configuration]({{< ref "configuration" >}}) section.
-
-## Colour schemes
-
-Blowfish ships with a number of colour schemes out of the box. To change the scheme, simply set the `colorScheme` theme parameter. Valid options are `blowfish` (default), `avocado`, `fire`, `ocean`, `forest`, `princess`, `neon`, `bloody`, `terminal`, `marvel`, `noir`, `autumn`, `congo`, and`slate`.
-
-```toml
-# config/_default/params.toml
-
-colorScheme = "blowfish"
-```
-
-Blowfish 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](https://tailwindcss.com/docs/customizing-colors#color-palette-reference). The three main colours are used for the header, footer, and accent colours. Here are the colors for each scheme:
-
-#### Blowfish (default)
-{{< swatches "#64748b" "#3b82f6" "#06b6d4" >}}
-
-#### Avocado
-{{< swatches "#78716c" "#84cc16" "#10b981" >}}
-
-#### Fire
-{{< swatches "#78716c" "#f97316" "#f43f5e" >}}
-
-#### Ocean
-{{< swatches "#64748b" "#3b82f6" "#06b6d4" >}}
-
-#### Forest
-{{< swatches "#658c86" "#3bf5df" "#06d45c" >}}
-
-#### Princess
-{{< swatches "#8c658c" "#f53bf2" "#7706d4" >}}
-
-#### Neon
-{{< swatches "#8338ec" "#ff006e" "#3a86ff" >}}
-
-#### Bloody
-{{< swatches "#d90429" "#8d99ae" "#457b9d" >}}
-
-#### Terminal
-{{< swatches "#004b23" "#38b000" "#1a759f" >}}
-
-#### Marvel
-{{< swatches "#2541b2" "#d81159" "#ffbc42" >}}
-
-#### Noir
-{{< swatches "#5c6b73" "#9db4c0" "#00a5cf" >}}
-
-#### Autumn
-{{< swatches "#0a9396" "#ee9b00" "#bb3e03" >}}
-
-#### Congo
-{{< swatches "#71717a" "#8b5cf6" "#d946ef" >}}
-
-#### Slate
-{{< swatches "#6B7280" "#64748b" "#6B7280" >}}
-
-
-Although these are the default schemes, you can also create your own. Refer to the [Advanced Customisation]({{< ref "advanced-customisation#colour-schemes" >}}) section for details.
-
-## Organising content
-
-By default, Blowfish doesn'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.
-
-Here's a quick overview of a basic Blowfish project. All content is placed within the `content` folder:
-
-```shell
-.
-├── assets
-│ └── img
-│ └── author.jpg
-├── config
-│ └── _default
-├── content
-│ ├── _index.md
-│ ├── about.md
-│ └── posts
-│ ├── _index.md
-│ ├── first-post.md
-│ └── another-post
-│ ├── aardvark.jpg
-│ └── index.md
-└── themes
- └── blowfish
-```
-
-It'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](https://gohugo.io/content-management/organization/) for more information.
-
-Blowfish 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_.
-
-Hugo defaults to using posts, tags and categories out of the box and this will work fine if that's what you want. If you wish to customise this, however, you can do so by creating a `taxonomies.toml` configuration file:
-
-```toml
-# config/_default/taxonomies.toml
-
-topic = "topics"
-```
-
-This will replace the default _tags_ and _categories_ with _topics_. Refer to the [Hugo Taxonomy docs](https://gohugo.io/content-management/taxonomies/) for more information on naming taxonomies.
-
-When 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.
-
-## Menus
-
-Blowfish 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.
-
-Both 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.
-
-```toml
-# config/_default/menus.toml
-
-[[main]]
- name = "Blog"
- pageRef = "posts"
- weight = 10
-
-[[main]]
- name = "Topics"
- pageRef = "topics"
- weight = 20
-
-[[main]]
- pre = "github"
- name = "GitHub"
- url = "https://github.com/nunocoracao/blowfish"
- weight = 30
-
-[[main]]
- identifier = "github2"
- pre = "github"
- url = "https://github.com/nunocoracao/blowfish"
- weight = 40
-
-[[footer]]
- name = "Privacy"
- url = "https://external-link"
-```
-
-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.
-
-The `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.
-
-The `pre` parameter allows you to place an icon from [Blowfish's icon set]({{< ref "samples/icons" >}}) on the menu entry. This parameter can be used with `name` parameter or by itself. If you want to use multiple menu entries with just icons please set the `identifier`parameter otherwise Hugo will default to the naming tag as the id and probably not display all the menu entries.
-
-Menu links will be sorted from lowest to highest `weight`, and then alphabetically by `name`.
-
-Both menus are completely optional and can be commented out if not required. Use the template provided in the file as a guide.
-
-### Nested menus
-
-The theme also supports nested menus. In order to use them you just need to define a parent entry in `menu.toml` and its sub-menus using the `parent` parameter to reference the parent. All properties can be used for sub-menus. `pageRef` and `url` can also be used in the parent entry. Nested menus are only available in the main menu not for the footer.
-
-```toml
-# config/_default/menus.toml
-
-[[main]]
- name = "Parent"
- weight = 20
-
-[[main]]
- name = "sub-menu 1"
- parent = "Parent"
- pageRef = "samples"
- weight = 20
-
-[[main]]
- name = "sub-menu 2"
- parent = "Parent"
- pageRef = "samples"
- weight = 20
-
-[[main]]
- name = "sub-menu 3"
- parent = "Parent"
- pre = "github"
- pageRef = "samples"
- weight = 20
-```
-
-### Sub-Navigation menu
-
-Additionally, you can also configure a sub-navigation menu. Just define new menu entries as `subnavigation` in `menus.toml`.
-This will render a second line with sub-categories below the main header menu.
-
-```toml
-# config/_default/menus.toml
-
-[[subnavigation]]
- name = "An interesting topic"
- pageRef = "tags/interesting-topic"
- weight = 10
-
-[[subnavigation]]
- name = "My Awesome Category"
- pageRef = "categories/awesome"
- weight = 20
-```
-
-The default `name` is the `pageRef` title cased.
-
-## Thumbnails & Backgrounds
-
-Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article structure, you just need to place an image file (almost all formats are supported but we recommend `.png` or `.jpg`) that starts with `feature*` inside your article folder. And that's it, Blowfish will then be able to both use the image as a thumbnail within your website as well as for oEmbed cards across social platforms.
-
-[Here]({{< ref "thumbnails" >}}) is also a guide with more info and a [sample]({{< ref "thumbnail_sample" >}}) if you want to see how you can do it.
-
-Additionally, Blowfish also supports background hero images in articles and lists. In order to use a different image than the featured one, add an image file in which the name starts with `background*`.
-
-## Detailed configuration
-
-The steps above are the bare minimum configuration. If you now run `hugo server` you will be presented with a blank Blowfish website. Detailed configuration is covered in the [Configuration]({{< ref "configuration" >}}) section.
diff --git a/content/posts/shortcodes/index.md b/content/posts/shortcodes/index.en.md
similarity index 97%
rename from content/posts/shortcodes/index.md
rename to content/posts/shortcodes/index.en.md
index 9747daf..aea5958 100644
--- a/content/posts/shortcodes/index.md
+++ b/content/posts/shortcodes/index.en.md
@@ -184,7 +184,6 @@ data: {
{{< /chart >}}
-You can see some additional Chart.js examples on the [charts samples]({{< ref "charts" >}}) page.
@@ -407,7 +406,7 @@ In order to add images to the gallery, use `img` tags for each image and add `cl
## GitLab Card
-`gitlab` allows you to quickly link a GitLab Project (GitLab's jargon for repo).
+`gitlab` allows you to quickly link a GitLab Project (GitLab's jargon for repo).
It displays realtime stats about it, such as the number of stars and forks it has.
Unlike `github` it can't display the main programming language of a project.
Finally, custom GitLab instance URL can be provided, as long as the `api/v4/projects/` endpoint is available, making this shortcode compatible with most self-hosted / enterprise deployments.
@@ -441,12 +440,9 @@ Finally, custom GitLab instance URL can be provided, as long as the `api/v4/proj
**Output:** {{< icon "github" >}}
-Icons are populated using Hugo pipelines which makes them very flexible. Blowfish includes a number of built-in icons for social, links and other purposes. Check the [icon samples]({{< ref "samples/icons" >}}) page for a full list of supported icons.
Custom 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.
-Icons can also be used in partials by calling the [icon partial]({{< ref "partials#icon" >}}).
-
## KaTeX
@@ -467,7 +463,6 @@ Inline notation can be generated by wrapping the expression in `\\(` and `\\)` d
{{< katex >}}
\\(f(a,b,c) = (a^2+b^2+c^2)^3\\)
-Check out the [mathematical notation samples]({{< ref "mathematical-notation" >}}) page for more examples.
@@ -529,7 +524,7 @@ When life gives you lemons, make lemonade.
When life gives you lemons, make lemonade.
{{< /lead >}}
-
+
## List
@@ -568,7 +563,7 @@ The `where` and `value` values are used in the following query `where .Site.Regu
-## LTR/RTL
+## LTR/RTL
`ltr` and `rtl` allows you to mix your contents. Many RTL language users want to include parts of the content in LTR. Using this shortcode will let you do so, and by leveraging `%` as the outer-most dilemeter in the shortcode [Hugo shortcodes](https://gohugo.io/content-management/shortcodes/#shortcodes-with-markdown), any markdown inside will be rendered normally.
@@ -641,7 +636,6 @@ A[Lemons]-->B[Lemonade];
B-->C[Profit]
{{< /mermaid >}}
-You can see some additional Mermaid examples on the [diagrams and flowcharts samples]({{< ref "diagrams-flowcharts" >}}) page.
@@ -681,7 +675,7 @@ The `timeline` creates a visual timeline that can be used in different use-cases
{{}}
{{}}
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus non magna ex. Donec sollicitudin ut lorem quis lobortis. Nam ac ipsum libero. Sed a ex eget ipsum tincidunt venenatis quis sed nisl. Pellentesque sed urna vel odio consequat tincidunt id ut purus. Nam sollicitudin est sed dui interdum rhoncus.
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus non magna ex. Donec sollicitudin ut lorem quis lobortis. Nam ac ipsum libero. Sed a ex eget ipsum tincidunt venenatis quis sed nisl. Pellentesque sed urna vel odio consequat tincidunt id ut purus. Nam sollicitudin est sed dui interdum rhoncus.
{{}}
@@ -718,7 +712,7 @@ With other shortcodes
{{< timeline >}}
{{< timelineItem icon="github" header="header" badge="badge test" subheader="subheader" >}}
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus non magna ex. Donec sollicitudin ut lorem quis lobortis. Nam ac ipsum libero. Sed a ex eget ipsum tincidunt venenatis quis sed nisl. Pellentesque sed urna vel odio consequat tincidunt id ut purus. Nam sollicitudin est sed dui interdum rhoncus.
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus non magna ex. Donec sollicitudin ut lorem quis lobortis. Nam ac ipsum libero. Sed a ex eget ipsum tincidunt venenatis quis sed nisl. Pellentesque sed urna vel odio consequat tincidunt id ut purus. Nam sollicitudin est sed dui interdum rhoncus.
{{}}
@@ -776,7 +770,7 @@ Blowfish implements a sub-set of TypeIt features using a `shortcode`. Write your
```md
{{}}
-Lorem ipsum dolor sit amet
+Lorem ipsum dolor sit amet
{{}}
```
@@ -787,12 +781,12 @@ Lorem ipsum dolor sit amet
**Example 2:**
```md
-{{}}
-Lorem ipsum dolor sit amet,
-consectetur adipiscing elit.
+Lorem ipsum dolor sit amet,
+consectetur adipiscing elit.
{{}}
```
@@ -807,7 +801,7 @@ consectetur adipiscing elit.
**Example 3:**
```md
-{{
+
+ {{ if .Params.showHero | default (.Site.Params.article.showHero | default false) }}
+ {{ $heroStyle := .Params.heroStyle }}
+ {{ if not $heroStyle }}{{ $heroStyle = .Site.Params.article.heroStyle }}{{ end }}
+ {{ $heroStyle := print "partials/hero/" $heroStyle ".html" }}
+ {{ if templates.Exists $heroStyle }}
+ {{ partial $heroStyle . }}
+ {{ else }}
+ {{ partial "partials/hero/basic.html" . }}
+ {{ end }}
+ {{ end }}
+
+ {{ if .Params.showBreadcrumbs | default (.Site.Params.article.showBreadcrumbs | default false) }}
+ {{ partial "breadcrumbs.html" . }}
+ {{ end }}
+
+