Update and run autoprefixer (#601)

Co-authored-by: kodiakhq[bot] <kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

.github/.kodiak.toml

@@ -0,0 +1,19 @@
+
+# .kodiak.toml
+version = 1
+[merge]
+method = "squash" # default: "merge"
+delete_branch_on_merge = true # default: false
+optimistic_updates = true # default: true
+prioritize_ready_to_merge = true # default: false
+
+[merge.message]
+title = "pull_request_title" # default: "github_default"
+body = "github_default" # default: "github_default"
+strip_html_comments = true # default: false
+
+[update]
+always = true # default: false
+
+[approve]
+auto_approve_usernames = ["hossainemruz"]

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,37 @@
+---
+name: Bug
+about: File a bug report.
+title: 'bug'
+---
+
+## Expected Behavior
+<!--- Tell us what should happen -->
+
+## Current Behavior
+<!--- Tell us what happens instead of the expected behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+
+## Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+### Screenshots
+<!--- Provide any screenshots or links to deployments -->
+
+### Browsers Affected
+<!-- Check all that apply -->
+- [ ] Chrome
+- [ ] Firefox
+- [ ] Edge
+- [ ] Safari 11
+- [ ] Safari 10
+- [ ] IE 11
+
+## Detailed Description
+<!--- Provide a detailed description of the change or addition you are proposing -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,30 @@
+---
+name: Feature Request
+about: File a Feature Request.
+title: 'Feature Request'
+---
+
+<!---
+Before filing an issue, please review the following:
+  Existing Features: https://github.com/hossainemruz/toha#features
+  Project Roadmap: https://github.com/hossainemruz/toha#project-roadmap
+-->
+
+### Describe the solution you'd like
+
+<!--
+  Provide a clear and concise description of what you want to happen.
+-->
+
+### Describe alternatives you've considered
+
+<!--
+  Let us know about other solutions you've tried or researched.
+-->
+
+### Additional context
+
+<!--
+  Is there anything else you can add about the proposal?
+  You might want to link to related issues here, if you haven't already.
+-->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,9 @@
+---
+name: Question
+about: Ask a general question.
+---
+
+<!--- Use this template for general questions. For bug reports or feature requests, please use those templates -->
+
+### Question
+<!--- Insert your question here. Please provide as much detail as possible. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+### Issue
+<!--- Insert a link to the associated github issue here. -->
+
+### Description
+
+<!-- Insert details about what the changes being proposed are. -->
+
+### Test Evidence
+
+<!-- Provide screenshot evidence and/or testing steps to validate the proposed changes. -->

.github/dependabot.yml

@@ -0,0 +1,13 @@
+# Update dependencies
+
+version: 2
+updates:
+# Update the Github Action  versions
+- package-ecosystem: "github-actions"
+  directory: "/"
+  schedule:
+    interval: "daily"
+  labels:
+  - "dependencies"
+  - "automerge"
+  - "enhancement"

.github/release-drafter.yml

@@ -7,27 +7,35 @@ template: |
   $CHANGES
 
   This release note has been generated automatically by [Release Drafter](https://github.com/marketplace/actions/release-drafter).
+
 categories:
-  - title: 'Breaking Changes'
-    label: 'breaking-change'
-  - title: 'New Features & Enhancements'
-    labels:
-    - 'feature'
-    - 'enhancement'
-  - title: 'Bug Fixes'
-    labels:
-      - 'bug'
-      - 'bug-fix'
+- title: 'Breaking Changes'
+  label: 'breaking-change'
+
+- title: 'New Features & Enhancements'
+  labels:
+  - 'feature'
+  - 'enhancement'
+
+- title: 'Translations'
+  label: 'translation'
+
+- title: 'Bug Fixes'
+  labels:
+  - 'bug'
+  - 'bug-fix'
 
 version-resolver:
   major:
     labels:
-      - 'breaking'
+    - 'breaking-change'
+    - 'breaking'
   minor:
     labels:
-      - 'feature'
-      - 'enhancement'
+    - 'feature'
+    - 'enhancement'
+    - 'translation'
   patch:
     labels:
-      - 'bug'
-      - 'bug-fix'
+    - 'bug'
+    - 'bug-fix'

.github/workflows/autoprefixer.yml

@@ -2,34 +2,34 @@ name: Autoprefixer
 on:
   push:
     branches:
-      - master
+      - main
 jobs:
   autoprefixer:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout to latest commit
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
 
       - name: Setup Node
-        uses: actions/setup-node@v1
+        uses: actions/setup-node@v3
         with:
-          node-version: "12.x"
+          node-version: "15.x"
 
       - name: Run autoprefixer
         run: |
-          npm install postcss-cli autoprefixer --save-dev
+          npm install postcss postcss-cli autoprefixer --save-dev
           npm run autoprefixer
 
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v3
+        uses: peter-evans/create-pull-request@v4
         with:
           branch: autoprefixer
           branch-suffix: timestamp
           commit-message: add vendor specific css prefixes
-          title: "Add vendor specific CSS prefixes"
+          title: "Update and run autoprefixer"
           body: |
-            This PR adds vendor specific CSS prefixes using [postcss/autoprefixer](https://github.com/postcss/autoprefixer).
+            This PR runs [postcss/autoprefixer](https://github.com/postcss/autoprefixer) to update vendor specific CSS prefixes.
 
             >This PR has been created automatically by Github Action [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request).
-          labels: enhancement
+          labels: "enhancement,automerge"
           reviewers: hossainemruz

.github/workflows/build.yml

@@ -0,0 +1,28 @@
+name: Run Build
+
+# Run action on pull request event
+on: [pull_request]
+
+
+jobs:
+  build:
+    runs-on: ubuntu-18.04
+    steps:
+    # checkout to the commit that has been pushed
+    - uses: actions/checkout@v2.4.0
+      with:
+        submodules: true  # Fetch Hugo themes (true OR recursive)
+        fetch-depth: 0    # Fetch all history for .GitInfo and .Lastmod
+
+    # install Hugo
+    - name: Setup Hugo
+      uses: peaceiris/actions-hugo@v2.5.0
+      with:
+        hugo-version: 'latest'
+        extended: true
+
+    # build website
+    - name: Create Config
+      run: touch config.toml
+    - name: Build
+      run: hugo --minify

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,71 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ main ]
+  schedule:
+    - cron: '19 16 * * 2'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'javascript' ]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
+        # Learn more:
+        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v3
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v2
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+        # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v2
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 https://git.io/JvXDl
+
+    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+    #    and modify them (or add more) to build your code if your project
+    #    uses a compiled language
+
+    #- run: |
+    #   make bootstrap
+    #   make release
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v2

.github/workflows/draft-release.yml

@@ -1,14 +1,15 @@
 name: Release Drafter
-
+# Run action on push in mater branch
 on:
   push:
     branches:
-      - master
+    - main
 
 jobs:
   update_release_draft:
     runs-on: ubuntu-latest
     steps:
-      - uses: release-drafter/release-drafter@master
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    # Create/Update release draft
+    - uses: release-drafter/release-drafter@v5.20.0
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/enforce-label.yml

@@ -0,0 +1,13 @@
+name: Enforce Labels
+
+on:
+  pull_request:
+    types: [labeled, unlabeled, opened, edited, synchronize]
+jobs:
+  enforce-label:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: yogevbd/enforce-label-action@2.2.2
+      with:
+        REQUIRED_LABELS_ANY: "automerge,breaking-change,bug-fix,enhancement,feature,translation"
+        REQUIRED_LABELS_ANY_DESCRIPTION: "The PR must have at least one these labels: ['automerge','breaking-change','bug-fix','enhancement','feature','translation']"

.github/workflows/md-link-checker.yml

@@ -0,0 +1,13 @@
+name: Check Markdown links
+
+# Run action on pull request event
+on: [pull_request]
+
+jobs:
+  markdown-link-check:
+    runs-on: ubuntu-latest
+    steps:
+    # checkout to latest commit
+    - uses: actions/checkout@v3
+    # run markdown linter
+    - uses: gaurav-nelson/github-action-markdown-link-check@1.0.14

.github/workflows/project-automation-issue.yaml

@@ -0,0 +1,150 @@
+name: Project Automation (Issue)
+on:
+  issues:
+    types:
+      - opened
+      - reopened
+      - closed
+      - labeled
+      - unlabeled
+jobs:
+  issue_automation:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+          ORGANIZATION: hugo-toha
+          PROJECT_NUMBER: 4
+        run: |
+          gh api graphql --header 'GraphQL-Features: projects_next_graphql' -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectNext(number: $number) {
+                  id
+                  fields(first:20) {
+                    nodes {
+                      id
+                      name
+                      settings
+                    }
+                  }
+                }
+              }
+            }' -f org="$ORGANIZATION" -F number=$PROJECT_NUMBER > project_data.json
+
+           echo 'PROJECT_ID='$(jq -r '.data.organization.projectNext.id' project_data.json) >> $GITHUB_ENV
+
+          # Read the ID of the "Type" field options
+          echo 'TYPE_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Type") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'PROJECT_ID='$(jq -r '.data.organization.projectNext.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Type") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_BUG='$(jq -r '.data.organization.projectNext.fields.nodes[] | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Bug")             |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_FEATURE='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Feature") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_ENHANCEMENT='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Enhancement") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_DOCUMENTATION='$(jq -r '.data.organization.projectNext.fields.nodes[]  | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Documentation")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_TRANSLATION='$(jq -r '.data.organization.projectNext.fields.nodes[]  | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Translation")    |.id' project_data.json) >> $GITHUB_ENV
+
+          # Read the id of the "Status" field options
+          echo 'STATUS_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Status") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_TODO='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Todo")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_IN_PROGRESS='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="In Progress")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_READY_FOR_REVIEW='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Ready for Review")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_DONE='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Done")    |.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add Issue to project
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+          ISSUE_ID: ${{ github.event.issue.node_id }}
+        run: |
+          item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $issue:ID!) {
+              addProjectNextItem(input: {projectId: $project, contentId: $issue}) {
+                projectNextItem {
+                  id
+                }
+              }
+            }' -f project="$PROJECT_ID" -f issue="$ISSUE_ID" --jq '.data.addProjectNextItem.projectNextItem.id')"
+
+          echo 'ITEM_ID='$item_id >> $GITHUB_ENV
+
+      - name: Export Labels
+        env:
+          ISSUE_DATA: ${{ toJson(github.event.issue) }}
+        run: |
+          echo 'LABELS='$(echo "$ISSUE_DATA" | jq -r '[.labels[].name] | join(" ")') >> $GITHUB_ENV
+
+      - name: Set "Type" field
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+        run: |
+          # Only execute this step if the Issue contains at least one label
+          if [ "${#LABELS[@]}" -gt 0 ]; then
+
+            # Let by default the type is "Bug"
+            OPTION_ID=$TYPE_BUG
+
+            # If it has "feature" label then set the type to "Feature"
+            if [[ "${LABELS[*]}" =~ "feature" ]]; then
+              OPTION_ID=$TYPE_FEATURE
+            fi
+
+            # If it has "enhancement" label then set the type to "Enhancement"
+            if [[ "${LABELS[*]}" =~ "enhancement" ]]; then
+              OPTION_ID=$TYPE_ENHANCEMENT
+            fi
+
+            # If it has "documentation" label then set the type to "Documentation"
+            if [[ "${LABELS[*]}" =~ "documentation" ]]; then
+              OPTION_ID=$TYPE_DOCUMENTATION
+            fi
+
+            # If it has "translation" label then set the type to "Translation"
+            if [[ "${LABELS[*]}" =~ "translation" ]]; then
+              OPTION_ID=$TYPE_TRANSLATION
+            fi
+
+            # Set the "Type" field to appropriate option
+            gh api graphql -f query='
+              mutation ($project: ID!, $item: ID!, $field: ID!, $opt_id: String!) {
+                updateProjectNextItemField(input: {
+                  projectId: $project
+                  itemId: $item
+                  fieldId: $field
+                  value: $opt_id
+                }) {
+                  projectNextItem {
+                    id
+                  }
+                }
+              }' -f project="$PROJECT_ID" -f item="$ITEM_ID" -f field="$TYPE_ID" -f opt_id="$OPTION_ID" --silent
+          fi
+
+      - name: Set "Status" field
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+        run: |
+          STATE=${{github.event.issue.state}}
+
+          echo "State: $STATE"
+
+          OPTION_ID=$STATUS_TODO
+
+          if [[ "${STATE}" == "closed" ]]
+          then
+            OPTION_ID=$STATUS_DONE
+          fi
+
+          gh api graphql -f query='
+            mutation ($project: ID!, $item: ID!, $field: ID!, $status_id: String!) {
+              updateProjectNextItemField(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $field
+                value: $status_id
+              }) {
+                projectNextItem {
+                  id
+                }
+              }
+            }' -f project="$PROJECT_ID" -f item="$ITEM_ID" -f field="$STATUS_ID" -f status_id="$OPTION_ID" --silent

.github/workflows/project-automation-pr.yaml

@@ -0,0 +1,219 @@
+name: Project Automation (PR)
+on:
+  pull_request:
+    types:
+      - opened
+      - ready_for_review
+      - reopened
+      - review_requested
+      - closed
+      - labeled
+      - unlabeled
+      - synchronize
+jobs:
+  pr_automation:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+          ORGANIZATION: hugo-toha
+          PROJECT_NUMBER: 4
+        run: |
+          gh api graphql --header 'GraphQL-Features: projects_next_graphql' -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectNext(number: $number) {
+                  id
+                  fields(first:20) {
+                    nodes {
+                      id
+                      name
+                      settings
+                    }
+                  }
+                }
+              }
+            }' -f org="$ORGANIZATION" -F number=$PROJECT_NUMBER > project_data.json
+
+          echo 'PROJECT_ID='$(jq -r '.data.organization.projectNext.id' project_data.json) >> $GITHUB_ENV
+
+          # Read the ID of the "Type" field options
+          echo 'TYPE_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Type") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'PROJECT_ID='$(jq -r '.data.organization.projectNext.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Type") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_BUG='$(jq -r '.data.organization.projectNext.fields.nodes[] | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Bug")             |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_FEATURE='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Feature") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_ENHANCEMENT='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Enhancement") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_DOCUMENTATION='$(jq -r '.data.organization.projectNext.fields.nodes[]  | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Documentation")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'TYPE_TRANSLATION='$(jq -r '.data.organization.projectNext.fields.nodes[]  | select(.name== "Type") |.settings | fromjson.options[] | select(.name=="Translation")    |.id' project_data.json) >> $GITHUB_ENV
+
+          # Read the id of the "Status" field options
+          echo 'STATUS_ID='$(jq -r '.data.organization.projectNext.fields.nodes[]     | select(.name== "Status") |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_TODO='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Todo")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_IN_PROGRESS='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="In Progress")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_READY_FOR_REVIEW='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Ready for Review")    |.id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_DONE='$(jq -r '.data.organization.projectNext.fields.nodes[]   | select(.name== "Status") |.settings | fromjson.options[] | select(.name=="Done")    |.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add PR to project
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+          PR_ID: ${{ github.event.pull_request.node_id }}
+        run: |
+          item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $pr:ID!) {
+              addProjectNextItem(input: {projectId: $project, contentId: $pr}) {
+                projectNextItem {
+                  id
+                }
+              }
+            }' -f project="$PROJECT_ID" -f pr="$PR_ID" --jq '.data.addProjectNextItem.projectNextItem.id')"
+
+          echo 'ITEM_ID='$item_id >> $GITHUB_ENV
+
+      - name: Export Labels
+        env:
+          PR_DATA: ${{ toJson(github.event.pull_request) }}
+        run: |
+          echo 'LABELS='$(echo "$PR_DATA" | jq -r '[.labels[].name] | join(" ")') >> $GITHUB_ENV
+
+      - name: Set "Type" field
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+        run: |
+          # Only execute this step if the PR contains at least one label
+          if [ "${#LABELS[@]}" -gt 0 ]; then
+
+            # Let by default the type is "Bug"
+            OPTION_ID=$TYPE_BUG
+
+            # If it has "feature" label then set the type to "Feature"
+            if [[ "${LABELS[*]}" =~ "feature" ]]; then
+              OPTION_ID=$TYPE_FEATURE
+            fi
+
+            # If it has "enhancement" label then set the type to "Enhancement"
+            if [[ "${LABELS[*]}" =~ "enhancement" ]]; then
+              OPTION_ID=$TYPE_ENHANCEMENT
+            fi
+
+            # If it has "documentation" label then set the type to "Documentation"
+            if [[ "${LABELS[*]}" =~ "documentation" ]]; then
+              OPTION_ID=$TYPE_DOCUMENTATION
+            fi
+
+            # If it has "translation" label then set the type to "Translation"
+            if [[ "${LABELS[*]}" =~ "translation" ]]; then
+              OPTION_ID=$TYPE_TRANSLATION
+            fi
+
+            # Set the "Type" field to appropriate option
+            gh api graphql -f query='
+              mutation ($project: ID!, $item: ID!, $field: ID!, $opt_id: String!) {
+                updateProjectNextItemField(input: {
+                  projectId: $project
+                  itemId: $item
+                  fieldId: $field
+                  value: $opt_id
+                }) {
+                  projectNextItem {
+                    id
+                  }
+                }
+              }' -f project="$PROJECT_ID" -f item="$ITEM_ID" -f field="$TYPE_ID" -f opt_id="$OPTION_ID" --silent
+          fi
+
+      - name: Set "Status" field
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+        run: |
+          MERGED=${{github.event.pull_request.merged}}
+          STATE=${{github.event.pull_request.state}}
+          REVIEWERS=${{github.event.pull_request.requested_reviewers}}
+          DRAFT=${{github.event.pull_request.draft}}
+
+          echo "Merged: $MERGED"
+          echo "State: $STATE"
+          echo "Draft: $DRAFT"
+          echo "Reviewer: $REVIEWER"
+
+          OPTION_ID=$STATUS_TODO
+
+          if [[ ("${MERGED}" == "true") || ("${STATE}" == "closed") ]]
+          then
+            OPTION_ID=$STATUS_DONE
+          elif [[ ${#REVIEWERS[@]} -gt 0 ]]
+          then
+            OPTION_ID=$STATUS_READY_FOR_REVIEW
+          else
+            OPTION_ID=$STATUS_IN_PROGRESS
+          fi
+
+          # Expose the OPTION_ID so that it can be used in later steps
+          echo 'PR_STATUS='$OPTION_ID >> $GITHUB_ENV
+
+          gh api graphql -f query='
+            mutation ($project: ID!, $item: ID!, $field: ID!, $status_id: String!) {
+              updateProjectNextItemField(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $field
+                value: $status_id
+              }) {
+                projectNextItem {
+                  id
+                }
+              }
+            }' -f project="$PROJECT_ID" -f item="$ITEM_ID" -f field="$STATUS_ID" -f status_id="$OPTION_ID" --silent
+
+      - name: Find Linked Issues
+        id: linked_issues
+        uses: hossainemruz/linked-issues@main
+        with:
+          pr_url: ${{github.event.pull_request.html_url}}
+          format: IssueNumber
+
+      - name: Update Linked Issues Status
+        env:
+          GITHUB_TOKEN: ${{secrets.PROJECT_AUTOMATION}}
+        run: |
+          declare -a issues=(${{ steps.linked_issues.outputs.issues }})
+
+          # Loop through the every issues and update their Status to same as the PR Status
+          for i in "${issues[@]}"
+          do
+            # Find the Issue ID
+            ISSUE_ID="$(gh api graphql -f query='
+              query($owner: String!, $name: String!, $issue_number: Int!) {
+                repository(owner: $owner, name: $name) {
+                  issue(number: $issue_number) {
+                    id
+                  }
+                }
+              }' -f owner="${{github.event.pull_request.head.repo.owner.login}}" -f name="${{github.event.pull_request.head.repo.name}}" -F issue_number=$i --jq='.data.repository.issue.id')"
+
+            # Find the id of the Issue at the project board
+            item_id="$( gh api graphql -f query='
+              mutation($project:ID!, $pr:ID!) {
+                addProjectNextItem(input: {projectId: $project, contentId: $pr}) {
+                  projectNextItem {
+                    id
+                  }
+                }
+              }' -f project="$PROJECT_ID" -f pr="$ISSUE_ID" --jq '.data.addProjectNextItem.projectNextItem.id')"
+
+            # Update the Issue Status
+            gh api graphql -f query='
+            mutation ($project: ID!, $item: ID!, $field: ID!, $status_id: String!) {
+              updateProjectNextItemField(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $field
+                value: $status_id
+              }) {
+                projectNextItem {
+                  id
+                }
+              }
+            }' -f project="$PROJECT_ID" -f item="$item_id" -f field="$STATUS_ID" -f status_id="$PR_STATUS" --silent
+          done

.gitignore

@@ -1,2 +1,5 @@
 .vscode/
 node_modules/
+.DS_Store
+.history/
+resources/

README.md

@@ -1,57 +1,111 @@
 # Toha
 
+[![Netlify Status](https://api.netlify.com/api/v1/badges/b1b93b02-f278-440b-ae1b-304e9f4c4ab5/deploy-status)](https://app.netlify.com/sites/toha/deploys)
+[![Build Status](https://img.shields.io/endpoint.svg?url=https%3A%2F%2Factions-badge.atrox.dev%2Fhugo-toha%2Ftoha%2Fbadge%3Fref%3Dmain&style=flat)](https://actions-badge.atrox.dev/hugo-toha/toha/goto?ref=main)
+![Repository Size](https://img.shields.io/github/repo-size/hugo-toha/toha)
+![Lines of Codes](https://img.shields.io/tokei/lines/github.com/hugo-toha/toha)
+![Contributor](https://img.shields.io/github/contributors/hugo-toha/toha)
+![Latest Release](https://img.shields.io/github/v/release/hugo-toha/toha?include_prereleases)
+![Last Commit](https://img.shields.io/github/last-commit/hugo-toha/toha)
+![Open Issues](https://img.shields.io/github/issues/hugo-toha/toha?color=important)
+![Open Pull Requests](https://img.shields.io/github/issues-pr/hugo-toha/toha?color=yellowgreen)
+![License](https://img.shields.io/github/license/hugo-toha/toha)
+![Security Headers](https://img.shields.io/security-headers?url=https%3A%2F%2Fhugo-toha.github.io%2F)
+[![This project is using Percy.io for visual regression testing.](https://percy.io/static/images/percy-badge.svg)](https://percy.io/b7cb60ab/hugo-toha.github.io)
+
 A [Hugo](https://gohugo.io/) theme for a personal portfolio with minimalist design and responsiveness.
 
-![Thumbnail](https://github.com/hossainemruz/toha/blob/master/images/tn.png)
+![Thumbnail](https://raw.githubusercontent.com/hugo-toha/toha/main/images/screenshot.png)
 
-Example Site: [Toha Example Site](https://toha.netlify.app)
+- **Example Site:** [hugo-toha.github.io](https://hugo-toha.github.io)
+- **Documentation:** [toha-guides.netlify.app](https://toha-guides.netlify.app/posts)
 
 ## Features
 
 - Minimalist Design
 - Fully Responsive
-- Carefully designed cards
-- Great Experience timeline
-- Achievement gallery
-- Sidebar to categorize posts
+- Multiple Language Support
+- Carefully Designed Cards
+- Experience Timeline
+- Achievement Gallery
+- Sidebar to Categorize the Posts
 - Short Codes
-- Google Analytics Support
-- Disqus Comment Support
+- Analytics Support
+  - GoatCounter
+  - counter.dev
+  - Google Analytics
+- Comment Support
+  - [Disqus](https://disqus.com/)
+  - [Valine](https://valine.js.org/)
+  - [Uttarances](https://utteranc.es/)
+  - [Giscus](https://giscus.app/)
 
-For more details about the features please visit [here](https://toha.netlify.app/posts/features/features/).
+For more details about the features please visit [here](https://toha-guides.netlify.app/posts/features/).
+
+## Available Translations
+
+- English
+- বাংলা
+- Français
+- Indonesian
+- Deutsch
+- Español
+- 简体中文
+- हिन्दी
+- Italiano
+- 日本語
+- 한국어
+- русский
+- suomi
+- Tiếng Việt
+
+To know more about how to translate your site, please visit [here](https://toha-guides.netlify.app/posts/translation/). Follow, the data and post format from this [example site](https://hugo-toha.github.io).
+
+## Screenshots
+
+Here are few screenshots from the [example site](https://hugo-toha.github.io).
+
+##### Home Page Sections
+
+![Home Page Sections](https://raw.githubusercontent.com/hugo-toha/toha/main/images/about.png)
+
+##### List Page
+
+![List Page](https://raw.githubusercontent.com/hugo-toha/toha/main/images/list.png)
+
+##### Reading Page
+
+![Reading Page](https://raw.githubusercontent.com/hugo-toha/toha/main/images/single.png)
 
 ## Requirements
 
-- Hugo Version 0.68.0 or higher
+- Hugo Version 0.87.0 or higher
 
-## Installation
+## Usage
 
-- Create your site if you haven't already
+In order to use this theme, follow the following steps:
+
+#### Add theme as git submodule
+
+At first, add [Toha](https://github.com/hugo-toha/toha) theme as git submodule to your hugo-site.
 
 ```console
-hugo new site my-site -f=yaml
-cd my-site
-git init
+$ git submodule add https://github.com/hugo-toha/toha.git themes/toha
 ```
 
-- Add the theme as git sub-module
+> Don't use SSH URL of the theme during adding as git sub-module. Also, don't clone the theme in your `themes` directory using `git clone`. They don't work well with Github Action or Netlify.
 
-```console
-git submodule add https://github.com/hossainemruz/toha.git themes/toha
-```
+If you don't already have a hugo site, create one by following the step-by-step guide from [here](https://toha-guides.netlify.app/posts/getting-started/prepare-site/).
 
->Don't use SSH URL of the theme during adding as git sub-module. Also, don't clone the theme in your `themes` directory using `git clone`. They don't work well with Github Action or Netlify.
+#### Configuring Site
 
-If you want to customize the theme templates, then fork it and use the fork as your theme.
-
-## Configuration
-
-Configure your `config.yaml` file of your site as below:
+Now, configure your site to use `toha` theme by adding the following configuration in `config.yaml` file of your site.
 
 ```yaml
-baseURL: http://example.org/
+baseURL: https://hugo-toha.github.io
+
 languageCode: en-us
-title: "Toha"
+title: "John's Blog"
 theme: "toha"
 
 # Manage languages
@@ -60,102 +114,89 @@ languages:
   en:
     languageName: English
     weight: 1
-  fr:
-    languageName: Français
-    weight: 2
-  bn:
-    languageName: বাংলা
-    weight: 3
 
-# Force a locale to be use, really useful to develop the application ! Should be commented in production, the "weight" should rocks.
-# DefaultContentLanguage: fr
-
-# Allow raw html in markdown file
+# Control TOC depth
 markup:
-  goldmark:
-    renderer:
-      unsafe: true
   tableOfContents:
     startLevel: 2
     endLevel: 6
     ordered: false
 
-# Enable Google Analytics
-googleAnalytics: UA-XXXXXXXXX-X
-
-# Enable Disqus forum
-disqusShortname: does-not-exist
+# At least HTML and JSON are required for the main HTML content and
+# client-side JavaScript search
+outputs:
+  home:
+  - HTML
+  - RSS
+  - JSON
 
 # Enable global emoji support
 enableEmoji: true
 
-# Custom parameters
+# Site parameters
 params:
-  # background image of the landing page
-  background: "images/background.jpg"
+  # GitHub repo URL and branch of your site
+  gitRepo: https://github.com/hugo-toha/hugo-toha.github.io
+  gitBranch: main
 
-  # Provide logos for your site. The inverted logo will be used in the initial
-  # transparent navbar and the main logo will be used in the non-transparent navbar.
-  # It will be default to the theme logos if not provided.
-  logo:
-    main: assets/images/main-logo.png
-    inverted: assets/images/inverted-logo.png
-    favicon: assets/images/favicon.png
-
-  # GitHub repo URL of your site
-  gitRepo: https://github.com/hossainemruz/toha-example-site
-
-  # specify whether you want to write blog post or not
+  # specify whether you want to write some blog posts or not
   enableBlogPost: true
 
   # specify whether you want to show Table of Contents in reading page
   enableTOC: true
 
-  # Provide newsletter configuration. This feature hasn't been implemented yet.
-  # Currently, you can just hide it from the footer.
+  # Provide newsletter configuration. 
+  # This feature has been implemented for Mailchimp only for now.
+  # You can also hide it from the footer.
   newsletter:
+    # specify whether you want to display the newsletter form 
     enable: true
+    # specify which newsletter provider you want to use
+    provider: mailchimp
+    # specify the target URL for the subscription form
+    mailchimpURL: https://github.us1.list-manage.com/subscribe/post?u=19de52a4603135aae97163fd8&id=094a24c76e
 ```
 
-You can just copy the content for `config.yaml` files from `theme/toha/exampleSite/config.yaml`.
+Don't forget to update `title`, `baseURL`, and `gitRepo` fields with your own information. To know about more available configuration options, please visit [here](https://toha-guides.netlify.app/posts/configuration/site-parameters/).
 
-If you want to customize the any of the CSS styles on your site, create a
-`static/assets/css/style.css` file and add any custom CSS there.
+#### Running Locally
 
-## Usage
-
-Run your hugo site with this theme.
+Now, you can run your hugo site with `toha` theme locally with the following command:
 
 ```console
-hugo server -w
+$ hugo server --theme toha --watch
 ```
 
-When you first run your site, it will start with the default parameters. It should look similar to the [example site](https://toha.netlify.app) except it will not have any sections in the homepage. Those sections are added via some data files.
-
-You can configure your site by following the step by step guides from [here](https://toha.netlify.app/posts/configuration/).
+When you run your site for first time, it will start with the default parameters. It should look similar to the [example site](https://hugo-toha.github.io). However, it will not have any sections in the homepage as we haven't configured them yet. You can configure your site by following the guides from [here](https://toha-guides.netlify.app/posts/configuration/).
 
 ## Shortcodes
 
 Here, are some handy shortcodes you can use with this theme.
 
-- [img](https://toha.netlify.app/posts/short-codes/img/)
-- [split](https://toha.netlify.app/posts/short-codes/split/)
-- [vs](https://toha.netlify.app/posts/short-codes/vs/)
-- [alert](https://toha.netlify.app/posts/short-codes/alert/)
+- [Alert](https://toha-guides.netlify.app/posts/shortcodes/#alert)
+- [Image](https://toha-guides.netlify.app/posts/shortcodes/#image)
+- [Split](https://toha-guides.netlify.app/posts/shortcodes/#split)
+- [Vertical Space](https://toha-guides.netlify.app/posts/shortcodes/#vertical-space)
+- [Video](https://toha-guides.netlify.app/posts/shortcodes/#video)
+- [Mermaid](https://hugo-toha.github.io/posts/shortcodes/#mermaid)
 
 ## Project Roadmap
 
 Here, are the current plan and progress of various components of this theme. The components will be prioritized based on users requests.
 
-### Sections
+### 1. Portfolio Mode
+
+Here is the check list for portfolio mode,
 
 - [x] **Home**
+
   - [x] Configurable Background
   - [x] Author Image
   - [x] Greeting
   - [x] Typing Carousel
 
 - [x] **About**
+
   - [x] Name and Designation
   - [x] Summary
     - [x] Markdown Support
@@ -165,27 +206,40 @@ Here, are the current plan and progress of various components of this theme. The
   - [x] Soft Skills Indicator
 
 - [x] **Skills**
+
   - [x] Skill Cards
   - [x] Markdown Support
 
 - [x] **Experiences**
+
   - [x] Designation
   - [x] Timeline
   - [x] Company Overview
   - [x] Responsibilities
 
-- [ ] **Projects**
+- [x] **Projects**
+
   - [x] Category Filter
-  - [ ] Project Card
+  - [x] Project Card
     - [x] Overview
       - [x] Markdown Support
     - [x] Github Stars
     - [x] External URL Support
-    - [ ] Technology Tags
+    - [x] Technology Tags
 
 - [x] **Recent Posts**
 
+- [x] **Academic Career**
+
+  - [x] Degree
+  - [x] Institution
+  - [x] Timeline
+  - [x] Taken Courses
+  - [x] CGPA
+  - [x] Extracurricular Activities
+
 - [ ] **Publications**
+
   - [ ] Category Filter
   - [ ] Card
   - [ ] Abstract
@@ -194,35 +248,61 @@ Here, are the current plan and progress of various components of this theme. The
   - [ ] Links
   - [ ] Gallery
 
-- [ ] **Accomplishment / Courses**
-  - [ ] Overview
-  - [ ] Certificate
+- [x] **Accomplishment / Courses**
+
+  - [x] Overview
+  - [x] Certificate
 
 - [x] **Achievements Gallery**
   - [x] Image
   - [x] Summary
 
-### List Page
+### 2. Blog Mode
 
-- [x] Post Cards
-- [x] Sidebar
-- [x] Pagination
+Here is the checklist for blog mode,
 
-### Reading Page
+- [ ] **Dedicated Home page**
 
-- [x] Hero Image
-- [x] Author Information
-- [x] Next & Previous Page Navigation
-- [x] `Improve This Page` Button
-- [x] Disqus Comment
-- [x] Option to navigate to list page
+- [x] **List Page**
 
-### Tracking and Comments
+  - [x] Post Cards
+  - [x] Sidebar
+  - [x] Pagination
+
+- [x] **Reading Page**
+
+  - [x] Hero Image
+  - [x] Author Information
+  - [x] Sidebar
+  - [x] Table of Contents
+  - [x] Next & Previous Page Navigation
+  - [x] `Improve This Page` Button
+  - [x] Disqus Comment
+
+### 3. Documentation Mode
+
+Here is the check list for documentation mode,
+
+- [ ] **Dedicated Home Page**
+- [ ] **Doc Page**
+  - [ ] Redesign sidebar
+  - [ ] Redesign TOC menu
+  - [ ] Search Capability
+
+### 4. Note Mode
+
+- [ ] **Dedicated Home Page**
+- [ ] **Note Page**
+  - [x] Add note view
+  - [ ] Redesign sidebar
+  - [ ] Add search capability
+
+### 5. Tracking and Comments
 
 - [x] Google Analytics
 - [x] Disqus Comment
 
-### Shortcodes
+### 6. Shortcodes
 
 - [x] Image
 - [x] Split Page into Multiple Column
@@ -230,19 +310,75 @@ Here, are the current plan and progress of various components of this theme. The
 - [x] Alert
 - [ ] Figure & sub-figure
 - [ ] Tabs
+- [x] Notes
 
 ## Contributing
 
-You can contribute to this theme in various way. You can report a bug, file an feature request, send a PR, share your thoughts etc.
+You can contribute to this theme in various ways. You can report a [bug](https://github.com/hugo-toha/toha/issues/new?template=bug.md), file an [feature request](https://github.com/hugo-toha/toha/issues/new?template=feature_request.md), send a PR, [share your thoughts](https://github.com/hugo-toha/toha/issues/new?template=question.md) etc.
 
-Pull requests are most welcomed and I will be happy to review. Just follow the following principles:
+Pull requests are most welcome and I will be happy to review. Just follow the following principles:
 
 - Keep it simple.
 - Keep it consistent with the design.
-- Use as little dependency as possible.
-- Have patient.
+- Use as few dependencies as possible.
+- Have patience.
 
->I am not a web developer. I just created this theme for my personal needs. So, it is reasonable to have some flaws in the codes. Feel free to open issues and PR acknowledging the problems.
+> I am not a web developer. I have created this theme for my personal needs. So, it is reasonable to have some flaws in the codes. Feel free to open issues and PRs acknowledging the problems.
+
+## Local Development
+
+For local development, you can make changes in the theme submodule and test the changes against your own site or this [example site](https://github.com/hugo-toha/hugo-toha.github.io) locally.
+
+### Fork
+
+At first, fork [this repo](https://github.com/hugo-toha/toha). Then, follow the following steps to use the forked theme for local developments,
+
+**Using the forked theme in your own site:**
+
+If you want to run your local development against your own site, follow the following steps:
+
+```bash
+# add the original theme as a submodule of your site if you haven't done already
+$ git submodule add https://github.com/hugo-toha/toha.git themes/toha
+# navigate into the toha theme folder
+$ cd themes/toha
+# add your own fork as a remote
+$ git remote add my-fork https://github.com/<your-github-user>/toha
+# create a new branch for your changes
+$ git checkout -b my-feature-branch
+```
+
+**Using the forked theme in the example site:**
+
+If your want to run your local development against this [example site](https://github.com/hugo-toha/hugo-toha.github.io), follow the following steps:
+
+```bash
+# clone the example site along with the submodules
+$ git clone git@github.com:hugo-toha/hugo-toha.github.io.git --recursive
+# navigate into the toha theme folder
+$ cd themes/toha
+# add your own fork as a remote
+$ git remote add my-fork https://github.com/<your-github-user>/toha
+# create a new branch for your changes
+$ git checkout -b my-feature-branch
+```
+
+From there you can make changes to the source code of the theme while testing with your running Hugo site or the example site.
+
+### Open a PR
+
+When the changes look good, commit and push them to your fork.
+
+```bash
+# stage all the changes
+$ git add .
+# commit the changes with a meaning full commit message
+$ git commit -m "A meaningful commit message"
+# push the commit to your fork
+$ git push my-fork my-feature-branch
+```
+
+Then, open a PR against `main` branch of [hugo-toha/toha](https://github.com/hugo-toha/toha) from the `my-feature-branch` branch of your own fork.
 
 ## Attribution
 

archetypes/default.md

@@ -1,6 +1,6 @@
 ---
-hero: /assets/images/background/sunrise.jpg
+hero: /images/background/sunrise.jpg
 author:
     name: Md. Emruz Hossain
-    image: /assets/images/profile-image.jpg
+    image: /images/profile-image.jpg
 ---

assets/images/hugo-logo.svg

@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" fill-rule="evenodd" stroke-width="27" aria-label="Logo" viewBox="0 0 1493 391"><path fill="#ebb951" stroke="#fcd804" d="M1345.211 24.704l112.262 64.305a43 43 0 0 1 21.627 37.312v142.237a40 40 0 0 1-20.702 35.037l-120.886 66.584a42 42 0 0 1-41.216-.389l-106.242-61.155a57 57 0 0 1-28.564-49.4V138.71a64 64 0 0 1 31.172-54.939l98.01-58.564a54 54 0 0 1 54.54-.503z"/><path fill="#33ba91" stroke="#00a88a" d="M958.07 22.82l117.31 66.78a41 41 0 0 1 20.72 35.64v139.5a45 45 0 0 1-23.1 39.32L955.68 369.4a44 44 0 0 1-43.54-.41l-105.82-61.6a56 56 0 0 1-27.83-48.4V140.07a68 68 0 0 1 33.23-58.44l98.06-58.35a48 48 0 0 1 48.3-.46z"/><path fill="#0594cb" stroke="#0083c0" d="M575.26 20.97l117.23 68.9a40 40 0 0 1 19.73 34.27l.73 138.67a48 48 0 0 1-24.64 42.2l-115.13 64.11a45 45 0 0 1-44.53-.42l-105.83-61.6a55 55 0 0 1-27.33-47.53V136.52a63 63 0 0 1 29.87-53.59l99.3-61.4a49 49 0 0 1 50.6-.56z"/><path fill="#ff4088" stroke="#c9177e" d="M195.81 24.13l114.41 66.54a44 44 0 0 1 21.88 38.04v136.43a48 48 0 0 1-24.45 41.82L194.1 370.9a49 49 0 0 1-48.48-.23L41.05 310.48a53 53 0 0 1-26.56-45.93V135.08a55 55 0 0 1 26.1-46.8l102.8-63.46a51 51 0 0 1 52.42-.69z"/><path fill="#fff" d="M1320.72 89.15c58.79 0 106.52 47.73 106.52 106.51 0 58.8-47.73 106.52-106.52 106.52-58.78 0-106.52-47.73-106.52-106.52 0-58.78 47.74-106.51 106.52-106.51zm0 39.57c36.95 0 66.94 30 66.94 66.94a66.97 66.97 0 0 1-66.94 66.94c-36.95 0-66.94-29.99-66.94-66.94a66.97 66.97 0 0 1 66.93-66.94h.01zm-283.8 65.31c0 47.18-8.94 60.93-26.81 80.58-17.87 19.65-41.57 27.57-71.1 27.57-27 0-48.75-9.58-67.61-26.23-20.88-18.45-36.08-47.04-36.08-78.95 0-31.37 11.72-58.48 32.49-78.67 18.22-17.67 45.34-29.18 73.3-29.18 33.77 0 68.83 15.98 90.44 47.53l-31.73 26.82c-13.45-25.03-32.94-33.46-60.82-34.26-30.83-.88-64.77 28.53-62.25 67.75 1.4 21.94 11.65 59.65 60.96 66.57 25.9 3.63 55.36-24.02 55.36-39.04H944.4v-37.5h92.5V194l.02.03zm-562.6-94.65h42.29v112.17c0 17.8.49 29.33 1.47 34.61 1.69 8.48 4.81 14.37 11.17 19.5 6.37 5.13 13.8 6.59 24.84 6.59 11.2 0 14.96-1.74 20.66-6.6 5.69-4.85 9.12-9.46 10.28-16.53 1.15-7.07 3.07-18.8 3.07-35.18V99.38h42.28v108.78c0 24.86-1.07 42.43-3.21 52.69-2.14 10.27-6.08 18.93-11.82 26-5.74 7.06-13.42 12.69-23.03 16.88-9.62 4.19-22.16 6.28-37.65 6.28-18.7 0-32.87-2.28-42.52-6.85-9.66-4.57-17.3-10.5-22.9-17.8-5.61-7.3-9.3-14.95-11.08-22.96-2.58-11.86-3.88-29.38-3.88-52.55V99.38h.03zM93.91 299.92V92.7h43.35v75.48h71.92V92.7h43.48v207.22h-43.48v-90.61h-71.92v90.61z"/></svg>

content/notes/search.bn.md

@@ -0,0 +1,54 @@
+---
+title: "অনুসন্ধানের ফলাফল"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.cn.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.de.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.es.md

@@ -0,0 +1,54 @@
+---
+title: "Resultados de Búsqueda"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+Este archivo existe únicamente para responder a la URL /search con la plantilla de diseño `search` relacionada.
+
+No se muestra ningún contenido aquí, todo el contenido se basa en la plantilla layouts/page/search.html
+
+Establecer una prioridad muy baja en el mapa del sitio le dirá a los motores de búsqueda que éste no es un contenido importante.
+
+Esta implementación utiliza Fusejs, jquery y mark.js
+
+
+## Configuración inicial
+
+La búsqueda depende del tipo de contenido de salida adicional de JSON en config.toml
+
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Búsqueda de archivos adicionales
+
+Para buscar campos adicionales definidos en el front matter, debes añadirlo en 2 lugares.
+
+### Editar layouts/_default/index.JSON
+Esto expone los valores en /index.json: por ejemplo, para agregar `categories`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Editar las opciones de fuse.js para buscar
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.fr.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.hi.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.id.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.it.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.jp.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.ko.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.md

@@ -0,0 +1,52 @@
+---
+title: "Search Results"
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.ru.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/notes/search.vn.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.bn.md

@@ -0,0 +1,54 @@
+---
+title: "অনুসন্ধানের ফলাফল"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.cn.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.de.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.es.md

@@ -0,0 +1,54 @@
+---
+title: "Resultados de Búsqueda"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+Este archivo existe únicamente para responder a la URL /search con la plantilla de diseño `search` relacionada.
+
+No se muestra ningún contenido aquí, todo el contenido se basa en la plantilla layouts/page/search.html
+
+Establecer una prioridad muy baja en el mapa del sitio le dirá a los motores de búsqueda que éste no es un contenido importante.
+
+Esta implementación utiliza Fusejs, jquery y mark.js
+
+
+## Configuración inicial
+
+La búsqueda depende del tipo de contenido de salida adicional de JSON en config.toml
+
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Búsqueda de archivos adicionales
+
+Para buscar campos adicionales definidos en el front matter, debes añadirlo en 2 lugares.
+
+### Editar layouts/_default/index.JSON
+Esto expone los valores en /index.json: por ejemplo, para agregar `categories`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Editar las opciones de fuse.js para buscar
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.fr.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.hi.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.id.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.it.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.jp.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.ko.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.ru.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

content/posts/search.vn.md

@@ -0,0 +1,54 @@
+---
+title: "Search Results"
+date: 2010-06-08T08:06:25+06:00
+weight: 999999
+sitemap:
+  priority : 0.1
+layout: "search"
+url: search
+---
+
+
+This file exists solely to respond to /search URL with the related `search` layout template.
+
+No content shown here is rendered, all content is based in the template layouts/page/search.html
+
+Setting a very low sitemap priority will tell search engines this is not important content.
+
+This implementation uses Fusejs, jquery and mark.js
+
+
+## Initial setup
+
+Search  depends on additional output content type of JSON in config.toml
+\```
+[outputs]
+  home = ["HTML", "JSON"]
+\```
+
+## Searching additional fileds
+
+To search additional fields defined in front matter, you must add it in 2 places.
+
+### Edit layouts/_default/index.JSON
+This exposes the values in /index.json
+i.e. add `category`
+\```
+...
+  "contents":{{ .Content | plainify | jsonify }}
+  {{ if .Params.tags }},
+  "tags":{{ .Params.tags | jsonify }}{{end}},
+  "categories" : {{ .Params.categories | jsonify }},
+...
+\```
+
+### Edit fuse.js options to Search
+`static/js/search.js`
+\```
+keys: [
+  "title",
+  "contents",
+  "tags",
+  "categories"
+]
+\```

exampleSite/config.yaml

@@ -1,66 +0,0 @@
-baseURL: http://example.org/
-languageCode: en-us
-title: "Toha"
-theme: "toha"
-
-# Manage languages
-# For any more details, you can check the official documentation: https://gohugo.io/content-management/multilingual/
-languages:
-  en:
-    languageName: English
-    weight: 1
-  fr:
-    languageName: Français
-    weight: 2
-  bn:
-    languageName: বাংলা
-    weight: 3
-
-# Force a locale to be use, really useful to develop the application ! Should be commented in production, the "weight" should rocks.
-# DefaultContentLanguage: fr
-
-# Allow raw html in markdown file
-markup:
-  goldmark:
-    renderer:
-      unsafe: true
-  tableOfContents:
-    startLevel: 2
-    endLevel: 6
-    ordered: false
-
-# Enable Google Analytics
-googleAnalytics: UA-XXXXXXXXX-X
-
-# Enable Disqus forum
-disqusShortname: does-not-exist
-
-# Enable global emoji support
-enableEmoji: true
-
-# Custom parameters
-params:
-  # background image of the landing page
-  background: "images/background.jpg"
-
-  # Provide logos for your site. The inverted logo will be used in the initial
-  # transparent navbar and the main logo will be used in the non-transparent navbar.
-  # It will be default to the theme logos if not provided.
-  logo:
-    main: assets/images/main-logo.png
-    inverted: assets/images/inverted-logo.png
-    favicon: assets/images/favicon.png
-
-  # GitHub repo URL of your site
-  gitRepo: https://github.com/hossainemruz/toha-example-site
-
-  # specify whether you want to write blog post or not
-  enableBlogPost: true
-
-  # specify whether you want to show Table of Contents in reading page
-  enableTOC: true
-
-  # Provide newsletter configuration. This feature hasn't been implemented yet.
-  # Currently, you can just hide it from the footer.
-  newsletter:
-    enable: true

exampleSite/data/bn/author.yaml

@@ -1,16 +0,0 @@
-# some information about you
-name: "জেইন ডো"
-nickname: "জেইন"
-# greeting message before your name. it will default to "Hi! I am" if not provided
-greeting: "হ্যালো, আমি হলাম"
-image: "images/avatar.png"
-# give your some contact information. they will be used in the footer
-contactInfo:
-  email: "janedoe@example.com"
-  phone: "+0123456789"
-
-# some summary about what you do
-summary:
-  - আমি একজন ডেভেলপার
-  - আমি ওপেন সোর্স প্রোজেক্ট এ কাজ করতে পছন্দ করি
-  - আমি মজার কিছু প্রোজেক্ট এ কাজ করতে ভালবাসি

exampleSite/data/bn/sections/about.yaml

@@ -1,78 +0,0 @@
-# section information
-section:
-  name: আমার-সম্পর্কে
-  id: about
-  enable: true
-  weight: 1
-  showOnNavbar: true
-  template: sections/about.html
-
-# your designation
-designation: Software Engineer
-# your company information
-company:
-  name: Example Co.
-  url: "https://www.example.com"
-
-# your resume. this file path should be relative to you "static" directory
-resume: "files/resume.pdf"
-
-# a summary about you
-summary: 'I am a passionate software engineer with x years of working experience. I built OSS tools for [Kubernetes](https://kubernetes.io/) using GO. My tools help people to deploy their workloads in Kubernetes. Sometimes, I work on some fun projects such as writing a theme, etc.'
-
-# your social links
-# give as many as you want. use font-awesome for the icons.
-socialLinks:
-- name: Email
-  icon: "fas fa-envelope"
-  url: "example@gmail.com"
-
-- name: Github
-  icon: "fab fa-github"
-  url: "https://www.github.com/example"
-
-- name: Stackoverflow
-  icon: "fab fa-stack-overflow"
-  url: "#"
-
-- name: LinkedIn
-  icon: "fab fa-linkedin"
-  url: "#"
-
-- name: Twitter
-  icon: "fab fa-twitter"
-  url: "#"
-
-- name: Facebook
-  icon: "fab fa-facebook"
-  url: "#"
-
-# your soft skills
-# give the percentage between 50 to 100 with 5 intervals.
-# currently supported colors: blue, yellow, pink, green, sky, orange
-softSkills:
-- name: Leadership
-  percentage: 85
-  color: blue
-- name: Team Work
-  percentage: 90
-  color: yellow
-- name: Communication
-  percentage: 85
-  color: pink
-- name: Hard Working
-  percentage: 85
-  color: green
-- name: Fast Learner
-  percentage: 85
-  color: sky
-- name: Problem Solving
-  percentage: 85
-  color: orange
-# you can also provide color code instead of pre-defined color name
-# - name: Example 1
-#   percentage: 75
-#   color: "#00adb5"
-# - name: Example 2
-#   percentage: 65
-#   color: "#8b8383"

exampleSite/data/bn/sections/achievements.yaml

@@ -1,25 +0,0 @@
-# section information
-section:
-  name: সাফল্য
-  id: achievements
-  enable: true
-  weight: 6
-  showOnNavbar: true
-  template: sections/achievements.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your achievements achievements
-achievements:
-- title: Best Presenter
-  image: images/achievements/presenter.jpg
-  summary: Best presenter in the 2020 XYZ conference.
-- title: Champion
-  image: images/achievements/sport.jpg
-  summary: Champion in cycling inter-city cycling championship 2020.
-- title: Graduation
-  image: images/achievements/graduation-cap.jpg
-  summary: Received Bachelor of Science (B.Sc.) in Computer Science and Engineer from XYZ University.
-- title: Award Winner
-  image: images/achievements/woman-winner.jpg
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Possimus architecto minus facere vero?

exampleSite/data/bn/sections/experiences.yaml

@@ -1,65 +0,0 @@
-# section information
-section:
-  name: অভিজ্ঞতা
-  id: experiences
-  enable: true
-  weight: 3
-  showOnNavbar: true
-  template: sections/experiences.html
-  # Can optionally hide the title in sections
-  # hideTitle: true 
-
-# Your experiences
-experiences:
-- company:
-    name: Example Co.
-    url: "https://www.example.com"
-    location: Dhaka Branch
-    # company overview
-    overview: Example Co. is a widely recognized company for cloud-native development. It builds tools for Kubernetes.
-  positions:
-  - designation: Senior Software Engineer
-    start: Nov 2019
-    # don't provide end date if you are currently working there. It will be replaced by "Present"
-    # end: Dec 2020
-    # give some points about what was your responsibilities at the company.
-    responsibilities:
-    - Design and develop XYZ tool for ABC task
-    - Design, develop and manage disaster recovery tool [Xtool](https://www.example.com) that backup Kubernetes volumes, databases, and cluster's resource definition.
-    - Lead backend team.
-
-  - designation: Junior Software Engineer
-    start: Nov 2017
-    end: Oct 2019
-    responsibilities:
-    - Implement and test xyz feature for abc tool.
-    - Support client for abc tool.
-    - Learn k,d,w technology for xyz.
-
-- company:
-    name: PreExample Co.
-    url: "https://www.preexample.com"
-    location: Nowhere
-    overview: PreExample Co. is a gateway company to enter into Example co. So, nothing special here.
-  positions:
-  - designation: Software Engineer
-    start: March 2016
-    end: May 2017
-    responsibilities:
-    - Write lots of example codes.
-    - Read lots of examples.
-    - See lots of example videos.
-
-- company:
-    name: Intern Counting Company (ICC).
-    url: "https://www.intern.com"
-    location: Intern Land
-    overview: Intern counting Company (ICC) is responsible for counting worldwide intern Engineers.
-  positions:
-  - designation: Intern
-    start: Jun 2015
-    end: Jan 2016
-    responsibilities:
-    - Count lost of interns.
-    - Count more interns.
-    - Count me as an intern.

exampleSite/data/bn/sections/projects.yaml

@@ -1,65 +0,0 @@
-# section information
-section:
-  name: প্রোজেক্ট
-  id: projects
-  enable: true
-  weight: 4
-  showOnNavbar: true
-  template: sections/projects.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# filter buttons
-buttons:
-- name: All
-  filter: "all"
-- name: Professional
-  filter: "professional"
-- name: Academic
-  filter: "academic"
-- name: Hobby
-  filter: "hobby"
-
-# your projects
-projects:
-- name: Kubernetes
-  logo: images/projects/kubernetes.png
-  role: Contributor
-  timeline: "March 2018 - Present"
-  repo: https://github.com/kubernetes/kubernetes # If your project is a public repo on GitHub, then provide this link. it will show star count.
-  #url: ""  # If your project is not a public repo but it has a website or any external details url then provide it here. don't provide "repo" and "url" simultaneously.
-  summary: Production-Grade Container Scheduling and Management.
-  tags: ["professional", "kubernetes", "cloud"]
-
-- name: Tensorflow
-  logo: images/projects/tensorflow.png
-  role: Developer
-  timeline: "Jun 2018 - Present"
-  repo: https://github.com/tensorflow/tensorflow
-  #url: ""
-  summary: An Open Source Machine Learning Framework for Everyone.
-  tags: ["professional", "machine-learning","academic"]
-
-- name: A sample academic paper
-  role: Team Lead
-  timeline: "Jan 2017 - Nov 2017"
-  url: "https://www.example.com"
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Sapiente eius reprehenderit animi suscipit autem eligendi esse amet aliquid error eum. Accusantium distinctio soluta aliquid quas placeat modi suscipit eligendi nisi.
-  tags: ["academic","iot"]
-
-- name: Nocode
-  logo: images/projects/no-code.png
-  role: Nothing
-  timeline: "Oct 2019 - Dec 2019"
-  repo: https://github.com/kelseyhightower/nocode
-  #url: ""
-  summary: The best way to write secure and reliable applications. Write nothing; deploy nowhere.
-  tags: ["hobby", "fun"]
-
-- name: Toha
-  logo: images/projects/toha.png
-  role: Owner
-  timeline: "Jun 2019 - Present"
-  repo: https://github.com/hossainemruz/toha
-  summary: A Hugo theme for personal portfolio.
-  tags: ["hobby","hugo","theme","professional"]

exampleSite/data/bn/sections/recent-posts.yaml

@@ -1,12 +0,0 @@
-# section information
-section:
-  name: সাম্প্রতিক-পোস্ট
-  id: recent-posts
-  enable: true
-  weight: 5
-  showOnNavbar: true
-  template: sections/recent-posts.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# no additional configuration is required

exampleSite/data/bn/sections/skills.yaml

@@ -1,50 +0,0 @@
-# section information
-section:
-  name: দক্ষতা
-  id: skills
-  enable: true
-  weight: 2
-  showOnNavbar: true
-  template: sections/skills.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your Skills.
-# Give a summary of you each skill in the summary section.
-skills:
-- name: Kubernetes
-  icon: "images/skills/kubernetes.png"
-  summary: "Capable of deploying, managing application on Kubernetes. Experienced in writing Kubernetes controllers for CRDs."
-  url: "https://kubernetes.io/"
-
-- name: Go Development
-  icon: "images/skills/go.png"
-  summary: "Using as the main language for professional development. Capable of writing scalable, testable, and maintainable program."
-  url: "https://golang.org/"
-
-- name: Cloud Computing
-  icon: "images/skills/cloud.png"
-  summary: "Worked with most of the major clouds such as GCP, AWS, Azure etc."
-
-- name: Docker
-  icon: "images/skills/docker.svg"
-  summary: "Write most of the programs as dockerized container. Experienced with multi-stage, multi-arch build process."
-  url: "https://www.docker.com/"
-
-- name: Prometheus
-  icon: "images/skills/prometheus.png"
-  summary: "Capable of setup, configure Prometheus metrics. Experienced with PromQL, AlertManager. Also, experienced with writing metric exporters."
-  url: "https://prometheus.io/"
-
-- name: Linux
-  icon: "images/skills/linux.png"
-  summary: "Using as the main operating system. Capable of writing bash/shell scripts."
-
-- name: Git
-  icon: "images/skills/git.png"
-  summary: "Experienced with git-based development. Mostly, use Github. Also, have experience in working with GitLab."
-  url: "https://git-scm.com/"
-
-- name: C++
-  icon: "images/skills/c++.png"
-  summary: "Know basic C/C++ programming. Used for contest programming and problem solving."

exampleSite/data/bn/site.yaml

@@ -1,11 +0,0 @@
-# Copyright Notice
-copyright: © 2020 Copyright.
-
-# Meta description for your site.  This will help the search engines to find your site.
-description: Portfolio and personal blog of Jane Doe.
-
-# specify the list of custom menus that you want to show in the top navbar.
-# they will be separated by a divider from the main menus.
-customMenus:
-- name: নোটসমুহ
-  url: https://hossainemruz.gitbook.io/

exampleSite/data/en/author.yaml

@@ -1,18 +0,0 @@
-# some information about you
-name: "Jane Doe"
-nickname: "Jane"
-# greeting message before your name. it will default to "Hi! I am" if not provided
-greeting: "Hi, I am"
-image: "images/avatar.png"
-# give your some contact information. they will be used in the footer
-contactInfo:
-  email: "janedoe@example.com"
-  phone: "+0123456789"
-
-# some summary about what you do
-summary:
-  - I am a Developer
-  - I am a Devops
-  - I love servers
-  - I work on open-source projects
-  - I love to work with some fun projects

exampleSite/data/en/sections/about.yaml

@@ -1,78 +0,0 @@
-# section information
-section:
-  name: About
-  id: about
-  enable: true
-  weight: 1
-  showOnNavbar: true
-  template: sections/about.html
-
-# your designation
-designation: Software Engineer
-# your company information
-company:
-  name: Example Co.
-  url: "https://www.example.com"
-
-# your resume. this file path should be relative to you "static" directory
-resume: "files/resume.pdf"
-
-# a summary about you
-summary: 'I am a passionate software engineer with x years of working experience. I built OSS tools for [Kubernetes](https://kubernetes.io/) using GO. My tools help people to deploy their workloads in Kubernetes. Sometimes, I work on some fun projects such as writing a theme, etc.'
-
-# your social links
-# give as many as you want. use font-awesome for the icons.
-socialLinks:
-- name: Email
-  icon: "fas fa-envelope"
-  url: "example@gmail.com"
-
-- name: Github
-  icon: "fab fa-github"
-  url: "https://www.github.com/example"
-
-- name: Stackoverflow
-  icon: "fab fa-stack-overflow"
-  url: "#"
-
-- name: LinkedIn
-  icon: "fab fa-linkedin"
-  url: "#"
-
-- name: Twitter
-  icon: "fab fa-twitter"
-  url: "#"
-
-- name: Facebook
-  icon: "fab fa-facebook"
-  url: "#"
-
-# your soft skills
-# give the percentage between 50 to 100 with 5 intervals.
-# currently supported colors: blue, yellow, pink, green, sky, orange
-softSkills:
-- name: Leadership
-  percentage: 85
-  color: blue
-- name: Team Work
-  percentage: 90
-  color: yellow
-- name: Communication
-  percentage: 85
-  color: pink
-- name: Hard Working
-  percentage: 85
-  color: green
-- name: Fast Learner
-  percentage: 85
-  color: sky
-- name: Problem Solving
-  percentage: 85
-  color: orange
-# you can also provide color code instead of pre-defined color name
-# - name: Example 1
-#   percentage: 75
-#   color: "#00adb5"
-# - name: Example 2
-#   percentage: 65
-#   color: "#8b8383"

exampleSite/data/en/sections/achievements.yaml

@@ -1,24 +0,0 @@
-# section information
-section:
-  name: Achievements
-  id: achievements
-  enable: true
-  weight: 6
-  showOnNavbar: true
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your achievements achievements
-achievements:
-- title: Best Presenter
-  image: images/achievements/presenter.jpg
-  summary: Best presenter in the 2020 XYZ conference.
-- title: Champion
-  image: images/achievements/sport.jpg
-  summary: Champion in cycling inter-city cycling championship 2020.
-- title: Graduation
-  image: images/achievements/graduation-cap.jpg
-  summary: Received Bachelor of Science (B.Sc.) in Computer Science and Engineer from XYZ University.
-- title: Award Winner
-  image: images/achievements/woman-winner.jpg
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Possimus architecto minus facere vero?

exampleSite/data/en/sections/experiences.yaml

@@ -1,64 +0,0 @@
-# section information
-section:
-  name: Experiences
-  id: experiences
-  enable: true
-  weight: 3
-  showOnNavbar: true
-  # Can optionally hide the title in sections
-  # hideTitle: true 
-
-# Your experiences
-experiences:
-- company:
-    name: Example Co.
-    url: "https://www.example.com"
-    location: Dhaka Branch
-    # company overview
-    overview: Example Co. is a widely recognized company for cloud-native development. It builds tools for Kubernetes.
-  positions:
-  - designation: Senior Software Engineer
-    start: Nov 2019
-    # don't provide end date if you are currently working there. It will be replaced by "Present"
-    # end: Dec 2020
-    # give some points about what was your responsibilities at the company.
-    responsibilities:
-    - Design and develop XYZ tool for ABC task
-    - Design, develop and manage disaster recovery tool [Xtool](https://www.example.com) that backup Kubernetes volumes, databases, and cluster's resource definition.
-    - Lead backend team.
-
-  - designation: Junior Software Engineer
-    start: Nov 2017
-    end: Oct 2019
-    responsibilities:
-    - Implement and test xyz feature for abc tool.
-    - Support client for abc tool.
-    - Learn k,d,w technology for xyz.
-
-- company:
-    name: PreExample Co.
-    url: "https://www.preexample.com"
-    location: Nowhere
-    overview: PreExample Co. is a gateway company to enter into Example co. So, nothing special here.
-  positions:
-  - designation: Software Engineer
-    start: March 2016
-    end: May 2017
-    responsibilities:
-    - Write lots of example codes.
-    - Read lots of examples.
-    - See lots of example videos.
-
-- company:
-    name: Intern Counting Company (ICC).
-    url: "https://www.intern.com"
-    location: Intern Land
-    overview: Intern counting Company (ICC) is responsible for counting worldwide intern Engineers.
-  positions:
-  - designation: Intern
-    start: Jun 2015
-    end: Jan 2016
-    responsibilities:
-    - Count lost of interns.
-    - Count more interns.
-    - Count me as an intern.

exampleSite/data/en/sections/projects.yaml

@@ -1,64 +0,0 @@
-# section information
-section:
-  name: Projects
-  id: projects
-  enable: true
-  weight: 4
-  showOnNavbar: true
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# filter buttons
-buttons:
-- name: All
-  filter: "all"
-- name: Professional
-  filter: "professional"
-- name: Academic
-  filter: "academic"
-- name: Hobby
-  filter: "hobby"
-
-# your projects
-projects:
-- name: Kubernetes
-  logo: images/projects/kubernetes.png
-  role: Contributor
-  timeline: "March 2018 - Present"
-  repo: https://github.com/kubernetes/kubernetes # If your project is a public repo on GitHub, then provide this link. it will show star count.
-  #url: ""  # If your project is not a public repo but it has a website or any external details url then provide it here. don't provide "repo" and "url" simultaneously.
-  summary: Production-Grade Container Scheduling and Management.
-  tags: ["professional", "kubernetes", "cloud"]
-
-- name: Tensorflow
-  logo: images/projects/tensorflow.png
-  role: Developer
-  timeline: "Jun 2018 - Present"
-  repo: https://github.com/tensorflow/tensorflow
-  #url: ""
-  summary: An Open Source Machine Learning Framework for Everyone.
-  tags: ["professional", "machine-learning","academic"]
-
-- name: A sample academic paper
-  role: Team Lead
-  timeline: "Jan 2017 - Nov 2017"
-  url: "https://www.example.com"
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Sapiente eius reprehenderit animi suscipit autem eligendi esse amet aliquid error eum. Accusantium distinctio soluta aliquid quas placeat modi suscipit eligendi nisi.
-  tags: ["academic","iot"]
-
-- name: Nocode
-  logo: images/projects/no-code.png
-  role: Nothing
-  timeline: "Oct 2019 - Dec 2019"
-  repo: https://github.com/kelseyhightower/nocode
-  #url: ""
-  summary: The best way to write secure and reliable applications. Write nothing; deploy nowhere.
-  tags: ["hobby", "fun"]
-
-- name: Toha
-  logo: images/projects/toha.png
-  role: Owner
-  timeline: "Jun 2019 - Present"
-  repo: https://github.com/hossainemruz/toha
-  summary: A Hugo theme for personal portfolio.
-  tags: ["hobby","hugo","theme","professional"]

exampleSite/data/en/sections/recent-posts.yaml

@@ -1,11 +0,0 @@
-# section information
-section:
-  name: Recent Posts
-  id: recent-posts
-  enable: true
-  weight: 5
-  showOnNavbar: true
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# no additional configuration is required

exampleSite/data/en/sections/skills.yaml

@@ -1,49 +0,0 @@
-# section information
-section:
-  name: Skills
-  id: skills
-  enable: true
-  weight: 2
-  showOnNavbar: true
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your Skills.
-# Give a summary of you each skill in the summary section.
-skills:
-- name: Kubernetes
-  icon: "images/skills/kubernetes.png"
-  summary: "Capable of deploying, managing application on Kubernetes. Experienced in writing Kubernetes controllers for CRDs."
-  url: "https://kubernetes.io/"
-
-- name: Go Development
-  icon: "images/skills/go.png"
-  summary: "Using as the main language for professional development. Capable of writing scalable, testable, and maintainable program."
-  url: "https://golang.org/"
-
-- name: Cloud Computing
-  icon: "images/skills/cloud.png"
-  summary: "Worked with most of the major clouds such as GCP, AWS, Azure etc."
-
-- name: Docker
-  icon: "images/skills/docker.svg"
-  summary: "Write most of the programs as dockerized container. Experienced with multi-stage, multi-arch build process."
-  url: "https://www.docker.com/"
-
-- name: Prometheus
-  icon: "images/skills/prometheus.png"
-  summary: "Capable of setup, configure Prometheus metrics. Experienced with PromQL, AlertManager. Also, experienced with writing metric exporters."
-  url: "https://prometheus.io/"
-
-- name: Linux
-  icon: "images/skills/linux.png"
-  summary: "Using as the main operating system. Capable of writing bash/shell scripts."
-
-- name: Git
-  icon: "images/skills/git.png"
-  summary: "Experienced with git-based development. Mostly, use Github. Also, have experience in working with GitLab."
-  url: "https://git-scm.com/"
-
-- name: C++
-  icon: "images/skills/c++.png"
-  summary: "Know basic C/C++ programming. Used for contest programming and problem solving."

exampleSite/data/en/site.yaml

@@ -1,11 +0,0 @@
-# Copyright Notice
-copyright: © 2020 Copyright.
-
-# Meta description for your site.  This will help the search engines to find your site.
-description: Portfolio and personal blog of Jane Doe.
-
-# specify the list of custom menus that you want to show in the top navbar.
-# they will be separated by a divider from the main menus.
-customMenus:
-- name: Notes
-  url: https://hossainemruz.gitbook.io/

exampleSite/data/fr/author.yaml

@@ -1,19 +0,0 @@
-name: "Jane Doe"
-nickname: "Jane"
-image: "images/avatar.png"
-
-# greeting message before your name. it will default to "Hi! I am" if not provided
-greeting: "Bonjour, je suis"
-
-# give your some contact information. they will be used in the footer
-contactInfo:
-  email: "janedoe@example.com"
-  phone: "+0123456789"
-
-# some summary about what you do
-summary:
-  - Je suis un développeur
-  - Je suis un Devops
-  - J'aime les serveurs
-  - Je travaille sur des projets open-source
-  - J'aime travailler avec des projets amusants

exampleSite/data/fr/sections/about.yaml

@@ -1,78 +0,0 @@
-# section information
-section:
-  name: "A propos"
-  id: about
-  enable: true
-  weight: 1
-  showOnNavbar: true
-  template: sections/about.html
-
-# your designation
-designation: "Développeur logiciel"
-# your company information
-company:
-  name: Example Co.
-  url: "https://www.example.com"
-
-# your resume. this file path should be relative to you "static" directory
-resume: "files/resume.pdf"
-
-# a summary about you
-summary: "Je suis un ingénieur en logiciel passionné, avec x années d'expérience professionnelle. J'ai construit des outils OSS pour [Kubernetes](https://kubernetes.io/) en utilisant GO. Mes outils aident les gens à déployer leurs charges de travail dans Kubernetes. Parfois, je travaille sur des projets amusants comme l'écriture d'un thème, etc."
-
-# your social links
-# give as many as you want. use font-awesome for the icons.
-socialLinks:
-- name: Email
-  icon: "fas fa-envelope"
-  url: "example@gmail.com"
-
-- name: Github
-  icon: "fab fa-github"
-  url: "https://www.github.com/example"
-
-- name: Stackoverflow
-  icon: "fab fa-stack-overflow"
-  url: "#"
-
-- name: LinkedIn
-  icon: "fab fa-linkedin"
-  url: "#"
-
-- name: Twitter
-  icon: "fab fa-twitter"
-  url: "#"
-
-- name: Facebook
-  icon: "fab fa-facebook"
-  url: "#"
-
-# your soft skills
-# give the percentage between 50 to 100 with 5 intervals.
-# currently supported colors: blue, yellow, pink, green, sky, orange
-softSkills:
-- name: Chef de projet
-  percentage: 85
-  color: blue
-- name: Travail d'équipe
-  percentage: 90
-  color: yellow
-- name: Communication
-  percentage: 85
-  color: pink
-- name: Persévérant
-  percentage: 85
-  color: green
-- name: Autonome
-  percentage: 85
-  color: sky
-- name: Logique
-  percentage: 85
-  color: orange
-# you can also provide color code instead of pre-defined color name
-# - name: Example 1
-#   percentage: 75
-#   color: "#00adb5"
-# - name: Example 2
-#   percentage: 65
-#   color: "#8b8383"

exampleSite/data/fr/sections/achievements.yaml

@@ -1,25 +0,0 @@
-# section information
-section:
-  name: Realisations
-  id: achievements
-  enable: true
-  weight: 6
-  showOnNavbar: true
-  template: sections/achievements.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your achievements achievements
-achievements:
-- title: Meilleur présentateur
-  image: images/achievements/presenter.jpg
-  summary: Meilleur présentateur de la conférence XYZ 2020.
-- title: Champion
-  image: images/achievements/sport.jpg
-  summary: Champion du championnat cycliste interurbain 2020.
-- title: Remise des diplômes
-  image: images/achievements/graduation-cap.jpg
-  summary: J'ai obtenu une licence en sciences (B.Sc.) en informatique et en ingénierie à l'université XYZ.
-- title: Lauréat du prix
-  image: images/achievements/woman-winner.jpg
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Possimus architecto minus facere vero?

exampleSite/data/fr/sections/experiences.yaml

@@ -1,65 +0,0 @@
-# section information
-section:
-  name: Experiences
-  id: experiences
-  enable: true
-  weight: 3
-  showOnNavbar: true
-  template: sections/experiences.html
-  # Can optionally hide the title in sections
-  # hideTitle: true 
-
-# Your experiences
-experiences:
-- company:
-    name: Example Co.
-    url: "https://www.example.com"
-    location: Dhaka Branch
-    # company overview
-    overview: Example Co. est une entreprise largement reconnue pour le développement de l'utilisation des nuages. Elle construit des outils pour Kubernetes.
-  positions:
-  - designation: Ingénieur logiciel senior
-    start: Nov 2019
-    # don't provide end date if you are currently working there. It will be replaced by "Present"
-    # end: Dec 2020
-    # give some points about what was your responsibilities at the company.
-    responsibilities:
-    - Concevoir et développer l'outil XYZ pour la tâche ABC.
-    - Concevoir, développer et gérer l'outil de reprise après sinistre [Xtool](https://www.example.com) qui sauvegarde les volumes, les bases de données et la définition des ressources du cluster de Kubernetes.
-    - Diriger l'équipe de soutien.
-
-  - designation: Ingénieur logiciel junior
-    start: Nov 2017
-    end: Oct 2019
-    responsibilities:
-    - Implémenter et tester la fonction xyz pour l'outil abc.
-    - Support client pour abc tool.
-    - Apprendre la technologie k,d,w pour xyz.
-
-- company:
-    name: PreExample Co.
-    url: "https://www.preexample.com"
-    location: Nowhere
-    overview: PreExample Co. est une société passerelle pour entrer dans Example co. Donc, rien de spécial ici.
-  positions:
-  - designation: Ingénieur logiciel
-    start: Mars 2016
-    end: Mai 2017
-    responsibilities:
-    - Rédigez de nombreux exemples de codes.
-    - Lire de nombreux exemples.
-    - Voir de nombreux exemples de vidéos.
-
-- company:
-    name: Intern Counting Company (ICC).
-    url: "https://www.intern.com"
-    location: Intern Land
-    overview: La Compagnie de comptage des stagiaires (ICC) est responsable du comptage des ingénieurs stagiaires du monde entier.
-  positions:
-  - designation: Stagiaire
-    start: Juin 2015
-    end: Jan 2016
-    responsibilities:
-    - Compte perdu des stagiaires.
-    - Comptez plus de stagiaires.
-    - Comptez-moi comme un stagiaire.

exampleSite/data/fr/sections/projects.yaml

@@ -1,65 +0,0 @@
-# section information
-section:
-  name: Projets
-  id: projects
-  enable: true
-  weight: 4
-  showOnNavbar: true
-  template: sections/projects.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# filter buttons
-buttons:
-- name: All
-  filter: "all"
-- name: Professionnel
-  filter: "professionnel"
-- name: Ecole
-  filter: "ecole"
-- name: Hobby
-  filter: "hobby"
-
-# your projects
-projects:
-- name: Kubernetes
-  logo: images/projects/kubernetes.png
-  role: Contributeur
-  timeline: "Mars 2018 - Présent"
-  repo: https://github.com/kubernetes/kubernetes # If your project is a public repo on GitHub, then provide this link. it will show star count.
-  #url: ""  # If your project is not a public repo but it has a website or any external details url then provide it here. don't provide "repo" and "url" simultaneously.
-  summary: Planification et gestion des conteneurs de qualité production.
-  tags: ["professionnel", "kubernetes", "cloud"]
-
-- name: Tensorflow
-  logo: images/projects/tensorflow.png
-  role: Développeur
-  timeline: "Juin 2018 - Présent"
-  repo: https://github.com/tensorflow/tensorflow
-  #url: ""
-  summary: Un cadre d'apprentissage machine à source ouverte pour tous.
-  tags: ["professionnel", "machine-learning","ecole"]
-
-- name: Un exemple d'article académique
-  role: Chef d'équipe
-  timeline: "Janvier 2017 - Novembre 2017"
-  url: "https://www.example.com"
-  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Sapiente eius reprehenderit animi suscipit autem eligendi esse amet aliquid error eum. Accusantium distinctio soluta aliquid quas placeat modi suscipit eligendi nisi.
-  tags: ["ecole","iot"]
-
-- name: Nocode
-  logo: images/projects/no-code.png
-  role: Rien
-  timeline: "Oct 2019 - Dec 2019"
-  repo: https://github.com/kelseyhightower/nocode
-  #url: ""
-  summary: La meilleure façon de rédiger des demandes sûres et fiables. N'écrivez rien, ne déployez rien.
-  tags: ["hobby", "fun"]
-
-- name: Toha
-  logo: images/projects/toha.png
-  role: Owner
-  timeline: "Juin 2019 - Présent"
-  repo: https://github.com/hossainemruz/toha
-  summary: Un thème Hugo pour le portfolio personnel.
-  tags: ["hobby","hugo","theme","professionnel"]

exampleSite/data/fr/sections/recent-posts.yaml

@@ -1,12 +0,0 @@
-# section information
-section:
-  name: Posts recents
-  id: recent-posts
-  enable: true
-  weight: 5
-  showOnNavbar: true
-  template: sections/recent-posts.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# no additional configuration is required

exampleSite/data/fr/sections/skills.yaml

@@ -1,50 +0,0 @@
-# section information
-section:
-  name: Competences
-  id: skills
-  enable: true
-  weight: 2
-  showOnNavbar: true
-  template: sections/skills.html
-  # Can optionally hide the title in sections
-  # hideTitle: true
-
-# Your Skills.
-# Give a summary of you each skill in the summary section.
-skills:
-- name: Kubernetes
-  icon: "images/skills/kubernetes.png"
-  summary: "Capable de déployer, de gérer l'application sur Kubernetes. Expérimenté dans la rédaction de contrôleurs Kubernetes pour les CRD."
-  url: "https://kubernetes.io/"
-
-- name: Go
-  icon: "images/skills/go.png"
-  summary: "Utiliser comme langue principale pour le développement professionnel. Capable d'écrire des programmes évolutifs, testables et maintenables."
-  url: "https://golang.org/"
-
-- name: Cloud Computing
-  icon: "images/skills/cloud.png"
-  summary: "A travaillé avec la plupart des principaux nuages tels que GCP, AWS, Azure, etc."
-
-- name: Docker
-  icon: "images/skills/docker.svg"
-  summary: "Inscrivez la plupart des programmes en tant que conteneur déchargé. Expérimenté dans le processus de construction en plusieurs étapes et en plusieurs arcs."
-  url: "https://www.docker.com/"
-
-- name: Prometheus
-  icon: "images/skills/prometheus.png"
-  summary: "Capable d'installation, de configurer les métriques de Prometheus. Expérimenté avec PromQL, AlertManager. Expérimenté également dans la rédaction d'exportateurs de métriques."
-  url: "https://prometheus.io/"
-
-- name: Linux
-  icon: "images/skills/linux.png"
-  summary: "Utilisé comme système d'exploitation principal. Capable d'écrire des scripts bash/shell."
-
-- name: Git
-  icon: "images/skills/git.png"
-  summary: "Expérimenté dans le développement basé sur les GIT. Surtout, utilisez Github. Avoir également une expérience de travail avec GitLab."
-  url: "https://git-scm.com/"
-
-- name: C++
-  icon: "images/skills/c++.png"
-  summary: "Connaître les bases de la programmation C/C++. Utilisé pour la programmation de concours et la résolution de problèmes."

exampleSite/data/fr/site.yaml

@@ -1,11 +0,0 @@
-# Copyright Notice
-copyright: © 2020 Droits d'auteur.
-
-# Meta description for your site.  This will help the search engines to find your site.
-description: Portfolio et blog personnel de Jane Doe.
-
-# specify the list of custom menus that you want to show in the top navbar.
-# they will be separated by a divider from the main menus.
-customMenus:
-- name: Remarques
-  url: https://hossainemruz.gitbook.io/

i18n/bn.toml

@@ -5,6 +5,15 @@ other = "হোম"
 [posts]
 other = "পোষ্ট সমূহ"
 
+[toc_heading]
+other = "সুচিপত্র"
+
+[tags]
+other = "ট্যাগ সমুহ"
+
+[categories]
+other = "বিভাগ সমুহ"
+
 [resume]
 other = "আমার জীবনবৃত্তান্ত"
 
@@ -14,6 +23,12 @@ other = "নেভিগেশন"
 [contact_me]
 other = "আমার সাথে যোগাযোগ করুনঃ"
 
+[email]
+other = "ইমেইল"
+
+[phone]
+other = "ফোন"
+
 [newsletter_text]
 other = "ইমেইল নোটিফিকেশান এর মাধ্যমে সর্বশেষ তথ্য জানুন"
 
@@ -21,10 +36,88 @@ other = "ইমেইল নোটিফিকেশান এর মাধ্
 other = "ইমেইল প্রবেশ করান"
 
 [newsletter_warning]
-other = "আমরা আপনার ইমেল অন্য কারও সাথে শেয়ার করব না।"
+other = "আপনার ইমেইল ঠিকানা প্রবেশের মাধমে আপনি এই ওয়েবসাইটের নিউজ লেটার পেতে সম্মত হচ্ছেন।"
 
 [submit]
 other = "জমা দিন"
 
 [hugoAttributionText]
 other = "পাওয়ারড বাই"
+
+[prev]
+other = "পূর্ববর্তী"
+
+[next]
+other = "পরবর্তী"
+
+[share_on]
+other = "শেয়ার করুন"
+
+[improve_this_page]
+other = "এই পৃষ্ঠাটি উন্নত করুন"
+
+[out_of]
+other = "এর মধ্যে"
+
+[publications]
+other = "প্রকাশনা সমূহ"
+
+[taken_courses]
+other = "গৃহীত কোর্সসমূহ"
+
+[course_name]
+other = "কোর্সের নাম"
+
+[total_credit]
+other = "মোট ক্রেডিট"
+
+[obtained_credit]
+other = "অর্জিত ক্রেডিট"
+
+[extracurricular_activities]
+other = "পাঠক্রম বহির্ভূত কার্যক্রম"
+
+[show_more]
+other = "আরো দেখান"
+
+[show_less]
+other = "কম দেখান"
+
+[responsibilities]
+other = "দায়িত্বসমুহ:"
+
+[present]
+other = "বর্তমান"
+
+# [comments_javascript]
+# other = "Please enable JavaScript to view the"
+
+# [comments_by]
+# other = "comments powered by"
+
+# [read]
+# other = "Read"
+
+# [project_star]
+# other = "Star"
+
+# [project_details]
+# other = "Details"
+
+# [err_404]
+# other = "The page you are looking for is not there yet."
+
+[more]
+other = "আরো"
+
+[view_certificate]
+other = "সার্টিফিকেট দেখুন"
+
+[notes]
+other = "নোট সমূহ"
+
+[disclaimer_text]
+other = "দায় বিজ্ঞপ্তি"
+
+[search]
+other = "অনুসন্ধান করুন"

i18n/de.toml

@@ -0,0 +1,126 @@
+# More documentation here: https://github.com/nicksnyder/go-i18n
+[home]
+other = "Home"
+
+[posts]
+other = "Beiträge"
+
+[toc_heading]
+other = "Inhaltsverzeichnis"
+
+[tags]
+other = "Stichworte"
+
+[categories]
+other = "Kategorien"
+
+[at]
+other = "bei"
+
+[resume]
+other = "Mein Lebenslauf"
+
+[navigation]
+other = "Navigation"
+
+[contact_me]
+other = "Kontaktiere mich:"
+
+[email]
+other = "E-Mail"
+
+[phone]
+other = "Telefon"
+
+[newsletter_text]
+other = "Mit dem Newsletter auf dem neuesten Stand bleiben"
+
+[newsletter_input_placeholder]
+other = "E-Mail Adresse eingeben"
+
+[newsletter_warning]
+other = "Mit der Eingabe Ihrer E-Mail-Adresse erklären Sie sich damit einverstanden, den Newsletter dieser Website zu erhalten."
+
+[submit]
+other = "Absenden"
+
+[hugoAttributionText]
+other = "Unterstützt von"
+
+[prev]
+other = "Vorherige"
+
+[next]
+other = "Nächste"
+
+# [share_on]
+# other = "Share on"
+
+[improve_this_page]
+other = "Diese Seite verbessern"
+
+[out_of]
+other = "aus"
+
+[publications]
+other = "Publikationen"
+
+[taken_courses]
+other = "Belegte Kurse"
+
+[course_name]
+other = "Kursname"
+
+[total_credit]
+other = "Gesamtguthaben"
+
+[obtained_credit]
+other = "Erhaltenes Guthaben"
+
+[extracurricular_activities]
+other = "Außerschulische Aktivitäten"
+
+[show_more]
+other = "Mehr anzeigen"
+
+[show_less]
+other = "Weniger anzeigen"
+
+[responsibilities]
+other = "Verantwortlichkeiten:"
+
+[present]
+other = "heute"
+
+[comments_javascript]
+other = "Bitte aktiviere JavaScript um die Kommentare zu sehen"
+
+[comments_by]
+other = "Kommentare Unterstützt von"
+
+[read]
+other = "Lesen"
+
+[project_star]
+other = "Star"
+
+[project_details]
+other = "Details"
+
+[err_404]
+other = "Die Seite nach der Seite ist noch nicht vorhanden."
+
+[more]
+other = "Mehr"
+
+[view_certificate]
+other = "Zertifikat ansehen"
+
+[notes]
+other = "Notizen"
+
+[disclaimer_text]
+other = "Haftungshinweis"
+
+[search]
+other = "Suche"