fix(purge) : élmination du code de tous les éléments inutiles du thème
binario
This commit is contained in:
parent
2fa809be31
commit
b16edd63dc
GPG Key ID:
3A9774E9CCBF3501
@ -1,19 +0,0 @@
|
||||
# editorconfig.org
|
||||
root = true
|
||||
|
||||
[*]
|
||||
charset = utf-8
|
||||
indent_style = tab
|
||||
end_of_line = lf
|
||||
trim_trailing_whitespace = true
|
||||
insert_final_newline = true
|
||||
|
||||
[*.md]
|
||||
trim_trailing_whitespace = false
|
||||
|
||||
[*.{json,yaml,yml,toml,md,babelrc,eslintrc,stylelintrc}]
|
||||
indent_style = space
|
||||
indent_size = 2
|
||||
|
||||
[layouts/**.{html,svg}]
|
||||
insert_final_newline = false
|
||||
@ -1,319 +0,0 @@
|
||||
{
|
||||
"plugins": [
|
||||
"stylelint-order"
|
||||
],
|
||||
"rules": {
|
||||
"at-rule-empty-line-before": [
|
||||
"always",
|
||||
{
|
||||
"except": [
|
||||
"blockless-after-same-name-blockless",
|
||||
"first-nested"
|
||||
],
|
||||
"ignore": [
|
||||
"after-comment"
|
||||
]
|
||||
}
|
||||
],
|
||||
"at-rule-name-case": "lower",
|
||||
"at-rule-name-space-after": "always-single-line",
|
||||
"at-rule-semicolon-newline-after": "always",
|
||||
"block-closing-brace-newline-after": "always",
|
||||
"block-closing-brace-empty-line-before": "never",
|
||||
"block-no-empty": true,
|
||||
"block-opening-brace-newline-after": "always-multi-line",
|
||||
"color-hex-case": "lower",
|
||||
"color-hex-length": "short",
|
||||
"color-no-invalid-hex": true,
|
||||
"comment-no-empty": true,
|
||||
"declaration-bang-space-after": "never",
|
||||
"declaration-bang-space-before": "always",
|
||||
"declaration-block-no-duplicate-properties": [
|
||||
true,
|
||||
{
|
||||
"ignore": [
|
||||
"consecutive-duplicates-with-different-values"
|
||||
]
|
||||
}
|
||||
],
|
||||
"declaration-block-no-shorthand-property-overrides": true,
|
||||
"declaration-block-semicolon-newline-after": "always-multi-line",
|
||||
"declaration-block-semicolon-space-after": "always-single-line",
|
||||
"declaration-block-semicolon-space-before": "never",
|
||||
"declaration-block-single-line-max-declarations": 1,
|
||||
"declaration-block-trailing-semicolon": "always",
|
||||
"declaration-colon-newline-after": "always-multi-line",
|
||||
"declaration-colon-space-after": "always-single-line",
|
||||
"declaration-colon-space-before": "never",
|
||||
"font-family-no-duplicate-names": true,
|
||||
"function-calc-no-unspaced-operator": true,
|
||||
"function-comma-newline-after": "always-multi-line",
|
||||
"function-comma-space-after": "always-single-line",
|
||||
"function-comma-space-before": "never",
|
||||
"function-linear-gradient-no-nonstandard-direction": true,
|
||||
"function-max-empty-lines": 0,
|
||||
"function-name-case": "lower",
|
||||
"function-parentheses-newline-inside": "always-multi-line",
|
||||
"function-parentheses-space-inside": "never-single-line",
|
||||
"function-whitespace-after": "always",
|
||||
"indentation": "tab",
|
||||
"keyframe-declaration-no-important": true,
|
||||
"length-zero-no-unit": true,
|
||||
"max-empty-lines": 1,
|
||||
"media-feature-colon-space-after": "always",
|
||||
"media-feature-colon-space-before": "never",
|
||||
"media-feature-name-case": "lower",
|
||||
"media-feature-name-no-unknown": true,
|
||||
"media-feature-parentheses-space-inside": "never",
|
||||
"media-feature-range-operator-space-after": "always",
|
||||
"media-feature-range-operator-space-before": "always",
|
||||
"media-query-list-comma-newline-after": "always-multi-line",
|
||||
"media-query-list-comma-space-after": "always-single-line",
|
||||
"media-query-list-comma-space-before": "never",
|
||||
"no-empty-source": true,
|
||||
"no-eol-whitespace": true,
|
||||
"no-extra-semicolons": true,
|
||||
"no-invalid-double-slash-comments": true,
|
||||
"no-missing-end-of-source-newline": true,
|
||||
"number-no-trailing-zeros": true,
|
||||
"property-case": "lower",
|
||||
"property-no-unknown": true,
|
||||
"selector-attribute-brackets-space-inside": "never",
|
||||
"selector-attribute-operator-space-after": "never",
|
||||
"selector-attribute-operator-space-before": "never",
|
||||
"selector-combinator-space-after": "always",
|
||||
"selector-combinator-space-before": "always",
|
||||
"selector-descendant-combinator-no-non-space": true,
|
||||
"selector-list-comma-newline-after": "always",
|
||||
"selector-list-comma-space-before": "never",
|
||||
"selector-pseudo-class-case": "lower",
|
||||
"selector-pseudo-class-no-unknown": true,
|
||||
"selector-pseudo-class-parentheses-space-inside": "never",
|
||||
"selector-pseudo-element-case": "lower",
|
||||
"selector-pseudo-element-colon-notation": "double",
|
||||
"selector-pseudo-element-no-unknown": true,
|
||||
"selector-type-case": "lower",
|
||||
"selector-type-no-unknown": true,
|
||||
"shorthand-property-no-redundant-values": true,
|
||||
"string-no-newline": true,
|
||||
"unit-case": "lower",
|
||||
"unit-no-unknown": true,
|
||||
"value-list-comma-newline-after": "always-multi-line",
|
||||
"value-list-comma-space-after": "always-single-line",
|
||||
"value-list-comma-space-before": "never",
|
||||
"value-list-max-empty-lines": 0,
|
||||
"order/properties-order": [
|
||||
"position",
|
||||
"top",
|
||||
"right",
|
||||
"bottom",
|
||||
"left",
|
||||
"z-index",
|
||||
"box-sizing",
|
||||
"display",
|
||||
"flex",
|
||||
"flex-align",
|
||||
"flex-basis",
|
||||
"flex-direction",
|
||||
"flex-wrap",
|
||||
"flex-flow",
|
||||
"flex-shrink",
|
||||
"flex-grow",
|
||||
"flex-wrap",
|
||||
"align-content",
|
||||
"align-items",
|
||||
"align-self",
|
||||
"justify-content",
|
||||
"order",
|
||||
"float",
|
||||
"width",
|
||||
"min-width",
|
||||
"max-width",
|
||||
"height",
|
||||
"min-height",
|
||||
"max-height",
|
||||
"padding",
|
||||
"padding-top",
|
||||
"padding-right",
|
||||
"padding-bottom",
|
||||
"padding-left",
|
||||
"margin",
|
||||
"margin-top",
|
||||
"margin-right",
|
||||
"margin-bottom",
|
||||
"margin-left",
|
||||
"overflow",
|
||||
"overflow-x",
|
||||
"overflow-y",
|
||||
"-webkit-overflow-scrolling",
|
||||
"-ms-overflow-x",
|
||||
"-ms-overflow-y",
|
||||
"-ms-overflow-style",
|
||||
"columns",
|
||||
"column-count",
|
||||
"column-fill",
|
||||
"column-gap",
|
||||
"column-rule",
|
||||
"column-rule-width",
|
||||
"column-rule-style",
|
||||
"column-rule-color",
|
||||
"column-span",
|
||||
"column-width",
|
||||
"orphans",
|
||||
"widows",
|
||||
"clip",
|
||||
"clear",
|
||||
"font",
|
||||
"font-family",
|
||||
"font-size",
|
||||
"font-style",
|
||||
"font-weight",
|
||||
"font-variant",
|
||||
"font-size-adjust",
|
||||
"font-stretch",
|
||||
"font-effect",
|
||||
"font-emphasize",
|
||||
"font-emphasize-position",
|
||||
"font-emphasize-style",
|
||||
"font-smooth",
|
||||
"src",
|
||||
"hyphens",
|
||||
"line-height",
|
||||
"color",
|
||||
"text-align",
|
||||
"text-align-last",
|
||||
"text-emphasis",
|
||||
"text-emphasis-color",
|
||||
"text-emphasis-style",
|
||||
"text-emphasis-position",
|
||||
"text-decoration",
|
||||
"text-indent",
|
||||
"text-justify",
|
||||
"text-outline",
|
||||
"-ms-text-overflow",
|
||||
"text-overflow",
|
||||
"text-overflow-ellipsis",
|
||||
"text-overflow-mode",
|
||||
"text-shadow",
|
||||
"text-transform",
|
||||
"text-wrap",
|
||||
"-webkit-text-size-adjust",
|
||||
"-ms-text-size-adjust",
|
||||
"letter-spacing",
|
||||
"-ms-word-break",
|
||||
"word-break",
|
||||
"word-spacing",
|
||||
"-ms-word-wrap",
|
||||
"word-wrap",
|
||||
"overflow-wrap",
|
||||
"tab-size",
|
||||
"white-space",
|
||||
"vertical-align",
|
||||
"direction",
|
||||
"unicode-bidi",
|
||||
"list-style",
|
||||
"list-style-position",
|
||||
"list-style-type",
|
||||
"list-style-image",
|
||||
"pointer-events",
|
||||
"-ms-touch-action",
|
||||
"touch-action",
|
||||
"cursor",
|
||||
"visibility",
|
||||
"zoom",
|
||||
"table-layout",
|
||||
"empty-cells",
|
||||
"caption-side",
|
||||
"border-spacing",
|
||||
"border-collapse",
|
||||
"content",
|
||||
"quotes",
|
||||
"counter-reset",
|
||||
"counter-increment",
|
||||
"resize",
|
||||
"user-select",
|
||||
"nav-index",
|
||||
"nav-up",
|
||||
"nav-right",
|
||||
"nav-down",
|
||||
"nav-left",
|
||||
"background",
|
||||
"background-color",
|
||||
"background-image",
|
||||
"filter",
|
||||
"background-repeat",
|
||||
"background-attachment",
|
||||
"background-position",
|
||||
"background-position-x",
|
||||
"background-position-y",
|
||||
"background-clip",
|
||||
"background-origin",
|
||||
"background-size",
|
||||
"border",
|
||||
"border-color",
|
||||
"border-style",
|
||||
"border-width",
|
||||
"border-top",
|
||||
"border-top-color",
|
||||
"border-top-style",
|
||||
"border-top-width",
|
||||
"border-right",
|
||||
"border-right-color",
|
||||
"border-right-style",
|
||||
"border-right-width",
|
||||
"border-bottom",
|
||||
"border-bottom-color",
|
||||
"border-bottom-style",
|
||||
"border-bottom-width",
|
||||
"border-left",
|
||||
"border-left-color",
|
||||
"border-left-style",
|
||||
"border-left-width",
|
||||
"border-radius",
|
||||
"border-top-left-radius",
|
||||
"border-top-right-radius",
|
||||
"border-bottom-right-radius",
|
||||
"border-bottom-left-radius",
|
||||
"border-image",
|
||||
"border-image-source",
|
||||
"border-image-slice",
|
||||
"border-image-width",
|
||||
"border-image-outset",
|
||||
"border-image-repeat",
|
||||
"outline",
|
||||
"outline-width",
|
||||
"outline-style",
|
||||
"outline-color",
|
||||
"outline-offset",
|
||||
"box-shadow",
|
||||
"opacity",
|
||||
"-ms-interpolation-mode",
|
||||
"page-break-after",
|
||||
"page-break-before",
|
||||
"page-break-inside",
|
||||
"transition",
|
||||
"transition-delay",
|
||||
"transition-timing-function",
|
||||
"transition-duration",
|
||||
"transition-property",
|
||||
"transform",
|
||||
"transform-origin",
|
||||
"perspective",
|
||||
"appearance",
|
||||
"animation",
|
||||
"animation-name",
|
||||
"animation-duration",
|
||||
"animation-play-state",
|
||||
"animation-timing-function",
|
||||
"animation-delay",
|
||||
"animation-iteration-count",
|
||||
"animation-direction",
|
||||
"animation-fill-mode",
|
||||
"quotes",
|
||||
"will-change",
|
||||
"fill",
|
||||
"fill-rule",
|
||||
"stroke"
|
||||
]
|
||||
}
|
||||
}
|
||||
@ -1,132 +0,0 @@
|
||||
# Contributing to Binario
|
||||
|
||||
**Binario** welcomes contributions and corrections. Before contributing, please make sure you have read the guidelines
|
||||
below. If you're a newcomer to open source and you haven't contributed to other projects or used
|
||||
[Git](https://git-scm.com/) before, you should make yourself familiar before proceeding.
|
||||
|
||||
## Issues
|
||||
|
||||
The [issue tracker](https://github.com/vimux/binario/issues) is the preferred channel for bug reports and features
|
||||
requests, but please respect the following restrictions:
|
||||
|
||||
### General requirements
|
||||
|
||||
* Issue must be written in English.
|
||||
* Please **do not** combine a few problems or feature requests in one issue. Create separate issues if needed.
|
||||
* Please **do not** create an issue that contains only title. Write a clear title and useful description.
|
||||
* Please **do not** use the issue tracker for personal support requests.
|
||||
* Please **do not** post comments consisting solely of "+1" or emoji. The project maintainer reserve the right to delete
|
||||
such comments. Use
|
||||
[GitHub's reactions feature](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) instead.
|
||||
* Search first before filing a new issue. Please check existing open or recently closed issues to make sure somebody
|
||||
else hasn't already reported the issue.
|
||||
|
||||
### Reporting bugs
|
||||
|
||||
When creating a new bug issue make sure to include the following information:
|
||||
|
||||
* Your environment e.g. OS version, Hugo version, theme is up to date? Anything unusual about your environment or
|
||||
deployment.
|
||||
* Specify the exact steps to reproduce the bug in as many details as possible with code examples. Include links to files
|
||||
or demo projects, or copy/pasteable snippets, which you use in those examples.
|
||||
* Any message or error you get from Hugo, if you do.
|
||||
* A screenshot of any visual bug.
|
||||
|
||||
Please, take in consideration the next template to report your bug:
|
||||
|
||||
> **Hugo version**\
|
||||
> _Run `hugo version` and paste output here._
|
||||
>
|
||||
> **Theme is up to date?**\
|
||||
> _No | Yes_
|
||||
>
|
||||
> **Expected behavior**\
|
||||
> _A short and expressive description of what behavior you're expecting._
|
||||
>
|
||||
> **Current behavior**\
|
||||
> _A short sentence explaining what's actually happening, possibly containing screenshots._
|
||||
>
|
||||
> **Steps to reproduce / Code to reproduce**\
|
||||
> _A step by step description of how to trigger this bug. / Provide link to a demo project which reproduces this bug._
|
||||
>
|
||||
> **Additional info**\
|
||||
> _Anything unusual about your environment or deployment process? Anything else do we need to know? Optional._
|
||||
|
||||
**Note:** If you find a **Closed** issue that seems like it is the same bug that you're experiencing, open a new issue
|
||||
and include a link to the original issue in the body of your new one.
|
||||
|
||||
### Proposing features
|
||||
|
||||
* Explain the proposed feature, what it should do, why it is useful, and alternatives considered if possible. Please
|
||||
note that the project maintainer may close this issue or ask you to create a Pull Request if this is not something that
|
||||
the project maintainer sees as a sufficiently high priority.
|
||||
|
||||
Following these guidelines helps maintainer and the community understand your suggestion and find related suggestions.
|
||||
|
||||
## Pull Requests (PR)
|
||||
|
||||
**Please ask first** before embarking on any significant pull request (e.g. implementing features or refactoring code),
|
||||
otherwise, you risk spending a lot of time working on something that the project maintainer might not want to merge into
|
||||
the project.
|
||||
|
||||
Please respect our Pull Request Acceptance Criteria. For larger changes, you will likely receive multiple rounds of
|
||||
comments and it may take some time to complete.
|
||||
|
||||
### Pull Request Acceptance Criteria
|
||||
|
||||
* Keep the change in a single PR as small as possible
|
||||
* 1 PR = 1 FIX or FEATURE (do not combine things, send separate PR if needed)
|
||||
* PR with irrelevant changes won't be merged. If you do want to fix formatting or style, do that in a separate PR
|
||||
* Use a clear and descriptive branch name (e.g. **NOT** "patch-1" or "update")
|
||||
* Don't create a Pull Request from master branch
|
||||
* Provide a reasonable PR title and description
|
||||
* PR must be written in English
|
||||
* If the PR changes the UI it should include before-and-after screenshots or a link to a video
|
||||
* Keep PR up to date with upstream/master
|
||||
* Pay attention to any automated CI failures reported in the Pull Request
|
||||
* PR solves a common use case that several users will need in their real-life projects, not only your specific problems
|
||||
* Before you start something new or refactor something old, make sure you've read through the codebase and understand
|
||||
each part's purpose so that you don't break something
|
||||
* Always try to avoid breaking changes. But if they are needed, then mark each breaking commit with a
|
||||
"BREAKING CHANGE:" prefix in the commit title and a detailed explanation in the commit description of what happened and
|
||||
what the user needs to do
|
||||
* Deprecated params must be maintained for a 6-month transition period
|
||||
* If something mandates an unclear solution, leave a comment behind for the contributors that come after you
|
||||
* If you've added or modify SVG, ensure that each SVG file:
|
||||
* Be less than 2048 bytes
|
||||
* Be minified to a single line with no formatting
|
||||
* Not contain any JS or CSS section inside it
|
||||
* Not contain any additional transformations (matrix, translate, scale) or negative viewBox position values
|
||||
* Сompatible with [MIT License](LICENSE)
|
||||
* Maintain clean commit history and use meaningful commit messages. Pull Requests with messy commit history (with
|
||||
commit messages like "update", "another update", etc) are difficult to review and won't be merged, even if the changes
|
||||
are good enough
|
||||
* Be prepared to answer questions and make code changes. The project maintainer expect you to be reasonably responsive
|
||||
to those feedback, otherwise the PR will be closed after 2-4 weeks of inactivity
|
||||
|
||||
### Pull Request Contribution Prerequisites
|
||||
|
||||
* You have Node & npm installed
|
||||
* You have Hugo installed at v0.48.0+
|
||||
* You are familiar with Git
|
||||
|
||||
### Pull Request Process
|
||||
|
||||
1. Fork the repository
|
||||
1. Clone down the repository to your local system
|
||||
1. Run `npm i` in the repository root
|
||||
1. Create a new *dedicated branch* with descriptive name from `master`
|
||||
1. Make your change and commit to the new branch from the previous step
|
||||
1. Write a clear commit message
|
||||
1. If you've added code that need documentation, update the README.md
|
||||
1. Make sure your code lints (`npm test`)
|
||||
1. Push to your fork
|
||||
1. Submit a Pull Request (PR) to the upstream
|
||||
|
||||
---
|
||||
|
||||
**⚠️ IMPORTANT: No guarantees can be made that your pull request will be accepted.**
|
||||
|
||||
## License
|
||||
|
||||
By contributing to Binario, you agree that your contributions will be licensed under [MIT License](LICENSE).
|
||||
@ -1,20 +0,0 @@
|
||||
The MIT License (MIT)
|
||||
|
||||
Copyright (c) 2018 Vimux
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a copy of
|
||||
this software and associated documentation files (the "Software"), to deal in
|
||||
the Software without restriction, including without limitation the rights to
|
||||
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
|
||||
the Software, and to permit persons to whom the Software is furnished to do so,
|
||||
subject to the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be included in all
|
||||
copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
|
||||
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
|
||||
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
|
||||
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
|
||||
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
||||
@ -1,463 +0,0 @@
|
||||
# Binario
|
||||
|
||||
**Binario** is a responsive card-based & code-light Hugo theme.
|
||||
|
||||
**[Demo](https://binario.netlify.app/)**
|
||||
|
||||
|
||||
|
||||
**Features:**
|
||||
|
||||
* Responsive
|
||||
* Card-based list layout
|
||||
* Color themes
|
||||
* Internal Hugo templates (Open Graph, Schema, Twitter Cards, Google Analytics, Disqus comments)
|
||||
* Table of contents
|
||||
* Related content
|
||||
* MathJax
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [Installation](#installation)
|
||||
- [Option A. Git clone](#option-a-git-clone)
|
||||
- [Option B. Git submodule](#option-b-git-submodule)
|
||||
- [Option C. Download ZIP and manual install](#option-c-download-zip-and-manual-install)
|
||||
- [Configuration](#configuration)
|
||||
- [Config.toml example](#configtoml-example)
|
||||
- [Front Matter example](#front-matter-example)
|
||||
- [Configuration options](#configuration-options)
|
||||
- [Columns](#columns)
|
||||
- [Custom CSS](#custom-css)
|
||||
- [Custom JS](#custom-js)
|
||||
- [Entry Meta](#entry-meta)
|
||||
- [Related Content](#related-content)
|
||||
- [Share Buttons](#share-buttons)
|
||||
- [Featured Image](#featured-image)
|
||||
- [Breadcrumb](#breadcrumb)
|
||||
- [Footer Social Icons](#footer-social-icons)
|
||||
- [Web App Manifest](#web-app-manifest)
|
||||
- [Contributing](#contributing)
|
||||
- [License](#license)
|
||||
|
||||
## Installation
|
||||
|
||||
*First of all, you will need to [install Hugo](https://gohugo.io/getting-started/quick-start/#step-1-install-hugo) and
|
||||
[create a new site](https://gohugo.io/getting-started/quick-start/#step-2-create-a-new-site). Also, you have git
|
||||
installed on your machine and you are familiar with basic git usage. After that, you ready to install **Binario**.*
|
||||
|
||||
There are three different ways you can install **Binario**. Choose one of the installation methods listed below and
|
||||
follow the instructions.
|
||||
|
||||
- **A**. [Git clone](#option-a-git-clone)
|
||||
- **B**. [Git submodule](#option-b-git-submodule)
|
||||
- **C**. [Download ZIP and manual install](#option-c-download-zip-and-manual-install)
|
||||
|
||||
*For more information read the "[Install and Use Themes](https://gohugo.io/themes/installing-and-using-themes/)"*.
|
||||
|
||||
### Option A. Git clone
|
||||
|
||||
In your Hugo site directory, run:
|
||||
|
||||
```
|
||||
git clone https://github.com/vimux/binario themes/binario
|
||||
```
|
||||
|
||||
Next, edit your `config.toml` configuration file and add parameter:
|
||||
|
||||
```toml
|
||||
theme = "binario"
|
||||
```
|
||||
|
||||
### Option B. Git submodule
|
||||
|
||||
In your Hugo site directory, run:
|
||||
|
||||
```
|
||||
git submodule add https://github.com/vimux/binario themes/binario
|
||||
```
|
||||
|
||||
Next, edit your `config.toml` configuration file and add parameter:
|
||||
|
||||
```toml
|
||||
theme = "binario"
|
||||
```
|
||||
|
||||
*You can [read the GitHub documentation for submodules](https://github.com/blog/2104-working-with-submodules) or those
|
||||
found on [Git's website](https://git-scm.com/book/en/v2/Git-Tools-Submodules) for more information*
|
||||
|
||||
### Option C. Download ZIP and manual install
|
||||
|
||||
**[Download ZIP](https://github.com/vimux/binario/archive/master.zip)** and extract to the `themes/binario` within your
|
||||
Hugo website.
|
||||
|
||||
Next, edit your `config.toml` configuration file and add parameter:
|
||||
|
||||
```toml
|
||||
theme = "binario"
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
You can run your site in Hugo server mode:
|
||||
|
||||
```
|
||||
hugo server
|
||||
```
|
||||
|
||||
Now you can go to [localhost:1313](http://localhost:1313) webpage and the Binario theme should be visible.
|
||||
|
||||
After you make sure that **Binario** works, you may start customizing the theme if it's needed. You can change
|
||||
[number of columns](#columns), activate [footer social icons](#footer-social-icons), [share buttons](#share-buttons) and
|
||||
[much more](#configuration-options).
|
||||
|
||||
## Configuration
|
||||
|
||||
Hugo uses the `config.toml`, `config.yaml`, or `config.json` (if found in the site root) as the default site config
|
||||
file. Here is Binario configuration example in TOML with all available theme-specific config params:
|
||||
|
||||
### Config.toml example
|
||||
|
||||
```toml
|
||||
baseurl = "/"
|
||||
title = "Binario"
|
||||
languageCode = "en-us"
|
||||
paginate = "10" # Number of elements per page in pagination
|
||||
theme = "binario"
|
||||
disqusShortname = "" # DEPRECATED! Use .Services.Disqus.Shortname
|
||||
googleAnalytics = "" # DEPRECATED! Use .Services.googleAnalytics.ID
|
||||
|
||||
[services.disqus]
|
||||
shortname = "" # Enable Disqus by entering your Disqus shortname
|
||||
[services.googleAnalytics]
|
||||
ID = "" # Enable Google Analytics by entering your tracking ID
|
||||
|
||||
[Author] # Used in authorbox
|
||||
name = "John Doe"
|
||||
bio = "John Doe's true identity is unknown. Maybe he is a successful blogger or writer."
|
||||
avatar = "img/avatar.png"
|
||||
|
||||
[Params]
|
||||
description = "Responsive card-based & code-light Hugo theme" # Site Description. Used in meta description
|
||||
copyright = "Binario" # Copyright holder, otherwise will use .Site.Title
|
||||
opengraph = true # Enable OpenGraph if true
|
||||
schema = true # Enable Schema
|
||||
twitter_cards = true # Enable Twitter Cards if true
|
||||
columns = 2 # Set the number of cards columns. Possible values: 1, 2, 3
|
||||
mainSections = ["post"] # Set main page sections
|
||||
dateFormat = "January 02, 2006" # Change the format of dates
|
||||
colorTheme = "" # dark-green, dark-blue, dark-red, dark-violet
|
||||
customCSS = ["css/custom.css"] # Include custom CSS files
|
||||
customJS = ["js/custom.js"] # Include custom JS files
|
||||
mainMenuAlignment = "right" # Align main menu (desktop version) to the right side
|
||||
authorbox = true # Show authorbox at bottom of single pages if true
|
||||
comments = true # Enable comments for all site pages
|
||||
related = true # Enable Related content for single pages
|
||||
relatedMax = 5 # Set the maximum number of elements that can be displayed in related block. Optional
|
||||
mathjax = true # Enable MathJax for all site pages
|
||||
mathjaxPath = "https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.6/MathJax.js" # Specify MathJax path. Optional
|
||||
mathjaxConfig = "TeX-AMS-MML_HTMLorMML" # Specify MathJax config. Optional
|
||||
hideNoPostsWarning = false # Don't show no posts empty state warning in main page, if true
|
||||
|
||||
[Params.Entry]
|
||||
meta = ["date", "categories", "tags"] # Enable meta fields in given order
|
||||
toc = true # Enable Table of Contents
|
||||
tocOpen = true # Open Table of Contents block. Optional
|
||||
|
||||
[Params.Featured]
|
||||
previewOnly = false # Show only preview featured image
|
||||
|
||||
[Params.Breadcrumb]
|
||||
enable = true # Enable breadcrumb block globally
|
||||
homeText = "Binario" # Home node text
|
||||
|
||||
[Params.Social]
|
||||
email = "example@example.com"
|
||||
facebook = "username"
|
||||
twitter = "username"
|
||||
telegram = "username"
|
||||
instagram = "username"
|
||||
pinterest = "username"
|
||||
vk = "username"
|
||||
linkedin = "username"
|
||||
github = "username"
|
||||
gitlab = "username"
|
||||
stackoverflow = "numberid"
|
||||
mastodon = "https://some.instance/@username"
|
||||
medium = "username"
|
||||
|
||||
[Params.Share] # Entry Share block
|
||||
facebook = true
|
||||
twitter = true
|
||||
reddit = true
|
||||
telegram = true
|
||||
linkedin = true
|
||||
vk = true
|
||||
pocket = true
|
||||
pinterest = true
|
||||
|
||||
# Web App Manifest settings
|
||||
# https://www.w3.org/TR/appmanifest/
|
||||
# https://developers.google.com/web/fundamentals/web-app-manifest/
|
||||
[Params.Manifest]
|
||||
name = "Binario"
|
||||
shortName = "Binario"
|
||||
display = "browser"
|
||||
startUrl = "/"
|
||||
backgroundColor = "#2a2a2a"
|
||||
themeColor = "#1b1b1b"
|
||||
description = "Responsive card-based & code-light Hugo theme"
|
||||
orientation = "portrait"
|
||||
scope = "/"
|
||||
|
||||
[outputFormats]
|
||||
[outputFormats.MANIFEST]
|
||||
mediaType = "application/json"
|
||||
baseName = "manifest"
|
||||
isPlainText = true
|
||||
notAlternative = true
|
||||
|
||||
[outputs]
|
||||
home = ["HTML", "RSS", "MANIFEST"]
|
||||
```
|
||||
|
||||
For more information about Hugo configuration files and all common configuration settings, please read
|
||||
"[Configure Hugo](https://gohugo.io/getting-started/configuration)" from Hugo official documentation.
|
||||
|
||||
### Front Matter example
|
||||
|
||||
Hugo supports three formats for front matter: `yaml`, `toml` and `json`. Here is Front Matter example in YAML:
|
||||
|
||||
```yaml
|
||||
---
|
||||
# Common-Defined params
|
||||
title: "Example article title"
|
||||
date: "2017-08-21"
|
||||
lastmod: "2018-12-21"
|
||||
description: "Example article description"
|
||||
categories:
|
||||
- "Category 1"
|
||||
- "Category 2"
|
||||
tags:
|
||||
- "Tag"
|
||||
- "Another tag"
|
||||
menu: main # Add page to a menu. Options: main, footer
|
||||
|
||||
# Theme-Defined params
|
||||
comments: true # Enable/disable Disqus comments for specific page
|
||||
authorbox: true # Enable/disable Authorbox for specific page
|
||||
toc: true # Enable/disable Table of Contents for specific page
|
||||
tocOpen: true # Open Table of Contents block for specific page
|
||||
mathjax: true # Enable/disable MathJax for specific page
|
||||
related: true # Enable/disable Related content for specific page
|
||||
meta:
|
||||
- date
|
||||
- categories
|
||||
- tags
|
||||
featured:
|
||||
url: image.jpg # relative path of the image
|
||||
alt: A scale model of the Eiffel tower # alternate text for the image
|
||||
caption: Eiffel tower model # image caption
|
||||
credit: Unknown author # image credit
|
||||
previewOnly: false # show only preview image (true/false)
|
||||
---
|
||||
```
|
||||
|
||||
For more information about front matter variables and formats read
|
||||
"[Hugo Front Matter](https://gohugo.io/content-management/front-matter)" from Hugo official documentation.
|
||||
|
||||
### Configuration options
|
||||
|
||||
Binario includes some customizable configuration options that may be useful.
|
||||
|
||||
#### Columns
|
||||
|
||||
By default, Binario works with two columns card layout (if it possible by screen size) for list pages, but you can also
|
||||
use one or three columns layout. Change `Params.columns`to preferable value (from 1 to 3). You can also change this
|
||||
option for specific list pages in frontmatter params.
|
||||
|
||||
#### Custom CSS
|
||||
|
||||
If you want to include custom CSS files, you need to assign an array of references in site config file
|
||||
(`config.toml` by default) like following:
|
||||
|
||||
```toml
|
||||
[Params]
|
||||
customCSS = ["css/custom.css"]
|
||||
```
|
||||
|
||||
Of course, you can reference as many CSS files as you want. Their paths need to be relative to the `static` folder of
|
||||
your Hugo site:
|
||||
|
||||
```toml
|
||||
[Params]
|
||||
customCSS = ["css/custom.css", "css/another.css"]
|
||||
```
|
||||
|
||||
All custom CSS files will be added in the `head` section of a `baseof.html` right after the built-in CSS file.
|
||||
|
||||
#### Custom JS
|
||||
|
||||
You can add custom JavaScript files by assigning an array of references in site config file (`config.toml` by default)
|
||||
like following:
|
||||
|
||||
```toml
|
||||
[Params]
|
||||
customJS = ["js/custom.js"]
|
||||
```
|
||||
|
||||
And of course, just like with custom CSS, you can reference as many JS files as you want. Their paths need to be
|
||||
relative to the `static` folder of your Hugo site:
|
||||
|
||||
```toml
|
||||
[Params]
|
||||
customJS = ["js/custom.js", "js/another.js"]
|
||||
```
|
||||
|
||||
All custom JS files will be added before closing body tag of a `baseof.html` file.
|
||||
|
||||
#### Entry Meta
|
||||
|
||||
Entry metadata are relevant information about your entry such as published date, last modified date, category, etc. You
|
||||
may activate meta fields with `meta` parameter under the `[Params.Entry]` config section:
|
||||
|
||||
```toml
|
||||
[Params.Entry]
|
||||
meta = ["date", "categories", "tags"]
|
||||
```
|
||||
|
||||
#### Related Content
|
||||
|
||||
Binario uses default Related Content Hugo feature to provide "See Also"-like section. You can activate "Related Content"
|
||||
section with `.Site.Params.related` parameter.
|
||||
|
||||
More information available at [Hugo Related Content](https://gohugo.io/content-management/front-matter)
|
||||
|
||||
#### Share Buttons
|
||||
|
||||
To display share buttons, set up `[Params.Share]` specific parameters in your site config file.
|
||||
|
||||
Available share buttons: Facebook, Twitter, Reddit, Telegram, LinkedIn, VK, Pocket, Pinterest
|
||||
|
||||
#### Featured Image
|
||||
|
||||
There are two main different ways to add a featured image for a page.
|
||||
|
||||
**Option 1.** Put `featured.*` or `thumbnail.*` image file in the
|
||||
[page bundle](https://gohugo.io/content-management/page-bundles/).
|
||||
|
||||
**Option 2.** Put any image in the page bundle & specify `featured` param in the page's front matter.
|
||||
|
||||
You may put any image in the page bundle and specify `featured` param in the page's front matter:
|
||||
|
||||
```yaml
|
||||
featured: image.jpg
|
||||
```
|
||||
|
||||
Or you can add some additional params like `alt`, `caption`, `credit` and `previewOnly`:
|
||||
|
||||
```yaml
|
||||
featured:
|
||||
url: image.jpg
|
||||
alt: A scale model of the Eiffel tower standing on a map
|
||||
caption: Eiffel tower model
|
||||
credit: Unknown author
|
||||
previewOnly: false
|
||||
```
|
||||
|
||||
**Note**: `caption` and `credit` appear only on single pages, not summaries.
|
||||
|
||||
#### Breadcrumb
|
||||
|
||||
Breadcrumb navigation is a hierarchical navigation menu presented as a trail of links. The main purpose of breadcrumb is
|
||||
to help users navigate in the site hierarchy.
|
||||
|
||||
For enabling breadcrumb partial globally (for all single and list pages), use `enable` param under the
|
||||
`[Params.Breadcrumb]` section of your config.toml file:
|
||||
|
||||
```toml
|
||||
[Params.Breadcrumb]
|
||||
enable = true
|
||||
```
|
||||
|
||||
The global `.Site.Params.Breadcrumb.enable` param can be overridden for specific pages with `breadcrumb` front matter
|
||||
param:
|
||||
|
||||
```yaml
|
||||
breadcrumb: false
|
||||
```
|
||||
|
||||
#### Footer Social Icons
|
||||
|
||||
With Binario, you have the option to display social icons in the footer. To display them, set up `[Params.Social]`
|
||||
specific parameters in your site config file.
|
||||
|
||||
Available social services: Email, Facebook, Twitter, Telegram, Instagram, Pinterest, VK, LinkedIn, GitHub, GitLab,
|
||||
Stack Overflow, Mastodon, Medium
|
||||
|
||||
#### Web App Manifest
|
||||
|
||||
[Web App Manifest](https://developers.google.com/web/fundamentals/web-app-manifest/) is a simple json file with basic
|
||||
site info like name, description, icons, etc. This file tells the browser about your web application and how it should
|
||||
behave when "installed" (as PWA) on the users mobile device or desktop.
|
||||
|
||||
To activate Web App Manifest, define `MANIFEST` as custom output format and include this for `home` Kind attribute in
|
||||
your site config file. Here's how to make it.
|
||||
|
||||
First of all, you should define `MANIFEST` custom output format [`config.toml`]:
|
||||
|
||||
```toml
|
||||
[outputFormats]
|
||||
[outputFormats.MANIFEST]
|
||||
mediaType = "application/json"
|
||||
baseName = "manifest"
|
||||
isPlainText = true
|
||||
notAlternative = true
|
||||
```
|
||||
|
||||
Then, include `MANIFEST` output format for `home` Kind attribute [`config.toml`]:
|
||||
|
||||
```toml
|
||||
[outputs]
|
||||
home = ["HTML", "RSS", "MANIFEST"]
|
||||
```
|
||||
|
||||
After that, Web App Manifest file will be generated. Still, it's better to specify `[Params.Manifest]` params to make
|
||||
sure that everything works as expected.
|
||||
|
||||
| Web App Manifest Property | `.Site.Params.Manifest` Key | Default Value | Type |
|
||||
| ------------------------- | --------------------------- | ------------- | ----------- |
|
||||
| name | name | `.Site.Title` | required |
|
||||
| short_name | shortName | `.Site.Title` | required |
|
||||
| display | display | `browser` | required |
|
||||
| start_url | startUrl | `/` | required |
|
||||
| background_color | backgroundColor | `#2a2a2a` | recommended |
|
||||
| theme_color | themeColor | `#1b1b1b` | recommended |
|
||||
| description | description | | recommended |
|
||||
| orientation | orientation | | recommended |
|
||||
| scope | scope | | recommended |
|
||||
| icons\* | | | required |
|
||||
|
||||
\* You can't customize manifest icons through config params, only replacing `icons/192.png` and `icons/512.png` files.
|
||||
|
||||
---
|
||||
|
||||
*To verify that your manifest file is configured properly and works well, run Hugo server and open
|
||||
Chrome DevTools (Press F12 in Chrome) → Application → Manifest*
|
||||
|
||||
*If you use Apache as a web server, you may have difficulty accessing files in the icons folder within your root dir.
|
||||
Check [Issue #4](https://github.com/Vimux/Binario/issues/4) for more information.*
|
||||
|
||||
## Contributing
|
||||
|
||||
Have a bug? [Please open a new issue](https://github.com/vimux/binario/issues/new).
|
||||
|
||||
Pull requests are very welcome too, but please make sure they match the existing
|
||||
[contributing guide](https://github.com/vimux/binario/blob/master/CONTRIBUTING.md).
|
||||
|
||||
## License
|
||||
|
||||
Binario is licensed under the [MIT License](https://github.com/vimux/binario/blob/master/LICENSE).
|
||||
|
||||
* Social media icons based on [SuperTinyIcons](https://github.com/edent/SuperTinyIcons) [MIT]
|
||||
* CSS Reset based on [Bootstrap Reboot](https://github.com/twbs/bootstrap/blob/v4-dev/dist/css/bootstrap-reboot.css)
|
||||
[MIT]
|
||||
@ -1,9 +0,0 @@
|
||||
baseURL = "https://example.com/"
|
||||
title = "Binario"
|
||||
languageCode = "en-us"
|
||||
paginate = 10
|
||||
theme = "binario"
|
||||
|
||||
[Params]
|
||||
description = "Responsive card-based & code-light Hugo theme"
|
||||
columns = 2
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
title: About Hugo
|
||||
description: Hugo, the world’s fastest framework for building websites
|
||||
date: 2019-02-28
|
||||
author: Hugo Authors
|
||||
menu: main
|
||||
---
|
||||
|
||||
Written in Go, Hugo is an open source static site generator available under the [Apache Licence 2.0.](https://github.com/gohugoio/hugo/blob/master/LICENSE) Hugo supports TOML, YAML and JSON data file types, Markdown and HTML content files and uses shortcodes to add rich content. Other notable features are taxonomies, multilingual mode, image processing, custom output formats, HTML/CSS/JS minification and support for Sass SCSS workflows.
|
||||
|
||||
Hugo makes use of a variety of open source projects including:
|
||||
|
||||
* https://github.com/russross/blackfriday
|
||||
* https://github.com/alecthomas/chroma
|
||||
* https://github.com/muesli/smartcrop
|
||||
* https://github.com/spf13/cobra
|
||||
* https://github.com/spf13/viper
|
||||
|
||||
Hugo is ideal for blogs, corporate websites, creative portfolios, online magazines, single page applications or even a website with thousands of pages.
|
||||
|
||||
Hugo is for people who want to hand code their own website without worrying about setting up complicated runtimes, dependencies and databases.
|
||||
|
||||
Websites built with Hugo are extremelly fast, secure and can be deployed anywhere including, AWS, GitHub Pages, Heroku, Netlify and any other hosting provider.
|
||||
|
||||
Learn more and contribute on [GitHub](https://github.com/gohugoio).
|
||||
@ -1,168 +0,0 @@
|
||||
---
|
||||
title: Basic HTML Elements
|
||||
description: Example test article that contains basic HTML elements for text formatting on the Web.
|
||||
date: 2019-09-24
|
||||
categories:
|
||||
- "Development"
|
||||
tags:
|
||||
- "HTML"
|
||||
- "CSS"
|
||||
- "Basic Elements"
|
||||
---
|
||||
|
||||
The main purpose of this article is to make sure that all basic HTML Elements are decorated with CSS so as to not miss any possible elements when creating new themes for Hugo.
|
||||
<!--more-->
|
||||
|
||||
## Headings
|
||||
|
||||
Let's start with all possible headings. The HTML `<h1>`—`<h6>` elements represent six levels of section headings. `<h1>` is the highest section level and `<h6>` is the lowest.
|
||||
|
||||
# Heading 1
|
||||
## Heading 2
|
||||
### Heading 3
|
||||
#### Heading 4
|
||||
##### Heading 5
|
||||
###### Heading 6
|
||||
|
||||
***
|
||||
|
||||
## Paragraph
|
||||
|
||||
According to the [HTML5 specification](https://www.w3.org/TR/html5/dom.html#elements) by [W3C](https://www.w3.org/), **HTML documents consist of a tree of elements and text**. Each element is denoted in the source by a [start tag](https://www.w3.org/TR/html5/syntax.html#syntax-start-tags), such as `<body>`, and an [end tag](https://www.w3.org/TR/html5/syntax.html#syntax-end-tags), such as `</body>`. (*Certain start tags and end tags can in certain cases be omitted and are implied by other tags.*)
|
||||
|
||||
Elements can have attributes, which control how the elements work. For example, hyperlink are formed using the `a` element and its `href` attribute.
|
||||
|
||||
## List Types
|
||||
|
||||
### Ordered List
|
||||
|
||||
1. First item
|
||||
2. Second item
|
||||
3. Third item
|
||||
|
||||
### Unordered List
|
||||
|
||||
* List item
|
||||
* Another item
|
||||
* And another item
|
||||
|
||||
### Nested list
|
||||
|
||||
<ul>
|
||||
<li>First item</li>
|
||||
<li>Second item
|
||||
<ul>
|
||||
<li>Second item First subitem</li>
|
||||
<li>Second item second subitem
|
||||
<ul>
|
||||
<li>Second item Second subitem First sub-subitem</li>
|
||||
<li>Second item Second subitem Second sub-subitem</li>
|
||||
<li>Second item Second subitem Third sub-subitem</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Second item Third subitem
|
||||
<ol>
|
||||
<li>Second item Third subitem First sub-subitem</li>
|
||||
<li>Second item Third subitem Second sub-subitem</li>
|
||||
<li>Second item Third subitem Third sub-subitem</li>
|
||||
</ol>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Third item</li>
|
||||
</ul>
|
||||
|
||||
### Definition List
|
||||
|
||||
HTML also supports definition lists.
|
||||
|
||||
<dl>
|
||||
<dt>Blanco tequila</dt>
|
||||
<dd>The purest form of the blue agave spirit...</dd>
|
||||
<dt>Reposado tequila</dt>
|
||||
<dd>Typically aged in wooden barrels for between two and eleven months...</dd>
|
||||
</dl>
|
||||
|
||||
## 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.
|
||||
|
||||
> Quoted text.
|
||||
> This line is part of the same quote.
|
||||
> Also you can *put* **Markdown** into a blockquote.
|
||||
|
||||
Blockquote with a citation.
|
||||
|
||||
<blockquote>
|
||||
<p>My goal wasn't to make a ton of money. It was to build good computers. I only started the company when I realized I could be an engineer forever.</p>
|
||||
<footer>— <cite>Steve Wozniak</cite></footer>
|
||||
</blockquote>
|
||||
|
||||
According to Mozilla's website, <q cite="https://www.mozilla.org/en-US/about/history/details/">Firefox 1.0 was released in 2004 and became a big success.</q>
|
||||
|
||||
## Tables
|
||||
|
||||
Tables aren't part of the core Markdown spec, but Hugo supports them.
|
||||
|
||||
| ID | Make | Model | Year |
|
||||
| --- | --------- | ------- | ---- |
|
||||
| 1 | Honda | Accord | 2009 |
|
||||
| 2 | Toyota | Camry | 2012 |
|
||||
| 3 | Hyundai | Elantra | 2010 |
|
||||
|
||||
Colons can be used to align columns.
|
||||
|
||||
| Tables | Are | Cool |
|
||||
|:----------- |:-------------:| ------------:|
|
||||
| align: left | align: center | align: right |
|
||||
| align: left | align: center | align: right |
|
||||
| align: left | align: center | align: right |
|
||||
|
||||
You can also use inline Markdown.
|
||||
|
||||
| Inline | Markdown | In | Table |
|
||||
| ---------- | --------- | ----------------- | ---------- |
|
||||
| *italics* | **bold** | ~~strikethrough~~ | `code` |
|
||||
|
||||
## Code
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>Example HTML5 Document</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>Test</p>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
|
||||
## Highlighted Code
|
||||
|
||||
{{< highlight html >}}
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>Example HTML5 Document</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>Test</p>
|
||||
</body>
|
||||
</html>
|
||||
{{< /highlight >}}
|
||||
|
||||
## Other stuff — abbr, sub, sup, kbd, etc.
|
||||
|
||||
<abbr title="Graphics Interchange Format">GIF</abbr> is a bitmap image format.
|
||||
|
||||
H<sub>2</sub>O
|
||||
|
||||
C<sub>6</sub>H<sub>12</sub>O<sub>6</sub>
|
||||
|
||||
X<sup>n</sup> + Y<sup>n</sup> = Z<sup>n</sup>
|
||||
|
||||
Press <kbd>X</kbd> to win. Or press <kbd><kbd>CTRL</kbd>+<kbd>ALT</kbd>+<kbd>F</kbd></kbd> to show FPS counter.
|
||||
|
||||
<mark>As a unit of information in information theory, the bit has alternatively been called a shannon</mark>, named after Claude Shannon, the founder of field of information theory.
|
||||
File diff suppressed because it is too large
Load Diff
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
@ -1,73 +0,0 @@
|
||||
---
|
||||
title: Featured Images
|
||||
description: "In this page, we will explain what featured images are and show you some examples how to add a featured \
|
||||
image for a page."
|
||||
date: 2019-09-12
|
||||
---
|
||||
|
||||
Featured image is the image that appears on summaries at the list pages and the top of content pages. Every content page
|
||||
in this theme can have a featured image.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## How to add a featured image
|
||||
|
||||
Content pages in Hugo can have their images or any other files stored under the same directory of the page itself.
|
||||
In Hugo's terms, it's called **page bundle** and allows us to keep all assets together with a page content file.
|
||||
|
||||
This theme uses [page bundles](https://gohugo.io/content-management/organization/#page-bundles) for featured images.
|
||||
There are two main different ways to add a featured image.
|
||||
|
||||
### Option 1. Put `featured.*` or `thumbnail.*` image in the page bundle
|
||||
|
||||
This theme considers `featured` or `thumbnail` image in any popular graphic format in the root of the page bundle as
|
||||
a featured image.
|
||||
|
||||
Directory structure of this page:
|
||||
|
||||
```
|
||||
content
|
||||
└── post
|
||||
└── featured-images // single page folder (page bundle)
|
||||
├── featured.png // featured image
|
||||
└── index.md // page content file
|
||||
```
|
||||
|
||||
### Option 2. Put any image in the page bundle & specify `featured` param
|
||||
|
||||
You may put any image in the page bundle and specify `featured` param in the page's front matter:
|
||||
|
||||
```yaml
|
||||
featured: image.jpg
|
||||
```
|
||||
|
||||
- `featured` [`String`]: relative path of the image
|
||||
|
||||
Or you can add some additional params like `alt`, `caption`, `credit` and `previewOnly`:
|
||||
|
||||
```yaml
|
||||
featured:
|
||||
url: image.jpg
|
||||
alt: A scale model of the Eiffel tower standing on a map
|
||||
caption: Eiffel tower model
|
||||
credit: Unknown author
|
||||
previewOnly: false
|
||||
```
|
||||
|
||||
- `featured` [`Map`]:
|
||||
- `url` [`String`]: relative path of the image
|
||||
- `alt` [`String`]: alternate text for the image
|
||||
- `caption` [`String`]: image caption
|
||||
- `credit` [`String`]: image credit
|
||||
- `previewOnly` [`Boolean`]: show only preview image
|
||||
|
||||
## FAQ
|
||||
|
||||
**Q**: _What will happen if I specify `alt`, `caption`, `credit` params, but miss `url`? Featured image will be shown or
|
||||
not?_\
|
||||
**A**: In that case, featured image would appear only if the page bundle contains `featured.*` or `thumbnail.*` image.
|
||||
Otherwise, you'll get nothing.
|
||||
|
||||
**Q**: _Is featured image path case sensitive or insensitive? Featured.png and featured.png are different image relative
|
||||
paths for Hugo?_\
|
||||
**A**: The image matching is case-insensitive. In that case, Featured.png and featured.png are identical for Hugo.
|
||||
@ -1,343 +0,0 @@
|
||||
---
|
||||
title: "(Hu)go Template Primer"
|
||||
date: 2014-04-02
|
||||
tags:
|
||||
- "go"
|
||||
- "golang"
|
||||
- "templates"
|
||||
- "themes"
|
||||
- "development"
|
||||
categories:
|
||||
- "Development"
|
||||
- "golang"
|
||||
menu: main
|
||||
---
|
||||
|
||||
Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
|
||||
its template engine. It is an extremely lightweight engine that provides a very
|
||||
small amount of logic. In our experience that it is just the right amount of
|
||||
logic to be able to create a good static website. If you have used other
|
||||
template systems from different languages or frameworks you will find a lot of
|
||||
similarities in Go templates.
|
||||
|
||||
<!--more-->
|
||||
|
||||
This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
|
||||
provide more details.
|
||||
|
||||
## Introduction to Go Templates
|
||||
|
||||
Go templates provide an extremely simple template language. It adheres to the
|
||||
belief that only the most basic of logic belongs in the template or view layer.
|
||||
One consequence of this simplicity is that Go templates parse very quickly.
|
||||
|
||||
A unique characteristic of Go templates is they are content aware. Variables and
|
||||
content will be sanitized depending on the context of where they are used. More
|
||||
details can be found in the [Go docs][gohtmltemplate].
|
||||
|
||||
## Basic Syntax
|
||||
|
||||
Golang templates are HTML files with the addition of variables and
|
||||
functions.
|
||||
|
||||
**Go variables and functions are accessible within {{ }}**
|
||||
|
||||
Accessing a predefined variable "foo":
|
||||
|
||||
{{ foo }}
|
||||
|
||||
**Parameters are separated using spaces**
|
||||
|
||||
Calling the add function with input of 1, 2:
|
||||
|
||||
{{ add 1 2 }}
|
||||
|
||||
**Methods and fields are accessed via dot notation**
|
||||
|
||||
Accessing the Page Parameter "bar"
|
||||
|
||||
{{ .Params.bar }}
|
||||
|
||||
**Parentheses can be used to group items together**
|
||||
|
||||
{{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
|
||||
|
||||
|
||||
## Variables
|
||||
|
||||
Each Go template has a struct (object) made available to it. In hugo each
|
||||
template is passed either a page or a node struct depending on which type of
|
||||
page you are rendering. More details are available on the
|
||||
[variables](/layout/variables) page.
|
||||
|
||||
A variable is accessed by referencing the variable name.
|
||||
|
||||
<title>{{ .Title }}</title>
|
||||
|
||||
Variables can also be defined and referenced.
|
||||
|
||||
{{ $address := "123 Main St."}}
|
||||
{{ $address }}
|
||||
|
||||
|
||||
## Functions
|
||||
|
||||
Go template ship with a few functions which provide basic functionality. The Go
|
||||
template system also provides a mechanism for applications to extend the
|
||||
available functions with their own. [Hugo template
|
||||
functions](/layout/functions) provide some additional functionality we believe
|
||||
are useful for building websites. Functions are called by using their name
|
||||
followed by the required parameters separated by spaces. Template
|
||||
functions cannot be added without recompiling hugo.
|
||||
|
||||
**Example:**
|
||||
|
||||
{{ add 1 2 }}
|
||||
|
||||
## Includes
|
||||
|
||||
When including another template you will pass to it the data it will be
|
||||
able to access. To pass along the current context please remember to
|
||||
include a trailing dot. The templates location will always be starting at
|
||||
the /layout/ directory within Hugo.
|
||||
|
||||
**Example:**
|
||||
|
||||
{{ template "chrome/header.html" . }}
|
||||
|
||||
|
||||
## Logic
|
||||
|
||||
Go templates provide the most basic iteration and conditional logic.
|
||||
|
||||
### Iteration
|
||||
|
||||
Just like in Go, the Go templates make heavy use of range to iterate over
|
||||
a map, array or slice. The following are different examples of how to use
|
||||
range.
|
||||
|
||||
**Example 1: Using Context**
|
||||
|
||||
{{ range array }}
|
||||
{{ . }}
|
||||
{{ end }}
|
||||
|
||||
**Example 2: Declaring value variable name**
|
||||
|
||||
{{range $element := array}}
|
||||
{{ $element }}
|
||||
{{ end }}
|
||||
|
||||
**Example 2: Declaring key and value variable name**
|
||||
|
||||
{{range $index, $element := array}}
|
||||
{{ $index }}
|
||||
{{ $element }}
|
||||
{{ end }}
|
||||
|
||||
### Conditionals
|
||||
|
||||
If, else, with, or, & and provide the framework for handling conditional
|
||||
logic in Go Templates. Like range, each statement is closed with `end`.
|
||||
|
||||
|
||||
Go Templates treat the following values as false:
|
||||
|
||||
* false
|
||||
* 0
|
||||
* any array, slice, map, or string of length zero
|
||||
|
||||
**Example 1: If**
|
||||
|
||||
{{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
|
||||
|
||||
**Example 2: If -> Else**
|
||||
|
||||
{{ if isset .Params "alt" }}
|
||||
{{ index .Params "alt" }}
|
||||
{{else}}
|
||||
{{ index .Params "caption" }}
|
||||
{{ end }}
|
||||
|
||||
**Example 3: And & Or**
|
||||
|
||||
{{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
|
||||
|
||||
**Example 4: With**
|
||||
|
||||
An alternative way of writing "if" and then referencing the same value
|
||||
is to use "with" instead. With rebinds the context `.` within its scope,
|
||||
and skips the block if the variable is absent.
|
||||
|
||||
The first example above could be simplified as:
|
||||
|
||||
{{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
|
||||
|
||||
**Example 5: If -> Else If**
|
||||
|
||||
{{ if isset .Params "alt" }}
|
||||
{{ index .Params "alt" }}
|
||||
{{ else if isset .Params "caption" }}
|
||||
{{ index .Params "caption" }}
|
||||
{{ end }}
|
||||
|
||||
## Pipes
|
||||
|
||||
One of the most powerful components of Go templates is the ability to
|
||||
stack actions one after another. This is done by using pipes. Borrowed
|
||||
from unix pipes, the concept is simple, each pipeline's output becomes the
|
||||
input of the following pipe.
|
||||
|
||||
Because of the very simple syntax of Go templates, the pipe is essential
|
||||
to being able to chain together function calls. One limitation of the
|
||||
pipes is that they only can work with a single value and that value
|
||||
becomes the last parameter of the next pipeline.
|
||||
|
||||
A few simple examples should help convey how to use the pipe.
|
||||
|
||||
**Example 1 :**
|
||||
|
||||
{{ if eq 1 1 }} Same {{ end }}
|
||||
|
||||
is the same as
|
||||
|
||||
{{ eq 1 1 | if }} Same {{ end }}
|
||||
|
||||
It does look odd to place the if at the end, but it does provide a good
|
||||
illustration of how to use the pipes.
|
||||
|
||||
**Example 2 :**
|
||||
|
||||
{{ index .Params "disqus_url" | html }}
|
||||
|
||||
Access the page parameter called "disqus_url" and escape the HTML.
|
||||
|
||||
**Example 3 :**
|
||||
|
||||
{{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
|
||||
Stuff Here
|
||||
{{ end }}
|
||||
|
||||
Could be rewritten as
|
||||
|
||||
{{ isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
|
||||
Stuff Here
|
||||
{{ end }}
|
||||
|
||||
|
||||
## Context (aka. the dot)
|
||||
|
||||
The most easily overlooked concept to understand about Go templates is that {{ . }}
|
||||
always refers to the current context. In the top level of your template this
|
||||
will be the data set made available to it. Inside of a iteration it will have
|
||||
the value of the current item. When inside of a loop the context has changed. .
|
||||
will no longer refer to the data available to the entire page. If you need to
|
||||
access this from within the loop you will likely want to set it to a variable
|
||||
instead of depending on the context.
|
||||
|
||||
**Example:**
|
||||
|
||||
{{ $title := .Site.Title }}
|
||||
{{ range .Params.tags }}
|
||||
<li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
|
||||
{{ end }}
|
||||
|
||||
Notice how once we have entered the loop the value of {{ . }} has changed. We
|
||||
have defined a variable outside of the loop so we have access to it from within
|
||||
the loop.
|
||||
|
||||
# Hugo Parameters
|
||||
|
||||
Hugo provides the option of passing values to the template language
|
||||
through the site configuration (for sitewide values), or through the meta
|
||||
data of each specific piece of content. You can define any values of any
|
||||
type (supported by your front matter/config format) and use them however
|
||||
you want to inside of your templates.
|
||||
|
||||
|
||||
## Using Content (page) Parameters
|
||||
|
||||
In each piece of content you can provide variables to be used by the
|
||||
templates. This happens in the [front matter](/content/front-matter).
|
||||
|
||||
An example of this is used in this documentation site. Most of the pages
|
||||
benefit from having the table of contents provided. Sometimes the TOC just
|
||||
doesn't make a lot of sense. We've defined a variable in our front matter
|
||||
of some pages to turn off the TOC from being displayed.
|
||||
|
||||
Here is the example front matter:
|
||||
|
||||
```
|
||||
---
|
||||
title: "Permalinks"
|
||||
date: "2013-11-18"
|
||||
aliases:
|
||||
- "/doc/permalinks/"
|
||||
groups: ["extras"]
|
||||
groups_weight: 30
|
||||
notoc: true
|
||||
---
|
||||
```
|
||||
|
||||
Here is the corresponding code inside of the template:
|
||||
|
||||
{{ if not .Params.notoc }}
|
||||
<div id="toc" class="well col-md-4 col-sm-6">
|
||||
{{ .TableOfContents }}
|
||||
</div>
|
||||
{{ end }}
|
||||
|
||||
|
||||
|
||||
## Using Site (config) Parameters
|
||||
In your top-level configuration file (eg, `config.yaml`) you can define site
|
||||
parameters, which are values which will be available to you in chrome.
|
||||
|
||||
For instance, you might declare:
|
||||
|
||||
```yaml
|
||||
params:
|
||||
CopyrightHTML: "Copyright © 2013 John Doe. All Rights Reserved."
|
||||
TwitterUser: "spf13"
|
||||
SidebarRecentLimit: 5
|
||||
```
|
||||
|
||||
Within a footer layout, you might then declare a `<footer>` which is only
|
||||
provided if the `CopyrightHTML` parameter is provided, and if it is given,
|
||||
you would declare it to be HTML-safe, so that the HTML entity is not escaped
|
||||
again. This would let you easily update just your top-level config file each
|
||||
January 1st, instead of hunting through your templates.
|
||||
|
||||
```
|
||||
{{if .Site.Params.CopyrightHTML}}<footer>
|
||||
<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
|
||||
</footer>{{end}}
|
||||
```
|
||||
|
||||
An alternative way of writing the "if" and then referencing the same value
|
||||
is to use "with" instead. With rebinds the context `.` within its scope,
|
||||
and skips the block if the variable is absent:
|
||||
|
||||
```
|
||||
{{with .Site.Params.TwitterUser}}<span class="twitter">
|
||||
<a href="https://twitter.com/{{.}}" rel="author">
|
||||
<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
|
||||
alt="Twitter"></a>
|
||||
</span>{{end}}
|
||||
```
|
||||
|
||||
Finally, if you want to pull "magic constants" out of your layouts, you can do
|
||||
so, such as in this example:
|
||||
|
||||
```
|
||||
<nav class="recent">
|
||||
<h1>Recent Posts</h1>
|
||||
<ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
|
||||
<li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
|
||||
{{end}}</ul>
|
||||
</nav>
|
||||
```
|
||||
|
||||
|
||||
[go]: https://golang.org/
|
||||
[gohtmltemplate]: https://golang.org/pkg/html/template/
|
||||
@ -1,86 +0,0 @@
|
||||
---
|
||||
title: Getting Started with Hugo
|
||||
date: 2014-04-02
|
||||
tags:
|
||||
- "go"
|
||||
- "golang"
|
||||
- "hugo"
|
||||
- "development"
|
||||
categories:
|
||||
- "Development"
|
||||
- "golang"
|
||||
menu: main
|
||||
---
|
||||
|
||||
## Step 1. Install Hugo
|
||||
|
||||
Go to [Hugo releases](https://github.com/spf13/hugo/releases) and download the
|
||||
appropriate version for your OS and architecture.
|
||||
|
||||
Save it somewhere specific as we will be using it in the next step.
|
||||
|
||||
More complete instructions are available at [Install Hugo](https://gohugo.io/getting-started/installing/)
|
||||
|
||||
## Step 2. Build the Docs
|
||||
|
||||
Hugo has its own example site which happens to also be the documentation site
|
||||
you are reading right now.
|
||||
|
||||
Follow the following steps:
|
||||
|
||||
1. Clone the [Hugo repository](https://github.com/spf13/hugo)
|
||||
2. Go into the repo
|
||||
3. Run hugo in server mode and build the docs
|
||||
4. Open your browser to http://localhost:1313
|
||||
|
||||
Corresponding pseudo commands:
|
||||
|
||||
git clone https://github.com/spf13/hugo
|
||||
cd hugo
|
||||
/path/to/where/you/installed/hugo server --source=./docs
|
||||
> 29 pages created
|
||||
> 0 tags index created
|
||||
> in 27 ms
|
||||
> Web Server is available at http://localhost:1313
|
||||
> Press ctrl+c to stop
|
||||
|
||||
Once you've gotten here, follow along the rest of this page on your local build.
|
||||
|
||||
## Step 3. Change the docs site
|
||||
|
||||
Stop the Hugo process by hitting Ctrl+C.
|
||||
|
||||
Now we are going to run hugo again, but this time with hugo in watch mode.
|
||||
|
||||
/path/to/hugo/from/step/1/hugo server --source=./docs --watch
|
||||
> 29 pages created
|
||||
> 0 tags index created
|
||||
> in 27 ms
|
||||
> Web Server is available at http://localhost:1313
|
||||
> Watching for changes in /Users/spf13/Code/hugo/docs/content
|
||||
> Press ctrl+c to stop
|
||||
|
||||
|
||||
Open your [favorite editor](http://vim.spf13.com) and change one of the source
|
||||
content pages. How about changing this very file to *fix the typo*. How about changing this very file to *fix the typo*.
|
||||
|
||||
Content files are found in `docs/content/`. Unless otherwise specified, files
|
||||
are located at the same relative location as the url, in our case
|
||||
`docs/content/overview/quickstart.md`.
|
||||
|
||||
Change and save this file.. Notice what happened in your terminal.
|
||||
|
||||
> Change detected, rebuilding site
|
||||
|
||||
> 29 pages created
|
||||
> 0 tags index created
|
||||
> in 26 ms
|
||||
|
||||
Refresh the browser and observe that the typo is now fixed.
|
||||
|
||||
Notice how quick that was. Try to refresh the site before it's finished building. I double dare you.
|
||||
Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.
|
||||
|
||||
## Step 4. Have fun
|
||||
|
||||
The best way to learn something is to play with it.
|
||||
@ -1,43 +0,0 @@
|
||||
---
|
||||
title: MathJax
|
||||
description: Simple MathJax example test article
|
||||
date: 2019-09-23
|
||||
mathjax: true
|
||||
tags:
|
||||
- "MathJax"
|
||||
---
|
||||
|
||||
MathJax JavaScript library allows you to include mathematics in your web pages for viewing in any modern browser.
|
||||
<!--more-->
|
||||
|
||||
## How to enable MathJax
|
||||
|
||||
For enabling MathJax, add this to your content's frontmatter:
|
||||
|
||||
```yaml
|
||||
mathjax: true
|
||||
```
|
||||
|
||||
## MathJax example
|
||||
|
||||
**Input**:
|
||||
|
||||
```
|
||||
When \\( a \ne 0 \\), there are two solutions to
|
||||
|
||||
$$ ax^2 + bx + c = 0 $$
|
||||
|
||||
and they are:
|
||||
|
||||
\\[ x = {-b \pm \sqrt{b^2-4ac} \over 2a} \\]
|
||||
```
|
||||
|
||||
**Output**:
|
||||
|
||||
When \\( a \ne 0 \\), there are two solutions to
|
||||
|
||||
$$ ax^2 + bx + c = 0 $$
|
||||
|
||||
and they are:
|
||||
|
||||
\\[ x = {-b \pm \sqrt{b^2-4ac} \over 2a} \\]
|
||||
@ -1,50 +0,0 @@
|
||||
---
|
||||
title: Hugo Syntax Highlighting
|
||||
description: Syntax Highlighting example test article that shows how to creating and highlighting code blocks in Hugo-generated site
|
||||
date: 2018-04-15
|
||||
categories:
|
||||
- "Development"
|
||||
tags:
|
||||
- "Chroma"
|
||||
- "Hugo"
|
||||
- "Syntax Highlighting"
|
||||
- "HTML"
|
||||
- "Markdown"
|
||||
---
|
||||
|
||||
You can have code snippets highlighted so that they are easier to read on your site using Chroma, Hugo's default syntax highlighter. It is built in Go lang and is really, really fast – and for the most important parts compatible with Pygments. Chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI-coloured text, etc.
|
||||
<!--more-->
|
||||
|
||||
The example below shows a simple HTML code snippet highlighted with the Hugo [highlight](https://gohugo.io/content-management/shortcodes/#highlight) built-in shortcode:
|
||||
|
||||
{{< highlight html >}}
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>Example HTML5 Document</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>Test</p>
|
||||
</body>
|
||||
</html>
|
||||
{{< /highlight >}}
|
||||
|
||||
The following code snippet was used to achieve that result:
|
||||
|
||||
```
|
||||
{{</* highlight html */>}}
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>Example HTML5 Document</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>Test</p>
|
||||
</body>
|
||||
</html>
|
||||
{{</* /highlight */>}}
|
||||
```
|
||||
|
||||
For more information, see "[Hugo Syntax Highlighting](https://gohugo.io/content-management/syntax-highlighting)" from official Hugo docs.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
@ -1,43 +0,0 @@
|
||||
---
|
||||
title: Translation Support
|
||||
description: With Hugo i18n possibilities, you can easily have a website in your language. This article explains how to translate and change language in Hugo's generated site.
|
||||
date: 2019-09-22
|
||||
tags:
|
||||
- "Translation"
|
||||
- "i18n"
|
||||
- "Hugo"
|
||||
featured:
|
||||
alt: Translation support
|
||||
previewOnly: true
|
||||
---
|
||||
|
||||
With Hugo i18n possibilities, you can easily have a website in your language. This Hugo theme is ready to be translated into other languages. You can create a special file that contains translated text to show the visitor instead of English.
|
||||
<!--more-->
|
||||
|
||||
## Translating the Theme
|
||||
|
||||
1. Create a folder named `/i18n/` in your Hugo site's root
|
||||
1. Create a file `<LANG-CODE>.yaml` inside `/i18n` folder. Language files `<LANG-CODE>.yaml` should be named according to RFC 5646 with names such as `en-US.yaml`, `fr.yaml`, `de.yaml`, etc.
|
||||
1. Copy a reference template to your translation from `<THEME>/i18n/en.yaml` file
|
||||
1. Translate all available `translation` strings into chosen language
|
||||
|
||||
For example, to create German translation, create a file `/i18n/de.yaml` in the folder of your Hugo site, copy reference template from `<THEME>/i18n/en.yaml` file and translate all available `translation` strings.
|
||||
|
||||
## Changing Site Language in Hugo
|
||||
|
||||
To use the translations, just set a correct value for `defaultContentLanguage` in site config file:
|
||||
|
||||
{{< highlight toml >}}
|
||||
defaultContentLanguage = "en" # de / fr / other lang code...
|
||||
{{< /highlight >}}
|
||||
|
||||
In other words, this field determines which i18n file to use.
|
||||
|
||||
## Contributing Translation
|
||||
|
||||
If you want to upload your translation in the theme master repository, feel free to create a pull request.
|
||||
|
||||
## More Information
|
||||
|
||||
* [Hugo Multilingual Mode](https://gohugo.io/content-management/multilingual/)
|
||||
* [Hugo i18n function](https://gohugo.io/functions/i18n/)
|
||||
@ -1,52 +0,0 @@
|
||||
# Entry
|
||||
- id: entry_toc
|
||||
translation: "Inhaltsverzeichnis"
|
||||
|
||||
# Entry meta
|
||||
- id: meta_lastmod
|
||||
translation: "Aktualisiert"
|
||||
|
||||
- id: meta_categories
|
||||
translation: "Kategorien"
|
||||
|
||||
- id: meta_tags
|
||||
translation: "Tags"
|
||||
|
||||
# Share
|
||||
- id: share-caption
|
||||
translation: "Share on"
|
||||
|
||||
- id: save-caption
|
||||
translation: "Speichere nach"
|
||||
|
||||
# Related
|
||||
- id: related_title
|
||||
translation: "Ähnlich"
|
||||
|
||||
# Footer
|
||||
- id: footer_credits
|
||||
translation: "Powered by <a href=\"https://gohugo.io/\" rel=\"nofollow noopener\" target=\"_blank\">Hugo</a> und \
|
||||
<a href=\"https://github.com/vimux/binario\" rel=\"nofollow noopener\" target=\"_blank\">Binario</a> theme."
|
||||
|
||||
# "No posts" empty state
|
||||
- id: empty_title
|
||||
translation: "Aktuell noch keine Posts vorhanden!"
|
||||
|
||||
- id: empty_text_start
|
||||
translation: "Sowie Posts in Deinen als <code>mainSections</code> definierten Verzeichnissen hinzugefügt werden"
|
||||
|
||||
- id: empty_text_end
|
||||
translation: "erscheinen sie hier."
|
||||
|
||||
- id: empty_tip
|
||||
translation: "<b>Tip:</b> Du kannst die als <code>mainSections</code> betrachteten Verzeichnisse in der Konfigurationsdatei Deiner Seite ändern."
|
||||
|
||||
# 404
|
||||
- id: page404_title
|
||||
translation: "404 Seite nicht gefunden"
|
||||
|
||||
- id: page404_lead
|
||||
translation: "Entschuldigung, die Seite die Du besuchen wolltest existiert nicht."
|
||||
|
||||
- id: page404_link
|
||||
translation: "Zurück zur Hauptseite"
|
||||
@ -1,52 +0,0 @@
|
||||
# Entry
|
||||
- id: entry_toc
|
||||
translation: "Sisältö"
|
||||
|
||||
# Entry meta
|
||||
- id: meta_lastmod
|
||||
translation: "Päivitetty"
|
||||
|
||||
- id: meta_categories
|
||||
translation: "Aiheet"
|
||||
|
||||
- id: meta_tags
|
||||
translation: "Tunnisteet"
|
||||
|
||||
# Share
|
||||
- id: share-caption
|
||||
translation: "Jaa"
|
||||
|
||||
- id: save-caption
|
||||
translation: "Talleta"
|
||||
|
||||
# Related
|
||||
- id: related_title
|
||||
translation: "Liittyvät"
|
||||
|
||||
# Footer
|
||||
- id: footer_credits
|
||||
translation: "Sivut on luotu <a href=\"https://gohugo.io/\" rel=\"nofollow noopener\" target=\"_blank\">Hugo</a>:lla käyttäen \
|
||||
<a href=\"https://github.com/vimux/binario\" rel=\"nofollow noopener\" target=\"_blank\">Binario</a> teemaa."
|
||||
|
||||
# "No posts" empty state
|
||||
- id: empty_title
|
||||
translation: "Et ole vielä tehnyt julkaisuja!"
|
||||
|
||||
- id: empty_text_start
|
||||
translation: "Lisättyäsi postauksia <code>mainSections</code> kansioihin"
|
||||
|
||||
- id: empty_text_end
|
||||
translation: "näkyvät ne täällä"
|
||||
|
||||
- id: empty_tip
|
||||
translation: "<b>Tip:</b> Voit muuttaa <code>mainSections</code> kansiot sivuston konfiguroinnissa."
|
||||
|
||||
# 404
|
||||
- id: page404_title
|
||||
translation: "404 Sivua ei löydy"
|
||||
|
||||
- id: page404_lead
|
||||
translation: "Valitettavasti etsimäsi sivu ei ole olemassa."
|
||||
|
||||
- id: page404_link
|
||||
translation: "Siirry takaisin pääsivulle"
|
||||
@ -1,52 +0,0 @@
|
||||
# Entry
|
||||
- id: entry_toc
|
||||
translation: "Sommario"
|
||||
|
||||
# Entry meta
|
||||
- id: meta_lastmod
|
||||
translation: "Ultima modifica"
|
||||
|
||||
- id: meta_categories
|
||||
translation: "Categorie"
|
||||
|
||||
- id: meta_tags
|
||||
translation: "Tag"
|
||||
|
||||
# Share
|
||||
- id: share-caption
|
||||
translation: "Condividi su"
|
||||
|
||||
- id: save-caption
|
||||
translation: "Salva su"
|
||||
|
||||
# Related
|
||||
- id: related_title
|
||||
translation: "Correlati"
|
||||
|
||||
# Footer
|
||||
- id: footer_credits
|
||||
translation: "Offerto da <a href=\"https://gohugo.io/\" rel=\"nofollow noopener\" target=\"_blank\">Hugo</a> e \
|
||||
il tema <a href=\"https://github.com/vimux/binario\" rel=\"nofollow noopener\" target=\"_blank\">Binario</a>."
|
||||
|
||||
# "No posts" empty state
|
||||
- id: empty_title
|
||||
translation: "Non hai ancora nessun post!"
|
||||
|
||||
- id: empty_text_start
|
||||
translation: "Man mano che i post vengono aggiunti nelle tue cartelle <code>mainSections</code>"
|
||||
|
||||
- id: empty_text_end
|
||||
translation: "appariranno qui"
|
||||
|
||||
- id: empty_tip
|
||||
translation: "<b>Suggerimento:</b> puoi cambiare le cartelle <code>mainSections</code> dal file di configurazione del sito."
|
||||
|
||||
# 404
|
||||
- id: page404_title
|
||||
translation: "404 Pagina non trovata"
|
||||
|
||||
- id: page404_lead
|
||||
translation: "Siamo spiacenti, la pagina che stavi cercando non esiste."
|
||||
|
||||
- id: page404_link
|
||||
translation: "Torna alla pagina principale"
|
||||
@ -1,52 +0,0 @@
|
||||
# Entry
|
||||
- id: entry_toc
|
||||
translation: "Conteúdo da página"
|
||||
|
||||
# Entry meta
|
||||
- id: meta_lastmod
|
||||
translation: "Última modificação"
|
||||
|
||||
- id: meta_categories
|
||||
translation: "Categorias"
|
||||
|
||||
- id: meta_tags
|
||||
translation: "Tags"
|
||||
|
||||
# Share
|
||||
- id: share-caption
|
||||
translation: "Campartilhar no"
|
||||
|
||||
- id: save-caption
|
||||
translation: "Salvar no"
|
||||
|
||||
# Related
|
||||
- id: related_title
|
||||
translation: "Relacionado"
|
||||
|
||||
# Footer
|
||||
- id: footer_credits
|
||||
translation: "Powered by <a href=\"https://gohugo.io/\" rel=\"nofollow noopener\" target=\"_blank\">Hugo</a> and \
|
||||
<a href=\"https://github.com/vimux/binario\" rel=\"nofollow noopener\" target=\"_blank\">Binario</a> theme."
|
||||
|
||||
# "No posts" empty state
|
||||
- id: empty_title
|
||||
translation: "Você ainda não tem postagens!"
|
||||
|
||||
- id: empty_text_start
|
||||
translation: "Conforme as postagens são adicionadas no diretório <code>mainSections</code>"
|
||||
|
||||
- id: empty_text_end
|
||||
translation: "Eles vão aparecendo aqui"
|
||||
|
||||
- id: empty_tip
|
||||
translation: "<b>Dica:</b> Você pode alterar o diretório <code>mainSections</code> no site config file."
|
||||
|
||||
# 404
|
||||
- id: page404_title
|
||||
translation: "404 Página não encontrada"
|
||||
|
||||
- id: page404_lead
|
||||
translation: "Desculpe, a página que você estava procurando não existe."
|
||||
|
||||
- id: page404_link
|
||||
translation: "Voltar para a página principal"
|
||||
@ -1,52 +0,0 @@
|
||||
# Entry
|
||||
- id: entry_toc
|
||||
translation: "Conteúdo da página"
|
||||
|
||||
# Entry meta
|
||||
- id: meta_lastmod
|
||||
translation: "Última modificação"
|
||||
|
||||
- id: meta_categories
|
||||
translation: "Categorias"
|
||||
|
||||
- id: meta_tags
|
||||
translation: "Tags"
|
||||
|
||||
# Share
|
||||
- id: share-caption
|
||||
translation: "Campartilhar"
|
||||
|
||||
- id: save-caption
|
||||
translation: "Salvar"
|
||||
|
||||
# Related
|
||||
- id: related_title
|
||||
translation: "Relacionado"
|
||||
|
||||
# Footer
|
||||
- id: footer_credits
|
||||
translation: "Powered by <a href=\"https://gohugo.io/\" rel=\"nofollow noopener\" target=\"_blank\">Hugo</a> and \
|
||||
<a href=\"https://github.com/vimux/binario\" rel=\"nofollow noopener\" target=\"_blank\">Binario</a> theme."
|
||||
|
||||
# "No posts" empty state
|
||||
- id: empty_title
|
||||
translation: "Você ainda não tem postagens!"
|
||||
|
||||
- id: empty_text_start
|
||||
translation: "Conforme as postagens são adicionadas no diretório <code>mainSections</code>"
|
||||
|
||||
- id: empty_text_end
|
||||
translation: "Eles vão aparecendo aqui"
|
||||
|
||||
- id: empty_tip
|
||||
translation: "<b>Dica:</b> Você pode alterar o diretório <code>mainSections</code> no site config file."
|
||||
|
||||
# 404
|
||||
- id: page404_title
|
||||
translation: "404 Página não encontrada"
|
||||
|
||||
- id: page404_lead
|
||||
translation: "Desculpe, a página que você estava procurando não existe."
|
||||
|
||||
- id: page404_link
|
||||
translation: "Voltar para a página principal"
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 339 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 220 KiB |
4370
themes/binario/package-lock.json
generated
4370
themes/binario/package-lock.json
generated
File diff suppressed because it is too large
Load Diff
@ -1,75 +0,0 @@
|
||||
{
|
||||
"name": "binario",
|
||||
"version": "1.0.0",
|
||||
"description": "Responsive card-based & code-light Hugo theme",
|
||||
"license": "MIT",
|
||||
"browserslist": [
|
||||
"> 0.25%",
|
||||
"last 2 version",
|
||||
"not dead",
|
||||
"IE 11",
|
||||
"iOS >= 9"
|
||||
],
|
||||
"postcss": {
|
||||
"plugins": {
|
||||
"autoprefixer": {
|
||||
"cascade": false
|
||||
}
|
||||
}
|
||||
},
|
||||
"eslintConfig": {
|
||||
"extends": "airbnb-base",
|
||||
"env": {
|
||||
"browser": true
|
||||
},
|
||||
"rules": {
|
||||
"indent": [
|
||||
2,
|
||||
"tab"
|
||||
],
|
||||
"comma-dangle": [
|
||||
"error",
|
||||
{
|
||||
"arrays": "always-multiline",
|
||||
"objects": "always-multiline",
|
||||
"imports": "always-multiline",
|
||||
"exports": "always-multiline",
|
||||
"functions": "ignore"
|
||||
}
|
||||
],
|
||||
"no-tabs": 0
|
||||
}
|
||||
},
|
||||
"dependencies": {},
|
||||
"devDependencies": {
|
||||
"autoprefixer": "^10.4.16",
|
||||
"editorconfig-checker": "^5.1.1",
|
||||
"eslint": "^8.52.0",
|
||||
"eslint-config-airbnb-base": "^15.0.0",
|
||||
"eslint-plugin-import": "^2.29.0",
|
||||
"postcss": "^8.4.31",
|
||||
"postcss-cli": "^10.1.0",
|
||||
"stylelint": "^15.11.0",
|
||||
"stylelint-order": "^6.0.3"
|
||||
},
|
||||
"scripts": {
|
||||
"lint:prefixes": "postcss static/css/*.css assets/css/*.css",
|
||||
"lint:css": "stylelint static/css/*.css assets/css/*.css",
|
||||
"lint:js": "eslint static/js/*.js",
|
||||
"lint:editorconfig": "editorconfig-checker",
|
||||
"lint": "npm run lint:css && npm run lint:js && npm run lint:editorconfig",
|
||||
"fix:prefixes": "postcss -r static/css/*.css assets/css/*.css",
|
||||
"fix:css": "stylelint static/css/*.css assets/css/*.css --fix",
|
||||
"fix:js": "eslint static/js/*.js --fix",
|
||||
"fix": "npm run fix:prefixes && npm run fix:css && npm run fix:js",
|
||||
"test": "npm run lint"
|
||||
},
|
||||
"repository": {
|
||||
"type": "git",
|
||||
"url": "git+https://github.com/Vimux/Binario.git"
|
||||
},
|
||||
"bugs": {
|
||||
"url": "https://github.com/Vimux/Binario/issues"
|
||||
},
|
||||
"homepage": "https://github.com/Vimux/Binario"
|
||||
}
|
||||
Loading…
x
Reference in New Issue
Block a user