fix typos, make markdownlint happy

Signed-off-by: Daniel Holbach <daniel.holbach@gmail.com>
This commit is contained in:
Daniel Holbach 2024-07-11 09:19:21 +02:00 committed by zjedi
parent a20a2ff6cd
commit 6264a749df
7 changed files with 16 additions and 11 deletions

View file

@ -5,7 +5,7 @@
/* Used for Landing screen menu buttons, but potentially usable for highlighting other things */
--highlight: #86c440;
--highlight-contrast: var(--cover-text-color);
/*iverse colors used for :hover */
/*inverse colors used for :hover */
--highlight-inverse: var(--cover-text-color);
--highlight-inverse-contrast: white;
@ -29,7 +29,7 @@
/* Dark section - background color */
--section-dark-bg-color: #b80135;
/* Light&Dark section >quote. Supressive color, compared to 'Light section - text color'*/
/* Light&Dark section >quote. Suppressive color, compared to 'Light section - text color'*/
--section-uni-quote: grey;
/* Light&Dark section `code` a bit darker than 'Light section - background color' */
--section-uni-code-bg-color: #e0ded7;

View file

@ -93,7 +93,7 @@ enableEmoji = true
# url = ""
# icon = ""
# Define additіonal languages
# Define additional languages
[languages]
[languages.en]
weight = 10

View file

@ -9,10 +9,12 @@ This demonstates localized content placed in dedicated language folder, `content
See i18n configuration in `[languages]` section of `config.toml`.
#### Local content
Localised content can be put in dedicated folder `content/de/`. Images should be naturally found from there:
![Image from content/de ](de-happy-ethnic-woman-sitting-at-table-with-laptop-3769021.jpg)
#### Assets
Images in assets folder can be localised, conventionally by adding `.de` suffix. However, assets may be tricky, see next section for details
![Broken DE Image from assets](images/asset-happy-ethnic-woman-sitting-at-table-with-laptop-3769021.de.jpg)

View file

@ -7,18 +7,21 @@ header_menu: true
This demonstates localized variants `about-me.de.md` placed along the primary language content, such as `content/en`. Both localisation approaches (separate folder, suffixes in the same folder) can be used and mixed.
#### Local content
When localised page variants are placed along, images of other languages can't be used directly. You would need to use `.de`-suffixed copy of the image: `![Jane Doe](en-happy-ethnic-woman-sitting-at-table-with-laptop-3769021.de.jpg)`
Consider using assets instead.
Images from local content location can't be pipeline-processed.
#### Static
Alternatively, images can be injected from `static/images`:
![Jane Doe](/images/static-happy-ethnic-woman-sitting-at-table-with-laptop-3769021.jpg)
Note the leading `/` is required in this case.
Images from static location can't be pipeline-processed and are always copied when publishing the site, even if not linked from any page.
#### Assets
Latest Hugo version supports injection from `assets` via natural Markdown notation, which empowers this approach for injecting images since pipeline processing (resizing etc) can be used. However, It only worked for me with the local test deployment, there were issues while deploying previews Netlify. Possible workaround would be to use custom shortcode to "touch" the image via [Resources.GetMatch](https://gohugo.io/functions/resources/getmatch/). I hope this gets fixed someday.
![Broken image from assets](images/asset-happy-ethnic-woman-sitting-at-table-with-laptop-3769021.jpg)