├── src
├── .hugo_build.lock
├── content
│ ├── posts
│ │ └── .gitkeep
│ ├── search.md
│ ├── themes.csv
│ ├── projects.csv
│ ├── docs
│ │ ├── compose
│ │ │ ├── _index.md
│ │ │ ├── organize-content.md
│ │ │ ├── shortcodes-example.md
│ │ │ ├── use-forestry-cms.md
│ │ │ ├── search.md
│ │ │ ├── install-theme.md
│ │ │ ├── customize.md
│ │ │ ├── graphs-charts-tables.md
│ │ │ ├── shortcodes.md
│ │ │ └── mermaid.md
│ │ ├── clarity
│ │ │ ├── _index.md
│ │ │ ├── features.md
│ │ │ ├── theme-overrides.md
│ │ │ ├── syntax-highlighting.md
│ │ │ ├── blogging.md
│ │ │ ├── getting-started.md
│ │ │ ├── images.md
│ │ │ └── customize.md
│ │ └── _index.md
│ └── _index.md
├── static
│ └── images
│ │ ├── painting.jpg
│ │ ├── scribble.jpg
│ │ ├── clarity
│ │ ├── tags.png
│ │ ├── tn.png
│ │ ├── article-toc.png
│ │ ├── screenshot.png
│ │ ├── tn-darkmode.png
│ │ ├── image-figure.png
│ │ ├── image-inline.png
│ │ ├── syntax-block.gif
│ │ ├── screenshot-darkmode.png
│ │ ├── screenshot-mobile.png
│ │ └── screenshot-mobile-darkmode.png
│ │ ├── GitHubMarkDark.svg
│ │ ├── GitHubMarkLight.svg
│ │ ├── compose.svg
│ │ └── compose-light.svg
├── README.md
├── go.mod
├── config
│ └── _default
│ │ ├── menus
│ │ └── menu.en.toml
│ │ ├── markup.toml
│ │ └── params.toml
├── resources
│ └── _gen
│ │ └── assets
│ │ └── sass
│ │ └── sass
│ │ ├── main.sass_ca26857cefa9076967ab300682271513.json
│ │ └── main.sass_ca26857cefa9076967ab300682271513.content
├── config.toml
├── netlify.toml
├── LICENSE
└── go.sum
├── .gitignore
├── CODEOWNER
├── OpenCV
├── remove.sh
├── .ipynb_checkpoints
│ ├── remove-checkpoint.sh
│ └── install_opencv4.1.1_jetson-checkpoint.sh
└── install_opencv4.1.1_jetson.sh
├── .gitmodules
├── .github
└── prlint.json
├── .pre-commit-config.yaml
├── set_cuda.sh
├── LICENSE
├── contribute.md
└── README.md
/src/.hugo_build.lock:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/src/content/posts/.gitkeep:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | .ipynb_checkpoints
2 | .idea
3 |
--------------------------------------------------------------------------------
/CODEOWNER:
--------------------------------------------------------------------------------
1 | Kevin Yu (@yqlbu)
2 | Shi Kun (@kunish)
3 |
--------------------------------------------------------------------------------
/src/content/search.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Search"
3 | searchPage = true
4 | type = "search"
5 | +++
--------------------------------------------------------------------------------
/OpenCV/remove.sh:
--------------------------------------------------------------------------------
1 | #!/bin/bash
2 | echo " -> Purge old opencv installation"
3 | sudo apt-get purge libopencv*
4 |
--------------------------------------------------------------------------------
/src/content/themes.csv:
--------------------------------------------------------------------------------
1 | clarity,V.1,chipzoller
2 | compose,V.1,weru
3 | swift,V.2,weru
4 | newsroom,V.1,weru
5 |
--------------------------------------------------------------------------------
/.gitmodules:
--------------------------------------------------------------------------------
1 | [submodule "src/themes/compose"]
2 | path = src/themes/compose
3 | url = git@github.com:onweru/compose.git
4 |
--------------------------------------------------------------------------------
/src/static/images/painting.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/painting.jpg
--------------------------------------------------------------------------------
/src/static/images/scribble.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/scribble.jpg
--------------------------------------------------------------------------------
/src/static/images/clarity/tags.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/tags.png
--------------------------------------------------------------------------------
/src/static/images/clarity/tn.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/tn.png
--------------------------------------------------------------------------------
/src/README.md:
--------------------------------------------------------------------------------
1 | ## Guide
2 |
3 | This guide covers the necessary bits. As the project evolves, it will only become more comprehensive
4 |
--------------------------------------------------------------------------------
/OpenCV/.ipynb_checkpoints/remove-checkpoint.sh:
--------------------------------------------------------------------------------
1 | #!/bin/bash
2 | echo " -> Purge old opencv installation"
3 | sudo apt-get purge libopencv*
4 |
--------------------------------------------------------------------------------
/src/go.mod:
--------------------------------------------------------------------------------
1 | module compose-exampleSite
2 |
3 | go 1.15
4 |
5 | require github.com/onweru/compose v0.0.0-20210506215729-3f2ccb9b9acb // indirect
6 |
--------------------------------------------------------------------------------
/src/static/images/clarity/article-toc.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/article-toc.png
--------------------------------------------------------------------------------
/src/static/images/clarity/screenshot.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/screenshot.png
--------------------------------------------------------------------------------
/src/static/images/clarity/tn-darkmode.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/tn-darkmode.png
--------------------------------------------------------------------------------
/src/static/images/clarity/image-figure.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/image-figure.png
--------------------------------------------------------------------------------
/src/static/images/clarity/image-inline.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/image-inline.png
--------------------------------------------------------------------------------
/src/static/images/clarity/syntax-block.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/syntax-block.gif
--------------------------------------------------------------------------------
/src/static/images/clarity/screenshot-darkmode.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/screenshot-darkmode.png
--------------------------------------------------------------------------------
/src/static/images/clarity/screenshot-mobile.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/screenshot-mobile.png
--------------------------------------------------------------------------------
/src/static/images/clarity/screenshot-mobile-darkmode.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/piyoki/jetson-packages-family/HEAD/src/static/images/clarity/screenshot-mobile-darkmode.png
--------------------------------------------------------------------------------
/.github/prlint.json:
--------------------------------------------------------------------------------
1 | {
2 | "title": [
3 | {
4 | "pattern": "^(build|ci|docs|feat|fix|perf|refactor|style|test)((.+))?:\\s.+",
5 | "message": "Your title needs to be prefixed with a topic"
6 | }
7 | ]
8 | }
9 |
--------------------------------------------------------------------------------
/.pre-commit-config.yaml:
--------------------------------------------------------------------------------
1 | repos:
2 | - repo: https://github.com/pre-commit/pre-commit-hooks
3 | rev: v4.0.1
4 | hooks:
5 | - id: trailing-whitespace
6 | - id: end-of-file-fixer
7 | - id: check-json
8 | - id: check-yaml
9 | - id: double-quote-string-fixer
10 |
--------------------------------------------------------------------------------
/src/config/_default/menus/menu.en.toml:
--------------------------------------------------------------------------------
1 | # menu items
2 | [[main]]
3 | name = "Docs"
4 | weight = 2
5 | url = "docs/"
6 |
7 | [[main]]
8 | name = "Example"
9 | weight = 3
10 | url = "https://docs.neuralvibes.com"
11 |
12 | # [[main]]
13 | # name = "Blog"
14 | # weight = 4
15 | # url = "blog/"
--------------------------------------------------------------------------------
/src/content/projects.csv:
--------------------------------------------------------------------------------
1 | project 6,alpha,weru
2 | project 4,beta,dan
3 | project 4,candidate,dahl
4 | project y,abandoned,weru
5 | project 1,alpha,weru
6 | project 4,beta,ryan
7 | project 4,candidate,dan
8 | project y,abandoned,weru
9 | project 11,alpha,dahl
10 | project 4,beta,dan
11 | project 4,candidate,dan
12 | project A,abandoned,weru
13 |
--------------------------------------------------------------------------------
/src/content/docs/compose/_index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Compose Docs"
3 | weight: 1
4 | ---
5 |
6 | Welcome to the Compose theme user guide! This guide shows you how to get started creating technical documentation sites using Compose, including site customization and how to use Compose's blocks and templates.
7 |
8 | {{< button "./install-theme/" "Get started now" >}}
9 |
--------------------------------------------------------------------------------
/src/resources/_gen/assets/sass/sass/main.sass_ca26857cefa9076967ab300682271513.json:
--------------------------------------------------------------------------------
1 | {"Target":"css/styles.3c1c2e57871ba783a4d85c82cb38c2dfd4be3ee80d6cbdbaa129405d9af1b18c43afa4f48e280dc331df5f85a5ee0949e4757cf2a98b54a8125d4bbb0dea11c5.css","MediaType":"text/css","Data":{"Integrity":"sha512-PBwuV4cbp4Ok2FyCyzjC39S+PugNbL26oSlAXZrxsYxDr6T0jigNwzHfX4Wl7glJ5HV88qmLVKgSXUu7DeoRxQ=="}}
--------------------------------------------------------------------------------
/src/content/docs/clarity/_index.md:
--------------------------------------------------------------------------------
1 | ---
2 | Title: Clarity Docs
3 | weight: 10
4 | ---
5 |
6 | __Hugo Clarity__ is a technology-minded theme for Hugo based on VMware's open-source [Clarity Design System](https://clarity.design/) featuring rich code support, dark/light mode, mobile support, and much more. See [a live demo at __neonmirrors.net__](https://neonmirrors.net/).
7 |
8 | {{< button "./getting-started/" "Get started with Clarity" >}}
9 |
--------------------------------------------------------------------------------
/src/config/_default/markup.toml:
--------------------------------------------------------------------------------
1 | [goldmark]
2 | [goldmark.renderer]
3 | unsafe = true
4 | [goldmark.extensions]
5 | typographer = false
6 | [highlight]
7 | codeFences = true
8 | guessSyntax = false
9 | hl_Lines = ""
10 | lineNoStart = 1
11 | lineNos = true
12 | lineNumbersInTable = false
13 | noClasses = false
14 | style = "monokai"
15 | tabWidth = 2
16 | [tableOfContents]
17 | endLevel = 4
18 | ordered = false
19 | startLevel = 2
--------------------------------------------------------------------------------
/src/config.toml:
--------------------------------------------------------------------------------
1 | baseURL = "https://example.com/"
2 | title = "Compose Docs"
3 | enableRobotsTXT = true
4 | # this example loads the theme as hugo module
5 | # comment out line below, and uncomment the line after it if you prefer to load the theme normally
6 | theme = ["github.com/onweru/compose"] # edit this if you'ld rather use a fork of this repo
7 | # theme = "compose"
8 | enableGitInfo = true
9 |
10 | disableKinds = ["taxonomy", "taxonomyTerm"]
11 |
12 | [outputs]
13 | home = ["HTML", "RSS","JSON"]
--------------------------------------------------------------------------------
/set_cuda.sh:
--------------------------------------------------------------------------------
1 | #!/bin/bash
2 |
3 | set -e
4 |
5 | if ! grep 'cuda/bin' ${HOME}/.bashrc > /dev/null ; then
6 | echo "[BASH] Add CUDA path into ~/.bashrc"
7 | echo >> ${HOME}/.bashrc
8 | echo "export PATH=/usr/local/cuda/bin:\${PATH}" >> ${HOME}/.bashrc
9 | echo "export LD_LIBRARY_PATH=/usr/local/cuda/lib64:\${LD_LIBRARY_PATH}" >> ${HOME}/.bashrc
10 | echo "export CPATH=$CPATH:/usr/local/cuda/targets/aarch64-linux/include" >> ${HOME}/.bashrc
11 | echo "export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/cuda/targets/aarch64-linux/lib" >> ${HOME}/.bashrc
12 | source ~/.bashrc
13 | fi
14 |
--------------------------------------------------------------------------------
/src/content/docs/_index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Themes' Docs"
3 | weight: 1
4 | ---
5 |
6 | These docs consists of two parts:
7 |
8 | 1. Hugo Compose Themes docs
9 | 2. Hugo Clarity Theme docs.
10 |
11 | Please note that the features listed under each theme are independent of each other. That is to say, some features may only be found in one theme and not in both.
12 |
13 |
14 |
15 | {{< button "./compose/" "Compose Theme Docs" "mb-1" >}}
16 |
17 | {{< button "./clarity/" "Clarity Theme Docs" >}}
18 |
19 |
--------------------------------------------------------------------------------
/src/content/docs/clarity/features.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Features
3 | Weight: 13
4 | ---
5 |
6 | * Blog with tagging and category options
7 | * Deeplinks
8 | * Native Image Lazy Loading
9 | * Customizable (see config)
10 | * Dark Mode (with UI controls for user preference setting)
11 | * Toggleable table of contents
12 | * Flexible image configuration
13 | * Logo alignment
14 | * Mobile support with configurable menu alignment
15 | * Syntax Highlighting
16 | * Rich code block functions including:
17 | 1. Copy to clipboard
18 | 2. Toggle line wrap (dynamic)
19 | 3. Toggle line numbers
20 | 4. Language label
21 | 5. Toggle block expansion/contraction (dynamic)
22 |
23 | To put it all in context, here is a preview showing all functionality.
24 |
25 | 
26 |
--------------------------------------------------------------------------------
/src/netlify.toml:
--------------------------------------------------------------------------------
1 | [build]
2 | publish = "public"
3 | #command = "hugo --gc --minify"
4 | command = "hugo --gc --minify --baseURL https://docs.neuralvibes.com/"
5 |
6 | [context.production.environment]
7 | HUGO_VERSION = "0.88.1"
8 | HUGO_ENV = "production"
9 | HUGO_ENABLEGITINFO = "true"
10 |
11 | [context.split1]
12 | command = "hugo --gc --minify --enableGitInfo"
13 |
14 | [context.split1.environment]
15 | HUGO_VERSION = "0.88.1"
16 | HUGO_ENV = "production"
17 |
18 | [context.deploy-preview]
19 | command = "hugo --gc --minify --buildFuture -b $DEPLOY_PRIME_URL"
20 |
21 | [context.deploy-preview.environment]
22 | HUGO_VERSION = "0.88.1"
23 |
24 | [context.branch-deploy]
25 | command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"
26 |
27 | [context.branch-deploy.environment]
28 | HUGO_VERSION = "0.88.1"
29 |
30 | [context.next.environment]
31 | HUGO_ENABLEGITINFO = "true"
32 |
33 |
--------------------------------------------------------------------------------
/src/static/images/GitHubMarkDark.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/src/static/images/GitHubMarkLight.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/src/content/docs/compose/organize-content.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Content organization"
3 | weight = 4
4 | +++
5 |
6 | This theme is primarily meant for documentation.
7 |
8 | #### Documentation
9 |
10 | All your documentation content should be authored within the `docs` directory.
11 |
12 | Unlike other regular pages, the documentation pages will have a left sidebar. This sidebar will list links to all the pages in the documentation pages. Beneath each link, there will be a collapsible list of __table of contents'__ links. These nested lists will unfold automatically on the active/current page.
13 |
14 | #### Home Page
15 |
16 | At the root level there's an `_index.md` page which is the homepage. Feel free to edit it as you like.
17 |
18 | #### Other pages
19 |
20 | You can also add as many regular pages as you like e.g `about.md`, `contact.md`...
21 |
22 | Take advantage of [shortcodes](./shortcodes) to customize the layouts of these pages and any other.
23 |
24 | #### Does this theme support blogging function?
25 |
26 | Currently, no.
27 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2020 kevinyu
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/src/config/_default/params.toml:
--------------------------------------------------------------------------------
1 | mainSections = ["posts"] # use it for blog page section
2 |
3 | uniqueHomePage = true # change to false to add sidebar to homepage
4 |
5 | repo = "https://github.com/onweru/compose"
6 |
7 | time_format_blog = "Monday, January 02, 2006"
8 | time_format_default = "January 2, 2006"
9 | enableDarkMode = true # set to false to disable darkmode by default # user will still have the option to use dark mode
10 |
11 | # sets the maximum number of lines per codeblock. The codeblock will however be scrollable and expandable.
12 | codeMaxLines = 7
13 |
14 | # disable showing line numbers by default. Switch to `true` if you'd rather have them on.
15 | codeLineNumbers = false
16 |
17 | # Site logo
18 | [logo]
19 | lightMode = "images/compose.svg"
20 | darkMode = "images/compose-light.svg"
21 |
22 | [source]
23 | name = "GitHub"
24 | iconLight = "images/GitHubMarkLight.svg"
25 | iconDark = "images/GitHubMarkDark.svg"
26 | url = "https://github.com/onweru/compose/"
27 |
28 | # optional
29 | # attribution. Feel free to delete this
30 | [author]
31 | name = "Weru"
32 | url = "https://neuralvibes.com/author/"
33 |
--------------------------------------------------------------------------------
/src/content/_index.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Compose"
3 | [data]
4 | baseChartOn = 3
5 | colors = ["#627c62", "#11819b", "#ef7f1a", "#4e1154"]
6 | columnTitles = ["Section", "Status", "Author"]
7 | fileLink = "content/projects.csv"
8 | title = "Projects"
9 |
10 | +++
11 | {{< block "grid-2" >}}
12 | {{< column >}}
13 |
14 | # Compose your Docs with **Ease**.
15 |
16 | Compose is a lean `Hugo` domentation theme, inspired by [forestry.io](https://forestry.io/docs/welcome/).
17 |
18 | {{< tip "warning" >}}
19 | Feel free to open a [PR](https://github.com/onweru/compose/pulls), raise an [issue](https://github.com/onweru/compose/issues/new/choose "Open a Github Issue")(s) or request new feature(s). {{< /tip >}}
20 |
21 | {{< tip >}}
22 | You can generate diagrams, flowcharts, and piecharts from text in a similar manner as markdown using [mermaid](./docs/compose/mermaid/).
23 |
24 | Or, [generate graphs, charts](docs/compose/graphs-charts-tables/#show-a-pie-doughnut--bar-chart-at-once) and tables from a csv, ~~or a json~~ file.
25 | {{< /tip >}}
26 |
27 | {{< button "docs/compose/" "Read the Docs" >}}{{< button "https://github.com/onweru/compose" "Download Theme" >}}
28 | {{< /column >}}
29 |
30 | {{< column >}}
31 | 
32 | {{< /column >}}
33 | {{< /block >}}
--------------------------------------------------------------------------------
/src/content/docs/clarity/theme-overrides.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Theme Overrides"
3 | +++
4 |
5 | ### Custom CSS and JS
6 |
7 | To minimize HTTP requests per page, we would recommend loading CSS styles and JavaScript helpers in single bundles. That is to say, one CSS file and one JavaScript file. Using Hugo minify functions, these files will be minified to optimize the size.
8 |
9 | Going by the above 👆🏻 reason, we recommend adding custom CSS and JS via [this custom SASS file](https://github.com/chipzoller/hugo-clarity/blob/master/assets/sass/_custom.sass) and [custom JavaScript file](https://github.com/chipzoller/hugo-clarity/blob/master/assets/js/custom.js).
10 |
11 | However, sometimes you may need to load additional style or script files. In such cases, you can add custom `.css` and `.js` files by listing them in the `config.toml` file (see the snippet below). Similar to images, these paths should be relative to the `static` directory.
12 |
13 | ```yaml
14 | [params]
15 | ...
16 | customCSS = ["css/custom.css"] # Include custom CSS files
17 | customJS = ["js/custom.js"] # Include custom JS files
18 | ...
19 | ```
20 |
21 | > __Pro Tip__: You can change the theme colors via the [this variable's SASS file](https://github.com/chipzoller/hugo-clarity/blob/master/assets/sass/_variables.sass)
22 |
23 | ### Hooks
24 |
25 | Clarity provides some hooks for adding code on page.
26 |
27 | If you need to add some code(CSS import, HTML meta or similar) to the head section on every page, add a partial to your project:
28 |
29 | ```
30 | layouts/partials/hooks/head-end.html
31 | ```
32 |
33 | Similar, if you want to add some code right before the body end, create your own version of the following file:
34 |
35 | ```
36 | layouts/partials/hooks/body-end.html
37 | ```
--------------------------------------------------------------------------------
/contribute.md:
--------------------------------------------------------------------------------
1 | ## Contribute
2 |
3 | If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.
4 |
5 | ### How to make a clean pull request
6 |
7 | - Create a `personal fork` of the project on Github.
8 | - Clone the fork on your local machine. Your remote repo on Github is called `origin`.
9 | - Add the original repository as a remote called `upstream`.
10 | - If you created your fork a while ago be sure to pull upstream changes into your local repository.
11 | - Create a new branch to work on! Branch from `develop` if it exists, else from `master`.
12 | - Implement/fix your feature, comment your code.
13 | - Follow the code style of the project, including indentation.
14 | - If the project has tests run them!
15 | - Write or adapt tests as needed.
16 | - Add or change the documentation as needed.
17 | - Squash your commits into a single commit with git's [interactive rebase](https://help.github.com/articles/interactive-rebase). Create a new branch if necessary.
18 | - Push your branch to your fork on Github, the remote `origin`.
19 | - From your fork open a pull request in the correct branch. Target the project's `develop` branch if there is one, else go for `master`!
20 | - Once the pull request is approved and merged you can pull the changes from `upstream` to your local repo and delete
21 | your extra branch(es).
22 |
23 | And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.
24 |
--------------------------------------------------------------------------------
/src/content/docs/compose/shortcodes-example.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Shortcodes Applied
3 | weight: 7
4 | description: 'This is how the shortcodes would look like in action
5 |
6 | '
7 | draft: true
8 |
9 | ---
10 | ### Blocks, columns & buttons
11 |
12 | ```sh
13 | {{* block "grid-2" */>}}
14 | {{* column */>}}
15 | #### Coumn 1
16 |
17 | Lorem ipsum dolor sit amet,
18 | ...
19 |
20 | {{* button "https://github.com/onweru/compose" "Download Theme" */>}}
21 |
22 | {{* /column */>}}
23 | {{* column */>}}
24 |
25 |
26 | ```
27 |
28 | {{< block "grid-2" >}}
29 | {{< column >}}
30 | #### Coumn 1
31 |
32 | Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et
33 |
34 | dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
35 |
36 | Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
37 |
38 | > Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
39 |
40 | {{< button "https://github.com/onweru/compose" "Download Theme" >}}
41 |
42 | {{< /column >}}
43 | {{< column >}}
44 | #### Coumn 2
45 |
46 |
47 | Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et
48 |
49 | > dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
50 |
51 | Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
52 |
53 | Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
54 |
55 | {{< button "docs/" "Read the Docs" >}}
56 |
57 | {{< /column >}}
58 | {{< /block >}}
--------------------------------------------------------------------------------
/src/content/docs/clarity/syntax-highlighting.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Syntax Highlighting"
3 | +++
4 |
5 | ### Code
6 |
7 | #### Display line numbers
8 |
9 | Choose whether to display line numbers within a code block globally with the parameter `codeLineNumbers` setting to `true` or `false`.
10 |
11 | ```yaml
12 | [params]
13 | ...
14 | codeLineNumbers = true # Shows line numbers for all code blocks globally.
15 | ...
16 | ```
17 |
18 | #### Limit code block height
19 |
20 | You can globally control the number of lines which are displayed by default for your code blocks. Code which has the number of lines exceed this value will dynamically cause two code block expansion buttons to appear, allowing the user to expand to full length and contract. This is useful when sharing code or scripts with tens or hundreds of lines where you wish to control how many are displayed. Under params in `config.toml` file, add a value as follows:
21 |
22 | ```yaml
23 | [params]
24 | ...
25 | codeMaxLines = 10 # Maximum number of lines to be shown by default across all articles.
26 | ...
27 | ```
28 |
29 | > If the value already exists, change it to the desired number. This will apply globally.
30 |
31 | If you need more granular control, this parameter can be overridden at the blog article level. Add the same value to your article frontmatter as follows:
32 |
33 | ```yaml
34 | ...
35 | codeMaxLines = 15 # Maximum number of lines to be shown in code blocks in this blog post.
36 | ...
37 | ```
38 |
39 | If `codeMaxLines` is specified both in `config.toml` and in the article frontmatter, the value specified in the article frontmatter will apply to the given article. In the above example, the global default is `10` and yet the article value is `15` so code blocks in this article will auto-collapse after 15 lines.
40 |
41 | If `codeMaxLines` is not specified anywhere, an internal default value of `100` will be assumed.
--------------------------------------------------------------------------------
/src/content/docs/compose/use-forestry-cms.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Use forestry CMS"
3 | description = ""
4 | weight = 3
5 | +++
6 |
7 | Do you prefer managing your site using a CMS? Or would you like to make it easier for someone (a non-techie, perhaps) in your team to make edits easily? If interested, follow along. Else, skip to the [next section](../overview/)
8 |
9 | Let's sync your site with forestry CMS.
10 |
11 | ## Prerequisites !!
12 |
13 | Obviously you ought to have __a github account__. This is where your website source will live. Basically, forestry will read from github and write (commmit) to your github repo.
14 |
15 | {{< tip "warning" >}}
16 | Gitlab or bitbucket will work too. Just check their [implementation here](https://forestry.io/docs/git-sync/gitlab/). Happy fishing.
17 | {{< /tip >}}
18 |
19 | ### Requirement 1 : A Forestry account
20 |
21 | Jump over to [forestry](https://bit.ly/forestry-account) and sign up for an account. Consider signing up using your github account. That way, you don't have to deal with passwords.
22 |
23 | ### Requirement 2: A Netlify account _(optional)_
24 |
25 | If you intend to host with something other than Netlify _e.g github pages_, please scroll on. Hosting with Netlify is a lot of fun though; I highly recommend it.
26 |
27 | ### Step 1 : Fork or Clone Compse theme
28 |
29 | First we will fork [this theme's](https://github.com/onweru/compose) template.
30 |
31 | ### Step 2 : Add your repository in Forestry
32 |
33 | {{< tip >}}
34 | The exampleSite already comes with prefilled default forestry settings. If you set up your site using [option 2](../getting-started/#option-2-recommended), look for a file `.forestry/settings.yml` and remove all `exampleSite/` strings from it.
35 | {{< /tip >}}
36 |
37 | Go to your [forestry](https://bit.ly/forestry-account) account and click on `import your site now`.
38 |
39 | 1. Choose `hugo`
40 | 2. `github` or `gitlab`. wherever your repo is at.
41 | 3. Select your repo
42 |
--------------------------------------------------------------------------------
/src/content/docs/clarity/blogging.md:
--------------------------------------------------------------------------------
1 | +++
2 | title="Blogging"
3 | +++
4 |
5 | ### Blog directory
6 |
7 | Edit the `config.toml` file and change the `mainSections` key. Values will be directories where the blogs reside.
8 |
9 | ```yaml
10 | [params]
11 | ...
12 | mainSections = ["posts", "docs", "blogs"]
13 | ...
14 | ```
15 |
16 | For more info, see the [Hugo docs](https://gohugo.io/functions/where/#mainsections).
17 |
18 | ### Mobile menu positioning
19 |
20 | The navigation menu when mobile browsing can be configured in `config.toml` to open right or left depending on preference. The "hamburger" menu icon will always display in the upper right hand corner regardless.
21 |
22 | ```yaml
23 | [params]
24 | ...
25 | mobileNavigation = "left" # Mobile nav menu will open to the left of the screen.
26 | ...
27 | ```
28 |
29 | ### Tags and Taxonomies
30 |
31 | #### Show number of tags
32 |
33 | The number of tags and taxonomies (including categories) that should be shown can be configured so that any more than this value will only be accessible when clicking the All Tags button. This is to ensure a large number of tags or categories can be easily managed without consuming excess screen real estate. Edit the `numberOfTagsShown` parameter and set accordingly.
34 |
35 | ```yaml
36 | [params]
37 | ...
38 | numberOfTagsShown = 14 # Applies for all other default & custom taxonomies. e.g categories, brands see https://gohugo.io/content-management/taxonomies#what-is-a-taxonomy
39 | ...
40 | ```
41 |
42 | #### Number of tags example
43 |
44 | 
45 |
46 |
47 |
48 | ### Table of contents
49 |
50 | Each article can optionally have a table of contents (TOC) generated for it based on top-level links. By configuring the `toc` parameter in the article frontmatter and setting it to `true`, a TOC will be generated only for that article. The TOC will then render under the featured image.
51 |
52 | #### Table of contents (TOC) example
53 |
54 | 
55 |
--------------------------------------------------------------------------------
/src/content/docs/compose/search.md:
--------------------------------------------------------------------------------
1 | +++
2 | description = ""
3 | title = "Search Function"
4 | weight = 7
5 | +++
6 |
7 | Firstly, ensure you have these lines inside your config.toml file
8 |
9 | ```toml
10 | [outputs]
11 | home = ["HTML", "RSS","JSON"]
12 | ```
13 |
14 | Compose implements `fuse.js` to enable search functionality. At the time of this writing, search on these theme takes either of this forms:
15 |
16 | ### 1. Passive search
17 |
18 | This occurs only when the user loads the search page i.e `/search/`. They can directly navigate to that url. Alternatively, the user can type you search query on the search field and click enter. They will be redirected to the search page which will contain matched results if any.
19 |
20 | ### 2. Live search
21 |
22 | This behaviour will be obvious as the user types a search query on the search field. All `valid search queries`, will yield a list of `quick links` or a simple `no matches found`. Else, the user will be prompted to continue typing.
23 |
24 | > Please note that the results under quick links will be a truncated list of the most relevant results. Only a maximum of 8 items will be returned. This number is pragmatic at best if not arbitrary. On the search page, the number is set to 12.
25 |
26 | Note that live search on the search page will behave differently than on the other pages. Nonetheles, the pages apply the same live search principle.
27 |
28 | > Hitting enter while typing on the search page will be moot as that page’s content will live update as you type in the search word / phrase.
29 |
30 | ### Customize search feedback labels
31 |
32 | Use the `i18n` files to do so.
33 |
34 |
42 |
43 | ### What is a valid search query
44 |
45 | A valid search query must be long enough. If the search query can be cast as a float, then it only need contain one or more characters.
46 |
47 | Else the search query must be at least 2 characters long.
48 |
49 |
--------------------------------------------------------------------------------
/src/content/docs/clarity/getting-started.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Getting started
3 | weight: 11
4 | ---
5 |
6 | ## Prerequisites
7 |
8 | Firstly, __ensure you have installed the [extended version of Hugo](https://github.com/gohugoio/hugo/releases)__. See installation steps from [Hugo's official docs](https://gohugo.io/getting-started/installing/).
9 |
10 | ## Getting up and running
11 |
12 | Read the [prerequisites](#prerequisites) above and verify you're using the extended version of Hugo. There are at least two ways of quickly getting started with Hugo and the VMware Clarity theme:
13 |
14 | ### Option 1 (recommended)
15 |
16 | Generate a new Hugo site and add this theme as a Git submodule inside your themes folder:
17 |
18 | ```bash
19 | hugo new site yourSiteName
20 | cd yourSiteName
21 | git init
22 | git submodule add https://github.com/chipzoller/hugo-clarity themes/hugo-clarity
23 | cp -a themes/hugo-clarity/exampleSite/* .
24 | ```
25 |
26 | Then run
27 |
28 | ```bash
29 | hugo server
30 | ```
31 |
32 | Hurray!
33 |
34 | ### Option 2 (Great for testing quickly)
35 |
36 | You can run your site directly from the `exampleSite`. To do so, use the following commands:
37 |
38 | ```bash
39 | git clone https://github.com/chipzoller/hugo-clarity
40 | cd hugo-clarity/exampleSite/
41 | hugo server --themesDir ../..
42 | ```
43 |
44 | > Although, option 2 is great for quick testing, it is somewhat problematic when you want to update your theme. You would need to be careful not to overwrite your changes.
45 |
46 | ### Option 3 (The new, most fun & painless approach)
47 |
48 | This option enables you to load this theme as a hugo module. It arguably requires the least effort to run and maintain in your website.
49 |
50 | First things first, ensure you have `go` binary [installed on your machine](https://golang.org/doc/install).
51 |
52 | ```bash
53 | git clone https://github.com/chipzoller/hugo-clarity.git clarity
54 | cd clarity/exampleSite/
55 | hugo mod init my-site
56 | ```
57 | Open config.toml file in your code editor, replace `theme = "hugo-clarity"` with `theme = ["github.com/chipzoller/hugo-clarity"]` or just `theme = "github.com/chipzoller/hugo-clarity"`.
58 |
59 | Hurray you can now run
60 |
61 | ```yaml
62 | hugo server
63 | ```
64 |
65 | To pull in theme updates, run `hugo mod get -u ./...` from the theme folder. If unsure, [learn how to update hugo modules](https://gohugo.io/hugo-modules/use-modules/#update-modules)
66 |
67 | > There [is more you could do with hugo modules](https://discourse.gohugo.io/t/hugo-modules-for-dummies/20758), but this will suffice for our use case here.
68 |
--------------------------------------------------------------------------------
/src/content/docs/compose/install-theme.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Install theme"
3 | weight: 2
4 | description: >
5 | This page tells you how to get started with the Compose theme.
6 | ---
7 |
8 | ### Prerequisites
9 |
10 | First ensure that you have hugo installed.
11 |
12 | You need a [recent **extended** version](https://github.com/gohugoio/hugo/releases) (we recommend version 0.61 or later) of [Hugo](https://gohugo.io/) to do local builds and previews of sites (like this one) that uses this theme.
13 |
14 | If you install from the release page, make sure to get the `extended` Hugo version, which supports [sass](https://sass-lang.com/documentation/file.SCSS_FOR_SASS_USERS.html); you may need to scroll down the list of releases to see it.
15 |
16 | For comprehensive Hugo documentation, see [gohugo.io](https://gohugo.io/).
17 |
18 | ## Run your site with compose theme
19 |
20 | You could go with the options right below.
21 |
22 | ### Option 1 (my favorite)
23 |
24 | This option enables you to load compose theme as a hugo module. First things first, ensure you have `go` binary [installed on your machine](https://golang.org/doc/install).
25 |
26 | ```bash
27 | git clone https://github.com/onweru/compose/
28 | cd compose/exampleSite/
29 | hugo server
30 | ```
31 |
32 | To pull in theme updates, run `hugo mod get -u ./...` from the theme folder. If unsure, [learn how to update hugo modules](https://gohugo.io/hugo-modules/use-modules/#update-modules)
33 |
34 | {{< tip >}}
35 | If you choose __Option 2__ or __Option 3__ below, ensure you edit [these lines in the config.toml file](https://github.com/onweru/compose/blob/b3e30e0816621223224897edc45eeeabd0d9cd16/exampleSite/config.toml#L4-L7) as advised on the comments
36 | {{< /tip >}}
37 |
38 | ### Option 2 (recommended)
39 |
40 | Generate a new Hugo site and add this theme as a Git submodule inside your themes folder:
41 |
42 | ```bash
43 | hugo new site yourSiteName
44 | cd yourSiteName
45 | git init
46 | git submodule add https://github.com/onweru/compose/ themes/compose
47 | cp -a themes/compose/exampleSite/* .
48 | ```
49 |
50 | Then run
51 |
52 | ```bash
53 | hugo server
54 | ```
55 |
56 | Hurray!
57 |
58 | ### Option 3 (Great for testing quickly)
59 |
60 | You can run your site directly from the `exampleSite`. To do so, use the following commands:
61 |
62 | ```bash
63 | git clone https://github.com/onweru/compose/
64 | cd compose/exampleSite/
65 | hugo server --themesDir ../..
66 | ```
67 |
68 | {{< tip >}}
69 | Although, option 3 is great for quick testing, it is somewhat problematic when you want to update your theme. You would need to be careful not to overwrite your changes.
70 | {{< /tip >}}
71 |
72 | Once set, jump over to the `config.toml` file and start [configuring](#configuration) your site.
73 |
74 |
--------------------------------------------------------------------------------
/src/content/docs/compose/customize.md:
--------------------------------------------------------------------------------
1 | +++
2 | description = "basic configuration"
3 | title = "Customize layouts & components"
4 |
5 | +++
6 | ### Shortcodes modifiers
7 |
8 | These modifiers are classes you can use with shortcodes to customize the look and feel of your layouts and components.
9 |
10 | #### Grid
11 |
12 | | modifier | space |
13 | | --- | --- |
14 | | grid-2 | 2 columns |
15 | | grid-3 | 3 columns |
16 | | grid-4 | 4 columns |
17 |
18 | #### Spacing
19 |
20 | | modifier | space |
21 | | --- | --- |
22 | | mt-1 | 1.5rem top margin |
23 | | mt-2 | 3rem top margin |
24 | | mt-3 | 4.5rem top margin |
25 | | mt-4 | 6rem top margin |
26 |
27 | > use pt-1 \~ pt-4 for top padding
28 |
29 | | modifier | space |
30 | | --- | --- |
31 | | mb-1 | 1.5rem bottom margin |
32 | | mb-2 | 3rem bottom margin |
33 | | mb-3 | 4.5rem bottom margin |
34 | | mb-4 | 6rem bottom margin |
35 |
36 | > use pb-1 \~ pb-4 for bottom padding
37 |
38 | ### How do I disable dark mode?
39 |
40 | Under `params` add `enableDarkMode = false` to your `config.toml` file. If your site is based on the exampleSite, the value is already included; you only need to uncomment it.
41 |
42 | > The user will still have the option to activate dark mode, if they so wish through the UI
43 |
44 | ### How do I change the theme color?
45 |
46 | If the theme is a git submodule, you can copy the file `assets/sass/_variables.sass` from the theme into your own site.
47 | The location must be exactly the same as in the theme, so put it in `YourFancySite/assets/sass/`.
48 | You can then edit the file to customize the theme color in your site without having to modify the theme itself.
49 |
50 | ### How can I change the address bar color on mobile devices?
51 |
52 | Just put the following line in the `[params]` section in your `config.toml` file (and of course change the color):
53 |
54 | ```toml
55 | metaThemeColor = "#123456"
56 | ```
57 |
58 | ### How do I add custom styles, scripts, meta tags e.t.c
59 |
60 | Use hooks. Ideally, you should not override the them directly.
61 |
62 | Instead, you should duplicate [these files](https://github.com/onweru/compose/tree/master/layouts/partials/hooks) at the root of you site directory.
63 |
64 | 1. layouts/partials/hooks/head.html
65 | 2. layouts/partials/hooks/scripts.html
66 |
67 | The contents of the first file will be attached just before the `` tag.
68 |
69 | The contents of the second file will be attached just before the `