mirror of
https://github.com/nunocoracao/blowfish.git
synced 2025-01-22 14:35:43 -06:00
Fix typos
This commit is contained in:
parent
0b8df7ea18
commit
bd2a50aade
10 changed files with 17 additions and 17 deletions
|
@ -35,9 +35,9 @@
|
||||||
- Indent using 2 spaces (soft tabs).
|
- Indent using 2 spaces (soft tabs).
|
||||||
- Put spaces between list items (ie. `[1, 2, 3]`, not `[1,2,3]`), around operators (ie. `1 + 1`, not `1+1`) and inside go templating tags (ie. `{{< alert >}}`, not `{{<alert>}}`).
|
- Put spaces between list items (ie. `[1, 2, 3]`, not `[1,2,3]`), around operators (ie. `1 + 1`, not `1+1`) and inside go templating tags (ie. `{{< alert >}}`, not `{{<alert>}}`).
|
||||||
- Avoid code reuse in templates by extracting components into partials.
|
- Avoid code reuse in templates by extracting components into partials.
|
||||||
- Layout code in a logical manner that prioritises readibility.
|
- Layout code in a logical manner that prioritises readability.
|
||||||
- Add comments when the intent of the code isn't immediately apparent or to break up large blocks of logic.
|
- Add comments when the intent of the code isn't immediately apparent or to break up large blocks of logic.
|
||||||
- Use relative paths to assets without including the preceeding slash but, when referring to a folder, including a trailing slash (ie. `static/img/`, not `/static/img/` or `/static/img`).
|
- Use relative paths to assets without including the preceding slash but, when referring to a folder, including a trailing slash (ie. `static/img/`, not `/static/img/` or `/static/img`).
|
||||||
- Any static text must be referenced using the `i18n` methods and included in the localisation assets.
|
- Any static text must be referenced using the `i18n` methods and included in the localisation assets.
|
||||||
- Commit often, preferring incremental changes rather than bundling everything into a single, large commit.
|
- Commit often, preferring incremental changes rather than bundling everything into a single, large commit.
|
||||||
|
|
||||||
|
|
|
@ -37,7 +37,7 @@ Blowfish is designed to be a powerful, lightweight theme for [Hugo](https://gohu
|
||||||
- Flexible with any content types, taxonomies and menus
|
- Flexible with any content types, taxonomies and menus
|
||||||
- Header and footer menus
|
- Header and footer menus
|
||||||
- Nested menus & sub-navigation menu
|
- Nested menus & sub-navigation menu
|
||||||
- Multilingual content support inlcuding support for RTL languages
|
- Multilingual content support including support for RTL languages
|
||||||
- Ability to link to posts on third-party websites
|
- Ability to link to posts on third-party websites
|
||||||
- Support for several shortcodes like Gallery, Timeline, GitHub cards, and Carousels
|
- Support for several shortcodes like Gallery, Timeline, GitHub cards, and Carousels
|
||||||
- Buymeacoffee integration
|
- Buymeacoffee integration
|
||||||
|
|
|
@ -21,7 +21,7 @@ Before leaping into it, first a quick note about [Hugo project structure](https:
|
||||||
**In summary:** Never directly edit the theme files. Only make customisations in your Hugo project's sub-directories, not in the themes directory itself.
|
**In summary:** Never directly edit the theme files. Only make customisations in your Hugo project's sub-directories, not in the themes directory itself.
|
||||||
{{< /alert >}}
|
{{< /alert >}}
|
||||||
|
|
||||||
Blowfish 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.
|
Blowfish 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 overridden 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.
|
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.
|
||||||
|
|
||||||
|
@ -56,7 +56,7 @@ Blowfish ships with a number of colour schemes out of the box. To change the bas
|
||||||
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.
|
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.
|
||||||
|
|
||||||
{{< alert "github">}}
|
{{< alert "github">}}
|
||||||
**Note:** generating these files manually can be hard, I've built a `nodejs` terminal tool to help with that, [Fugu](https://github.com/nunocoracao/fugu). In a nutshell, you pass the main three `hex` values of your color pallette and the program will output a css file that can be imported directly into Blowfish.
|
**Note:** generating these files manually can be hard, I've built a `nodejs` terminal tool to help with that, [Fugu](https://github.com/nunocoracao/fugu). In a nutshell, you pass the main three `hex` values of your color palette and the program will output a css file that can be imported directly into Blowfish.
|
||||||
{{< /alert >}}
|
{{< /alert >}}
|
||||||
|
|
||||||
|
|
||||||
|
@ -82,7 +82,7 @@ The `custom.css` file will be minified by Hugo and loaded automatically after al
|
||||||
|
|
||||||
### Using additional fonts
|
### Using additional fonts
|
||||||
|
|
||||||
Blowfish allows you to easily change the font for your site. After creating a `custom.css` file in your project's `assets/css/` folder, place you font file inside a `fonts` folder withing the `static` root folder.
|
Blowfish allows you to easily change the font for your site. After creating a `custom.css` file in your project's `assets/css/` folder, place you font file inside a `fonts` folder within the `static` root folder.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
.
|
.
|
||||||
|
|
|
@ -45,7 +45,7 @@ Note that the variable names provided in this table use dot notation to simplify
|
||||||
|
|
||||||
## Thumbnails
|
## Thumbnails
|
||||||
|
|
||||||
Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article strucutre, 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 able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> 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 able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> 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.
|
[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.
|
||||||
|
|
||||||
|
@ -169,7 +169,7 @@ Many of the article defaults here can be overridden on a per article basis by sp
|
||||||
| `disableImageOptimization` | `false` | Disables image resize and optimization features across all the images in the site. |
|
| `disableImageOptimization` | `false` | Disables image resize and optimization features across all the images in the site. |
|
||||||
| `disableTextInHeader` | `false` | Disables text in header, useful for logo based headers. |
|
| `disableTextInHeader` | `false` | Disables text in header, useful for logo based headers. |
|
||||||
| `defaultBackgroundImage` | _Not set_ | Default background image for both `background` homepage layout and `background` hero style |
|
| `defaultBackgroundImage` | _Not set_ | Default background image for both `background` homepage layout and `background` hero style |
|
||||||
| `defaultFeaturedImage` | _Not set_ | Default background image for all `featured` images across articles, will be overriden by a local `featured` image. |
|
| `defaultFeaturedImage` | _Not set_ | Default background image for all `featured` images across articles, will be overridden by a local `featured` image. |
|
||||||
| `highlightCurrentMenuArea` | _Not set_ | Marks menu entries in the main manu when selected |
|
| `highlightCurrentMenuArea` | _Not set_ | Marks menu entries in the main manu when selected |
|
||||||
| `smartTOC` | _Not set_ | Activate smart Table of Contents, items in view will be highlighted. |
|
| `smartTOC` | _Not set_ | Activate smart Table of Contents, items in view will be highlighted. |
|
||||||
| `smartTOCHideUnfocusedChildren` | _Not set_ | When smart Table of Contents is turned on, this will hide deeper levels of the table when they are not in focus. |
|
| `smartTOCHideUnfocusedChildren` | _Not set_ | When smart Table of Contents is turned on, this will hide deeper levels of the table when they are not in focus. |
|
||||||
|
@ -196,7 +196,7 @@ Many of the article defaults here can be overridden on a per article basis by sp
|
||||||
| `homepage.homepageImage` | _Not set_ | Image to be used in `hero` and `card` layouts. Refer to the [Homepage Layout]({{< ref "homepage-layout" >}}) section for more details. |
|
| `homepage.homepageImage` | _Not set_ | Image to be used in `hero` and `card` layouts. Refer to the [Homepage Layout]({{< ref "homepage-layout" >}}) section for more details. |
|
||||||
| `homepage.showRecent` | `false` | Whether or not to display the recent articles list on the homepage. |
|
| `homepage.showRecent` | `false` | Whether or not to display the recent articles list on the homepage. |
|
||||||
| `homepage.showRecentItems` | 5 | How many articles to display if showRecent is true. If variable is set to 0 or if it isn't defined the system will default to 5 articles. |
|
| `homepage.showRecentItems` | 5 | How many articles to display if showRecent is true. If variable is set to 0 or if it isn't defined the system will default to 5 articles. |
|
||||||
| `homepage.showMoreLink` | `false` | Wether or not to display a show more link at the end of your posts that takes the user to a predefined place. |
|
| `homepage.showMoreLink` | `false` | Whether or not to display a show more link at the end of your posts that takes the user to a predefined place. |
|
||||||
| `homepage.showMoreLinkDest` | `/posts` | The destination of the show more button. |
|
| `homepage.showMoreLinkDest` | `/posts` | The destination of the show more button. |
|
||||||
| `homepage.cardView` | `false` | Display recent articles as a gallery of cards. |
|
| `homepage.cardView` | `false` | Display recent articles as a gallery of cards. |
|
||||||
| `homepage.cardViewScreenWidth` | `false` | Enhance the width of the recent articles card gallery to take the full width available. |
|
| `homepage.cardViewScreenWidth` | `false` | Enhance the width of the recent articles card gallery to take the full width available. |
|
||||||
|
|
|
@ -25,7 +25,7 @@ Front matter parameter default values are inherited from the theme's [base confi
|
||||||
| `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`. |
|
| `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's docs](https://developers.google.com/search/docs/advanced/robots/robots_meta_tag#directives) for valid values. |
|
| `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's docs](https://developers.google.com/search/docs/advanced/robots/robots_meta_tag#directives) 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. |
|
| `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 for the deafult author is displayed in the article footer. |
|
| `showAuthor` | `article.showAuthor` | Whether or not the author box for the default author is displayed in the article footer. |
|
||||||
| `authors` | _Not set_ | Array of values for authors, if set it overrides `showAuthor` settings for page or site. Used on the multiple authors feature, check [this page]({{< ref "multi-author" >}}) for more details on how to configure that feature. |
|
| `authors` | _Not set_ | Array of values for authors, if set it overrides `showAuthor` settings for page or site. Used on the multiple authors feature, check [this page]({{< ref "multi-author" >}}) for more details on how to configure that feature. |
|
||||||
| `showAuthorsBadges` | `article.showAuthorsBadges` | Whether the `authors` taxonomies are are displayed in the article or list header. This requires the setup of `multiple authors` and the `authors` taxonomy. Check [this page]({{< ref "multi-author" >}}) for more details on how to configure that feature. |
|
| `showAuthorsBadges` | `article.showAuthorsBadges` | Whether the `authors` taxonomies are are displayed in the article or list header. This requires the setup of `multiple authors` and the `authors` taxonomy. Check [this page]({{< ref "multi-author" >}}) for more details on how to configure that feature. |
|
||||||
| `showHero` | `article.showHero` | Whether the thumbnail image will be shown as a hero image within the article page. |
|
| `showHero` | `article.showHero` | Whether the thumbnail image will be shown as a hero image within the article page. |
|
||||||
|
|
|
@ -249,7 +249,7 @@ The default `name` is the `pageRef` title cased.
|
||||||
|
|
||||||
## Thumbnails & Backgrounds
|
## Thumbnails & Backgrounds
|
||||||
|
|
||||||
Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article strucutre, 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 able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> 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 able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> 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.
|
[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.
|
||||||
|
|
||||||
|
|
|
@ -80,7 +80,7 @@ The articles listed in this section are derived from the `mainSections` setting
|
||||||
|
|
||||||
## Thumbnails
|
## Thumbnails
|
||||||
|
|
||||||
Blowfish was built so it would be easy to add visual support to your articles. If your familiar with Hugo article strucutre, you just need to place an image file (almost all formats are supported bue we recommend `.png` or `.jpg`) that starts with `feature*` inside your article folder. And that's it, Blowfish will then able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> 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 able to both use the image as a thumbnail within your website as well as for <a target="_blank" href="https://oembed.com/">oEmbed</a> cards across social platforms.
|
||||||
|
|
||||||
[Here]({{< ref "thumbnails" >}}) is a guide with more info and a [sample]({{< ref "thumbnail_sample" >}}) if you want to see an example.
|
[Here]({{< ref "thumbnails" >}}) is a guide with more info and a [sample]({{< ref "thumbnail_sample" >}}) if you want to see an example.
|
||||||
|
|
||||||
|
|
|
@ -316,13 +316,13 @@ In order to add images to the gallery, use `img` tags for each image and add `cl
|
||||||
`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.
|
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.
|
Unlike `github` it can't display the main programming language of a project.
|
||||||
Finaly custom GitLab instace URL can be provided, as long as the `api/v4/projects/` endpoint is available, making this shortcode compatible with most self-hosted / entreprise deployments.
|
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.
|
||||||
|
|
||||||
<!-- prettier-ignore-start -->
|
<!-- prettier-ignore-start -->
|
||||||
| Parameter | Description |
|
| Parameter | Description |
|
||||||
| ----------- | ---------------------------------------------------------------------- |
|
| ----------- | ---------------------------------------------------------------------- |
|
||||||
| `projectID` | [String] gitlab numeric ProjectID |
|
| `projectID` | [String] gitlab numeric ProjectID |
|
||||||
| `baseURL` | [String] optional gitlab instace URL, default is `https://gitlab.com/` |
|
| `baseURL` | [String] optional gitlab instance URL, default is `https://gitlab.com/` |
|
||||||
<!-- prettier-ignore-end -->
|
<!-- prettier-ignore-end -->
|
||||||
|
|
||||||
**Example 1:**
|
**Example 1:**
|
||||||
|
@ -576,7 +576,7 @@ The `timeline` creates a visual timeline that can be used in different use-cases
|
||||||
| ----------- | -------------------------------------------- |
|
| ----------- | -------------------------------------------- |
|
||||||
| `icon` | the icon to be used in the timeline visuals. |
|
| `icon` | the icon to be used in the timeline visuals. |
|
||||||
| `header` | header for each entry |
|
| `header` | header for each entry |
|
||||||
| `badge` | text to place within the top righ badge |
|
| `badge` | text to place within the top right badge |
|
||||||
| `subheader` | entry's subheader |
|
| `subheader` | entry's subheader |
|
||||||
|
|
||||||
<!-- prettier-ignore-end -->
|
<!-- prettier-ignore-end -->
|
||||||
|
|
|
@ -14,6 +14,6 @@ Recipes, guides, and tutorials for Blowfish
|
||||||
|
|
||||||
**Blowfish user?** To add your guide to this list, [check the template](/guides/template/).
|
**Blowfish user?** To add your guide to this list, [check the template](/guides/template/).
|
||||||
|
|
||||||
This section contains guides for a variety of scnearios on how to configure your theme. If you're new, check out the [Installation]({{< ref "docs/installation" >}}) guide to begin or visit the [Samples]({{< ref "samples" >}}) section to see what Blowfish can do.
|
This section contains guides for a variety of scenarios on how to configure your theme. If you're new, check out the [Installation]({{< ref "docs/installation" >}}) guide to begin or visit the [Samples]({{< ref "samples" >}}) section to see what Blowfish can do.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
|
@ -4,6 +4,6 @@ title: Tags
|
||||||
|
|
||||||
Blowfish 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.
|
Blowfish 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]({{< ref "advanced" >}}) below to see how to take this concept even further.
|
This area could be used to add some extra descriptive text to each taxonomy. Check out the [advanced tag]({{< ref "advanced" >}}) below to see how to take this concept even further.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
Loading…
Reference in a new issue