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>
add vendor specific css prefixes (#600 )
2022-06-10 15:23:40 +00:00 · 2022-06-10 21:22:48 +06:00 · 2022-06-10 15:18:49 +00:00 · 2022-06-09 04:23:08 +00:00 · 2022-05-16 22:26:23 +06:00 · 2022-05-16 05:08:47 +00:00
556 changed files with 11767 additions and 4224 deletions
@@ -17,7 +17,7 @@ categories:
  - 'feature'
  - 'enhancement'
- title: 'New Translations'
+- title: 'Translations'
  label: 'translation'
 - title: 'Bug Fixes'
@@ -2,26 +2,26 @@ name: Autoprefixer
 on:
  push:
    branches:
-      - master
+      - main
 jobs:
  autoprefixer:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout to latest commit
-        uses: actions/checkout@v2.3.4
+        uses: actions/checkout@v3
      - name: Setup Node
-        uses: actions/setup-node@v2.1.5
+        uses: actions/setup-node@v3
        with:
          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.8.2
+        uses: peter-evans/create-pull-request@v4
        with:
          branch: autoprefixer
          branch-suffix: timestamp
@@ -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
@@ -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
@@ -3,13 +3,13 @@ name: Release Drafter
 on:
  push:
    branches:
-    - master
+    - main
 jobs:
  update_release_draft:
    runs-on: ubuntu-latest
    steps:
    # Create/Update release draft
-    - uses: release-drafter/release-drafter@v5.14.0
+    - uses: release-drafter/release-drafter@v5.20.0
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -7,7 +7,7 @@ jobs:
  enforce-label:
    runs-on: ubuntu-latest
    steps:
-    - uses: yogevbd/enforce-label-action@2.2.1
+    - 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']"
@@ -8,6 +8,6 @@ jobs:
    runs-on: ubuntu-latest
    steps:
    # checkout to latest commit
-    - uses: actions/checkout@master
+    - uses: actions/checkout@v3
    # run markdown linter
-    - uses: gaurav-nelson/github-action-markdown-link-check@v1
+    - uses: gaurav-nelson/github-action-markdown-link-check@1.0.14
@@ -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
@@ -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
@@ -1,10 +1,21 @@
 # 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%3Dmaster&style=flat)](https://actions-badge.atrox.dev/hugo-toha/toha/goto?ref=master) ![Repository Size](https://img.shields.io/github/repo-size/hugo-toha/toha) ![Lines of Codes](https://img.shields.io/tokei/lines/github/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)
+[![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://raw.githubusercontent.com/hugo-toha/toha/master/images/screenshot.png)
+![Thumbnail](https://raw.githubusercontent.com/hugo-toha/toha/main/images/screenshot.png)
 - **Example Site:** [hugo-toha.github.io](https://hugo-toha.github.io)
 - **Documentation:** [toha-guides.netlify.app](https://toha-guides.netlify.app/posts)
@@ -19,8 +30,15 @@ A [Hugo](https://gohugo.io/) theme for a personal portfolio with minimalist desi
 - Achievement Gallery
 - Sidebar to Categorize the Posts
 - Short Codes
- Google Analytics Support
+- Analytics Support
- Disqus Comment 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-guides.netlify.app/posts/features/).
@@ -38,29 +56,30 @@ For more details about the features please visit [here](https://toha-guides.netl
 - 日本語
 - 한국어
 - русский
 - 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 screenshot from the [example site](https://hugo-toha.github.io).
+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/master/images/about.png)
+![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/master/images/list.png)
+![List Page](https://raw.githubusercontent.com/hugo-toha/toha/main/images/list.png)
 ##### Reading Page
-![Reading Page](https://raw.githubusercontent.com/hugo-toha/toha/master/images/single.png)
+![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
 ## Usage
@@ -76,7 +95,7 @@ $ git submodule add https://github.com/hugo-toha/toha.git themes/toha
 > 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.
-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/).
+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/).
 #### Configuring Site
@@ -126,10 +145,16 @@ params:
  # specify whether you want to show Table of Contents in reading page
  enableTOC: true
-  # Provide newsletter configuration. This feature hasn't been implemented yet.
+  # Provide newsletter configuration. 
-  # Currently, you can just hide it from the footer.
+  # 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&amp;id=094a24c76e
 ```
 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/).
@@ -139,7 +164,7 @@ Don't forget to update `title`, `baseURL`, and `gitRepo` fields with your own in
 Now, you can run your hugo site with `toha` theme locally with the following command:
 ```console
-$ hugo server -t toha -w
+$ hugo server --theme toha --watch
 ```
 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/).
@@ -148,16 +173,20 @@ When you run your site for first time, it will start with the default parameters
 Here, are some handy shortcodes you can use with this theme.
- [Alert](https://toha-guides.netlify.app/posts/short-codes/alert/)
+- [Alert](https://toha-guides.netlify.app/posts/shortcodes/#alert)
- [Image](https://toha-guides.netlify.app/posts/short-codes/img/)
+- [Image](https://toha-guides.netlify.app/posts/shortcodes/#image)
- [Split](https://toha-guides.netlify.app/posts/short-codes/split/)
+- [Split](https://toha-guides.netlify.app/posts/shortcodes/#split)
- [Vertical Space](https://toha-guides.netlify.app/posts/short-codes/vs/)
+- [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**
@@ -219,37 +248,61 @@ Here, are the current plan and progress of various components of this theme. The
  - [ ] Links
  - [ ] Gallery
- [ ] **Accomplishment / Courses**
+- [x] **Accomplishment / Courses**
-  - [ ] Overview
+  - [x] Overview
-  - [ ] Certificate
+  - [x] Certificate
 - [x] **Achievements Gallery**
  - [x] Image
  - [x] Summary
-### List Page
+### 2. Blog Mode
- [x] Post Cards
+Here is the checklist for blog mode,
 - [x] Sidebar
 - [x] Pagination
-### Reading Page
+- [ ] **Dedicated Home page**
- [x] Hero Image
+- [x] **List Page**
 - [x] Author Information
 - [x] Sidebar
 - [x] Table of Contents
 - [x] Next & Previous Page Navigation
 - [x] `Improve This Page` Button
 - [x] Disqus Comment
-### 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
@@ -257,6 +310,7 @@ Here, are the current plan and progress of various components of this theme. The
 - [x] Alert
 - [ ] Figure & sub-figure
 - [ ] Tabs
 - [x] Notes
 ## Contributing
@@ -324,7 +378,7 @@ $ git commit -m "A meaningful commit message"
 $ git push my-fork my-feature-branch
 ```
-Then, open a PR against `master` branch of [hugo-toha/toha](https://github.com/hugo-toha/toha) from the `my-feature-branch` branch of your own fork.
+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
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -1,5 +1,7 @@
 ---
 title: "Search Results"
 date: 2010-06-08T08:06:25+06:00
 weight: 999999
 sitemap:
  priority : 0.1
 layout: "search"
@@ -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"
 ]
 \```
@@ -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"
 ]
 \```
@@ -1,91 +0,0 @@
 baseURL: http://example.org/
 languageCode: en-us
 defaultContentLanguage: en
 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
  bn:
    languageName: বাংলা
    weight: 2
  fr:
    languageName: Français
    weight: 3
  id:
    languageName: Indonesian
    weight: 4
  de:
    languageName: Deutsch
    weight: 5
  es:
    languageName: Spanish
    weight: 6
  it:
    languageName: Italian
    weight: 7
  cn:
    languageName: 中文
    weight: 8
 # At least HTML and JSON are required for the main HTML content and
 # client-side JavaScript search
 outputs:
  home:
    - HTML
    - RSS
    - JSON
 # 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
 # Site parameters
 params:
  # Background image of the landing page
  background: /images/site/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 default to the theme logos if not provided.
  logo:
    main: /images/site/main-logo.png
    inverted: /images/site/inverted-logo.png
    favicon: /images/site/favicon.png
  # GitHub repo URL of your site
  gitRepo: https://github.com/hugo-toha/hugo-toha.github.io
  gitBranch: main
  # 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.
  newsletter:
    enable: true
@@ -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/author/john.png"
 # give your some contact information. they will be used in the footer
 contactInfo:
  ইমেইল: "johndoe@example.com"
  ফোন: "+0123456789"
 # some summary about what you do
 summary:
  - আমি একজন ডেভেলপার
  - আমি ওপেন সোর্স প্রোজেক্ট এ কাজ করতে পছন্দ করি
  - আমি মজার কিছু প্রোজেক্ট এ কাজ করতে ভালবাসি
@@ -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: 'আমি X বছর অভিজ্ঞতা সম্পন্ন একজন দক্ষ সফটওয়্যার ইঞ্জিনিয়ার । আমি Go ভাষা ব্যবহার  করে [Kubernetes](https://kubernetes.io/) এর জন্য ওপেন সোর্স টুল তৈরি করি । মাঝে মাঝে আমি থিম বানানোর মত মজার প্রোজেক্ট নিয়ে কাজ করি ।'
 # 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"
@@ -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: সেরা উপস্থাপক
  image: /images/sections/achievements/presenter.jpg
  summary: 2020 XYZ কনফারেন্স এ সেরা উপস্থাপক
 - title: বিজয়ী
  image: /images/sections/achievements/sport.jpg
  summary: আন্তঃ শহর সাইক্লিং প্রতিযোগিতা ২০২০ এ বিজয়ী
 - title: গ্রাজুয়েশন
  image: /images/sections/achievements/graduation-cap.jpg
  summary: XYZ ইউনিভার্সিটি থেকে কম্পিউটার বিজ্ঞানে স্নাতক  সম্পন্ন করেছি
 - title: পুরুস্কার বিজয়ী
  image: /images/sections/achievements/woman-winner.jpg
  summary: IEE Conference 2020 এ সেরা গবেষণাপত্রের পুরষ্কার বিজয়ী হয়েছি
@@ -1,89 +0,0 @@
 # section information
 section:
  name: শিক্ষা জীবন
  id: education
  template: sections/education.html
  enable: true
  weight: 4
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 degrees:
 - name: কোয়ান্টাম ক্রিপ্টোগ্রাফিতে পি. এইচ. ডি.
  icon: fa-microscope
  timeframe: ২০১৬-২০২০
  institution:
    name: এ. বি. সি. প্রযুক্তি বিশ্ববিদ্যালয়
    url: "#"
  grade:
    scale: সিজিপিএ
    achieved: ৪
    outOf: ৩.৬
  publications:
  - title: অর্থহীন লেখা যার মাঝে আছে অনেক কিছু।
    url: "#"
  - title: হ্যাঁ, এই লেখার মাঝেই আছে অনেক কিছু।
    url: "#"
  - title: যদি তুমি মনে করো, এটা তোমার কাজে লাগবে, তাহলে তা লাগবে কাজে।
    url: "#"
 - name: কম্পিউটার সায়েন্স এন্ড ইঞ্জিনিয়ারিং এ বি.এসসি
  icon: fa-graduation-cap
  timeframe: ২০১২-২০১৬
  institution:
    name: এক্স ওয়াই জেড বিশ্ববিদ্যালয়
    url: "#"
  grade:
    scale: সিজিপিএ
    achieved: ৪
    outOf: ৩.৫
  takenCourses:
    # if true, the courses will be rendered as a table otherwise it will render as a list and the grades will be hidden.
    showGrades: true
    courses:
    - name: ডেটা স্ট্রাকচারস এবং অ্যালগরিদম
      achieved: ৩.৭৫
      outOf: ৪
    - name: নেটওয়ার্ক সিকিউরিটি
      achieved: ৩.৮০
      outOf: ৪
    - name: অপারেটিং সিস্টেম
      achieved: ৩.৫
      outOf: ৪
    - name: কৃত্রিম বুদ্ধিমত্তা
      achieved: ৩.৭৫
      outOf: ৪
  publications:
  - title: নিজের ভাষায় লেখা দেখতে অভ্যস্ত হও।
    url: "#"
  - title: মনে রাখবে লেখা অর্থহীন হয়, যখন তুমি তাকে অর্থহীন মনে করো; আর লেখা অর্থবোধকতা তৈরি করে, যখন তুমি তাতে অর্থ ঢালো।
    url: "#"
  extracurricularActivities:
  - কোনো লেখাই তোমার কাছে অর্থবোধকতা তৈরি করতে পারে, যদি তুমি সেখানে অর্থদ্যোতনা দেখতে পাও।
  - যে কথাকে কাজে লাগাতে চাও, তাকে কাজে লাগানোর কথা চিন্তা করার আগে ভাবো, তুমি কি সেই কথার জাদুতে আচ্ছন্ন হয়ে গেছ কিনা।
  - তুমি যদি নিশ্চিত হও যে, তুমি কোনো মোহাচ্ছাদিত আবহে আবিষ্ট হয়ে অন্যের শেখানো বুলি আত্মস্থ করছো না, তাহলে তুমি নির্ভয়ে, নিশ্চিন্তে অগ্রসর হও।
  - তুমি সেই কথাকে জানো, বুঝো, আত্মস্থ করো; মনে রাখবে, যা অনুসরণ করতে চলেছো, তা আগে অনুধাবন করা জরুরি; এখানে কিংকর্তব্যবিমূঢ় হবার কোনো সুযোগ নেই।
 - name: উচ্চমাধ্যমিক সার্টিফিকেট
  icon: fa-university
  timeframe: ২০১০-২০১২
  institution:
    name: এমএসটি বিজ্ঞান কলেজ
    url: "#"
  grade:
    scale: জিপিএ
    achieved: ৫
    outOf: ৫
  extracurricularActivities:
  - কোনো কথা শোনামাত্রই কি তুমি তা বিশ্বাস করবে?
  - হয়তো বলবে, করবে, হয়তো বলবে “আমি করবো না।”
  - তাই কোন কথাটি কাজে লাগবে, তা নির্ধারণ করবে তুমি— হ্যাঁ, তুমি।
  - নিজেই ঠিক করো, নিজের ভাষাটা কি অর্থহীন, নাকি কিছু সত্যিই বলছে!
 - name: মাধ্যমিক সার্টিফিকেট
  icon: fa-school
  timeframe: ২০০৫-২০১০
  institution:
    name: জে কে স্কুল অফ সায়েন্স
  grade:
    scale: জিপিএ
    achieved: ৫
    outOf: ৪.৫
@@ -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: ঢাকা ব্রাঞ্চ
    # company overview
    overview: Example Co. হচ্ছে ক্লাউড নেটিভ ডেভেলপমেন্টের জন্যে একটি স্বীকৃত প্রতিষ্ঠান । এটি Kubernetes এর জন্যে বিভিন্ন সফটওয়্যার বানায়।
  positions:
  - designation: সিনিয়র সফটওয়্যার ইঞ্জিনিয়ার
    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:
    - ABC কাজের জন্য XYZ টুল ডিজাইন ও ডেভেলপ করা ।
    - Kubernetes এর ভলিউম, ডাটাবেজ ইত্যাদি ব্যাকআপ নেওয়ার জন্যে বিপর্যয় পুনরুদ্ধার টুল ডিজাইন, ডেভেলপ এবং পরিচালনা করা। 
    - বাকেন্ড টিমের নেতৃত্ব দেওয়া।
  - designation: জুনিয়র সফটওয়্যার ইঞ্জিনিয়ার
    start: Nov 2017
    end: Oct 2019
    responsibilities:
    - ABC টুল এর জন্য XYZ ফিচার বাস্তবায়ন করা এবং টেস্ট করা।
    - ABC টুলের ক্লায়েন্ট সাপোর্ট দেওয়া।
    - XYZ এর জন্য K, D, W টেকনোলজি শিখা।
 - company:
    name: PreExample Co.
    url: "https://www.preexample.com"
    location: Nowhere
    overview: PreExample Co. হচ্ছে Example co.  তে যাওয়ার মাধ্যম। সুতারাং, এখানে বিশেষ কিছু নেই।
  positions:
  - designation: সফটওয়্যার ইঞ্জিনিয়ার
    start: March 2016
    end: May 2017
    responsibilities:
    - প্রচুর পরিমাণে উদাহারন কোড লিখা ।
    - প্রচুর পরিমাণে উদাহারন পড়া।
    - প্রচুর পরিমাণে উদাহারন ভিডিও দেখা ।
 - company:
    name: Intern Counting Company (ICC).
    url: "https://www.intern.com"
    location: Intern Land
    overview: Intern counting Company (ICC) বিশ্বব্যাপী ইন্টার্ন ইঞ্জিনিয়ারদের গণনার জন্য দায়ী ।
  positions:
  - designation: ইন্টার্ন
    start: Jun 2015
    end: Jan 2016
    responsibilities:
    - প্রচুর ইন্টার্ন গণনা করা।
    - আরও ইন্টার্ন গণনা করা।
    - নিজেকে  ইন্টার্ন হিসেবে গণনা করা ।
@@ -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: সব বিষয়
  filter: "all"
 - name: প্রোফেসনাল
  filter: "professional"
 - name: প্রাতিষ্ঠানিক
  filter: "academic"
 - name: শখের প্রোজেক্ট
  filter: "hobby"
 # your projects
 projects:
 - name: Kubernetes
  logo: /images/sections/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/sections/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"]
 - 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/sections/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/sections/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"]
@@ -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
@@ -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
  logo: "/images/sections/skills/kubernetes.png"
  summary: "আমি Kubernetes এ অ্যাপ্লিকেশান পরিচালনা করতে সক্ষম । আমার  Kubernetes এ CRD এর জন্য কন্ট্রোলার লিখার অভিজ্ঞতা আছে ।"
  url: "https://kubernetes.io/"
 - name: Go ডেভেলপমেন্ট
  logo: "/images/sections/skills/go.png"
  summary: "ডেভেলপমেন্টের জন্য প্রধান ভাষা হিসেবে ব্যবহার করছি। টেস্ট যোগ্য,  রক্ষণাবেক্ষণ যোগ্য কোড লিখতে সক্ষম।"
  url: "https://golang.org/"
 - name: ক্লাউড কম্পিউটিং
  logo: "/images/sections/skills/cloud.png"
  summary: "GCP, AWS, Azure গুলোর মত বেশিরভাগ বড় বড় ক্লাউড নিয়ে কাজর অভিজ্ঞতা আছে।"
 - name: Docker
  logo: "/images/sections/skills/docker.svg"
  summary: "বেশির ভাগ প্রোগ্রামেরই  Docker কন্টেইনার তৈরি করি। মাল্টি স্টেজ এবং মাল্টি আর্কিটেকচার কন্টেইনার নিয়ে অভিজ্ঞতা আছে।"
  url: "https://www.docker.com/"
 - name: Prometheus
  logo: "/images/sections/skills/prometheus.png"
  summary: "Prometheus metrics সেটআপ ও কনফিগার করতে সক্ষম। PromQL, AlertManager নিয়ে অভিজ্ঞতা আছে। Metric exporters লিখাতেও অভিজ্ঞতা আছে।"
  url: "https://prometheus.io/"
 - name: লিনাক্স
  logo: "/images/sections/skills/linux.png"
  summary: "প্রধান অপারেটিং সিস্টেম হিসেবে ব্যবহার করছি। bash/shell scripts লিখতে সক্ষম।"
 - name: গিট
  logo: "/images/sections/skills/git.png"
  summary: "গিট ভিত্তিক ডেভেলপমেন্টের অভিজ্ঞতা আছে। বেশির ভাগ ক্ষেতরেই GitHub ব্যবহার করি তবে GitLab ব্যবহারেরও অভিজ্ঞতা আছে।"
  url: "https://git-scm.com/"
 - name: C++
  logo: "/images/sections/skills/c++.png"
  summary: "বেসিক C/C++ প্রোগ্রামিং জানি । প্রব্লেম সল্ভিং এবং কন্টেস্ট এর জন্য ব্যবহার করেছি।"
@@ -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: জন ডো এর বাক্তিগত পোর্টফোলিও ও ব্লগ.
 # 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://toha-guides.netlify.app/posts/
@@ -1,18 +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/author/john.png"
 # give your some contact information. they will be used in the footer
 contactInfo:
  邮箱: "qiaoyi@example.com"
  电话: "+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
@@ -1,82 +0,0 @@
 # section information
 section:
  name: 简介
  id: about
  enable: true
  weight: 1
  showOnNavbar: true
  template: sections/about.html
 # your designation
 designation: 软件工程师
 # your company information
 company:
  name: 某某公司.
  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: "我是一个软件工程师，就职于某某公司，巴拉巴拉."
 # 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: PGP key
    icon: "fab fa-keybase"
    url: "#"
  - name: LinkedIn
    icon: "fab fa-linkedin"
    url: "#"
  - name: Twitter
    icon: "fab fa-twitter"
    url: "#"
  - name: Facebook
    icon: "fab fa-facebook"
    url: "#"
  - name: Steam
    icon: "fab fa-steam"
    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: 领导能力
    percentage: 90
    color: blue
  - name: 团队合作
    percentage: 90
    color: yellow
  - name: 沟通能力
    percentage: 85
    color: pink
  - name: 辛勤刻苦
    percentage: 85
    color: green
  - name: 接受能力
    percentage: 85
    color: sky
  - name: 攻坚能力
    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"
@@ -1,24 +0,0 @@
 # section information
 section:
  name: 成就
  id: achievements
  enable: true
  weight: 7
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # Your achievements achievements
 achievements:
 - title: Best Presenter
  image: /images/sections/achievements/presenter.jpg
  summary: Best presenter in the 2020 XYZ conference.
 - title: Champion
  image: /images/sections/achievements/sport.jpg
  summary: Champion in cycling inter-city cycling championship 2020.
 - title: Graduation
  image: /images/sections/achievements/graduation-cap.jpg
  summary: Received Bachelor of Science (B.Sc.) in Computer Science and Engineer from XYZ University.
 - title: Award Winner
  image: /images/sections/achievements/woman-winner.jpg
  summary: Wined best paper award at IEE Conference 2020.
@@ -1,89 +0,0 @@
 # section information
 section:
  name: 学历
  id: education
  template: sections/education.html # Use "sections/education-alt.html for alternate template.
  enable: true
  weight: 4
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 degrees:
 - name: Ph.D in Quantum Cryptography
  icon: fa-microscope
  timeframe: 2016-2020
  institution:
    name: ABC University of Technology
    url: "#"
  grade: #(optional)
    scale: CGPA
    achieved: 3.6
    outOf: 4
  publications: #(optional)
  - title: Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    url: "#"
  - title: Fusce eu augue ut odio porttitor pulvinar.
    url: "#"
  - title: Nullam vitae orci tincidunt purus viverra pulvinar.
    url: "#"
 - name: B.Sc. in Computer Science & Engineering
  icon: fa-graduation-cap
  timeframe: 2012-2016
  institution:
    name: University of XYZ
    url: "#"
  grade: #(optional)
    scale: CGPA
    achieved: 3.5
    outOf: 4
  takenCourses: #(optional)
    # if true, the courses will be rendered as a table otherwise it will render as a list and the grades will be hidden.
    showGrades: true
    courses:
    - name: Data Structures and Algorithm
      achieved: 3.75
      outOf: 4
    - name: Network Security
      achieved: 3.80
      outOf: 4
    - name: Operating System
      achieved: 3.5
      outOf: 4
    - name: Artificial Intelligent
      achieved: 3.75
      outOf: 4
  publications: #(optional)
  - title: Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    url: "#"
  - title: Fusce eu augue ut odio porttitor pulvinar.
    url: "#"
  extracurricularActivities: #(optional)
  - In vitae facilisis est, eget porta sem.
  - Vestibulum consectetur lorem justo, at laoreet lorem feugiat et.
  - Duis sed massa feugiat, ornare justo et, aliquam est.
  - Pellentesque ut fringilla magna.
 - name: Higher Secondary School Certificate
  icon: fa-university
  timeframe: 2010-2012
  institution:
    name: MST College of Science
    url: "#"
  grade: #(optional)
    scale: GPA
    achieved: 5
    outOf: 5
  extracurricularActivities: #(optional)
  - In vitae facilisis est, eget porta sem.
  - Vestibulum consectetur lorem justo, at laoreet lorem feugiat et.
  - Duis sed massa feugiat, ornare justo et, aliquam est.
  - Pellentesque ut fringilla magna.
 - name: Secondary School Certificate
  icon: fa-school
  timeframe: 2005-2010
  institution:
    name: JK School of Science
  grade: #(optional)
    scale: GPA
    achieved: 4.5
    outOf: 5
@@ -1,64 +0,0 @@
 # section information
 section:
  name: 履历
  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.
@@ -1,64 +0,0 @@
 # section information
 section:
  name: 项目
  id: projects
  enable: true
  weight: 5
  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/sections/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/sections/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"]
 - 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/sections/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/sections/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"]
@@ -1,11 +0,0 @@
 # section information
 section:
  name: 最近文章
  id: recent-posts
  enable: true
  weight: 6
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # no additional configuration is required
@@ -1,49 +0,0 @@
 # section information
 section:
  name: 技能
  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/sections/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/sections/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/sections/skills/cloud.png"
  summary: "Worked with most of the major clouds such as GCP, AWS, Azure etc."
 - name: Docker
  icon: "/images/sections/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/sections/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/sections/skills/linux.png"
  summary: "Using as the main operating system. Capable of writing bash/shell scripts."
 - name: Git
  icon: "/images/sections/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/sections/skills/c++.png"
  summary: "Know basic C/C++ programming. Used for contest programming and problem solving."
@@ -1,13 +0,0 @@
 # Copyright Notice
 copyright: © 2008 - 2021 Copyright.
 # Meta description for your site.  This will help the search engines to find your site.
 description: Portfolio and personal blog of John 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://toha-guides.netlify.app/posts/
  # - name: 关于 #这里可以放个人说明页
  #   url: about
@@ -1,18 +0,0 @@
 # some information about you
 name: "John Doe"
 nickname: "John"
 # greeting message before your name. it will default to "Hi! I am" if not provided
 greeting: "Hi, I am"
 image: "images/author/john.png"
 # give your some contact information. they will be used in the footer
 contactInfo:
  email: "johndoe@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
@@ -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"
@@ -1,24 +0,0 @@
 # section information
 section:
  name: Achievements
  id: achievements
  enable: true
  weight: 7
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # Your achievements achievements
 achievements:
 - title: Best Presenter
  image: /images/sections/achievements/presenter.jpg
  summary: Best presenter in the 2020 XYZ conference.
 - title: Champion
  image: /images/sections/achievements/sport.jpg
  summary: Champion in cycling inter-city cycling championship 2020.
 - title: Graduation
  image: /images/sections/achievements/graduation-cap.jpg
  summary: Received Bachelor of Science (B.Sc.) in Computer Science and Engineer from XYZ University.
 - title: Award Winner
  image: /images/sections/achievements/woman-winner.jpg
  summary: Wined best paper award at IEE Conference 2020.
@@ -1,89 +0,0 @@
 # section information
 section:
  name: Education
  id: education
  template: sections/education.html # Use "sections/education-alt.html for alternate template.
  enable: true
  weight: 4
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 degrees:
 - name: Ph.D in Quantum Cryptography
  icon: fa-microscope
  timeframe: 2016-2020
  institution:
    name: ABC University of Technology
    url: "#"
  grade: #(optional)
    scale: CGPA
    achieved: 3.6
    outOf: 4
  publications: #(optional)
  - title: Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    url: "#"
  - title: Fusce eu augue ut odio porttitor pulvinar.
    url: "#"
  - title: Nullam vitae orci tincidunt purus viverra pulvinar.
    url: "#"
 - name: B.Sc. in Computer Science & Engineering
  icon: fa-graduation-cap
  timeframe: 2012-2016
  institution:
    name: University of XYZ
    url: "#"
  grade: #(optional)
    scale: CGPA
    achieved: 3.5
    outOf: 4
  takenCourses: #(optional)
    # if true, the courses will be rendered as a table otherwise it will render as a list and the grades will be hidden.
    showGrades: true
    courses:
    - name: Data Structures and Algorithm
      achieved: 3.75
      outOf: 4
    - name: Network Security
      achieved: 3.80
      outOf: 4
    - name: Operating System
      achieved: 3.5
      outOf: 4
    - name: Artificial Intelligent
      achieved: 3.75
      outOf: 4
  publications: #(optional)
  - title: Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    url: "#"
  - title: Fusce eu augue ut odio porttitor pulvinar.
    url: "#"
  extracurricularActivities: #(optional)
  - In vitae facilisis est, eget porta sem.
  - Vestibulum consectetur lorem justo, at laoreet lorem feugiat et.
  - Duis sed massa feugiat, ornare justo et, aliquam est.
  - Pellentesque ut fringilla magna.
 - name: Higher Secondary School Certificate
  icon: fa-university
  timeframe: 2010-2012
  institution:
    name: MST College of Science
    url: "#"
  grade: #(optional)
    scale: GPA
    achieved: 5
    outOf: 5
  extracurricularActivities: #(optional)
  - In vitae facilisis est, eget porta sem.
  - Vestibulum consectetur lorem justo, at laoreet lorem feugiat et.
  - Duis sed massa feugiat, ornare justo et, aliquam est.
  - Pellentesque ut fringilla magna.
 - name: Secondary School Certificate
  icon: fa-school
  timeframe: 2005-2010
  institution:
    name: JK School of Science
  grade: #(optional)
    scale: GPA
    achieved: 4.5
    outOf: 5
@@ -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.
@@ -1,64 +0,0 @@
 # section information
 section:
  name: Projects
  id: projects
  enable: true
  weight: 5
  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/sections/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/sections/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"]
 - 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/sections/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/sections/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"]
@@ -1,11 +0,0 @@
 # section information
 section:
  name: Recent Posts
  id: recent-posts
  enable: true
  weight: 6
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # no additional configuration is required
@@ -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
  logo: "/images/sections/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
  logo: "/images/sections/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
  logo: "/images/sections/skills/cloud.png"
  summary: "Worked with most of the major clouds such as GCP, AWS, Azure etc."
 - name: Docker
  logo: "/images/sections/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
  logo: "/images/sections/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
  logo: "/images/sections/skills/linux.png"
  summary: "Using as the main operating system. Capable of writing bash/shell scripts."
 - name: Git
  logo: "/images/sections/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++
  logo: "/images/sections/skills/c++.png"
  summary: "Know basic C/C++ programming. Used for contest programming and problem solving."
@@ -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 John 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: Docs
  url: https://toha-guides.netlify.app/posts/
@@ -1,20 +0,0 @@
 # some information about you
 name: "John Doe"
 nickname: "John"
 # greeting message before your name. it will default to "Hi! I am" if not provided
 greeting: "Bonjour, je suis"
 image: "images/author/john.png"
 # give your some contact information. they will be used in the footer
 contactInfo:
  email: "johndoe@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
@@ -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"
@@ -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/sections/achievements/presenter.jpg
  summary: Meilleur présentateur de la conférence XYZ 2020.
 - title: Champion
  image: /images/sections/achievements/sport.jpg
  summary: Champion du championnat cycliste interurbain 2020.
 - title: Remise des diplômes
  image: /images/sections/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/sections/achievements/woman-winner.jpg
  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Possimus architecto minus facere vero?
@@ -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.
@@ -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/sections/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/sections/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/sections/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/sections/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"]
@@ -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
@@ -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
  logo: "/images/sections/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
  logo: "/images/sections/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
  logo: "/images/sections/skills/cloud.png"
  summary: "A travaillé avec la plupart des principaux nuages tels que GCP, AWS, Azure, etc."
 - name: Docker
  logo: "/images/sections/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
  logo: "/images/sections/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
  logo: "/images/sections/skills/linux.png"
  summary: "Utilisé comme système d'exploitation principal. Capable d'écrire des scripts bash/shell."
 - name: Git
  logo: "/images/sections/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++
  logo: "/images/sections/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."
@@ -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: Docs
  url: https://toha-guides.netlify.app/posts/
@@ -1,18 +0,0 @@
 # some information about you
 name: "John Doe"
 nickname: "John"
 # greeting message before your name. it will default to "Hi! I am" if not provided
 greeting: "Halo, saya"
 image: "images/author/john.png"
 # give your some contact information. they will be used in the footer
 contactInfo:
  email: "johndoe@example.com"
  phone: "+0123456789"
 # some summary about what you do
 summary:
  - Saya seorang developer
  - Saya mengerjakan System
  - Saya suka dengan servers
  - Saya melakukan projek open-source
  - Projek-projek yang seru sangat menarik buat saya
@@ -1,78 +0,0 @@
 # section information
 section:
  name: Tentang Saya
  id: about
  enable: true
  weight: 1
  showOnNavbar: true
  template: sections/about.html
 # your designation
 designation: Programmer
 # 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: 'Saya seorang insinyur perangkat lunak yang bersemangat dengan pengalaman kerja x tahun. Saya membuat alat OSS untuk [Kubernetes] (https://kubernetes.io/) menggunakan GO. Alat saya membantu orang untuk menyebarkan beban kerja mereka di Kubernetes. Terkadang, saya mengerjakan beberapa proyek menyenangkan seperti menulis tema, dll.'
 # 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: Kepemimpinan
  percentage: 85
  color: blue
 - name: Bekerja dengan Tim
  percentage: 90
  color: yellow
 - name: Komunikasi
  percentage: 85
  color: pink
 - name: Kerja Keras
  percentage: 85
  color: green
 - name: Belajar Cepat
  percentage: 85
  color: sky
 - name: Menyelesaikan Masalah
  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"
@@ -1,24 +0,0 @@
 # section information
 section:
  name: Presentasi
  id: achievements
  enable: true
  weight: 6
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # Your achievements achievements
 achievements:
 - title: Presenter Terbaik
  image: /images/sections/achievements/presenter.jpg
  summary: Best presenter in the 2020 XYZ conference.
 - title: Juara
  image: /images/sections/achievements/sport.jpg
  summary: Champion in cycling inter-city cycling championship 2020.
 - title: Wisuda
  image: /images/sections/achievements/graduation-cap.jpg
  summary: Received Bachelor of Science (B.Sc.) in Computer Science and Engineer from XYZ University.
 - title: Pemenang Award
  image: /images/sections/achievements/woman-winner.jpg
  summary: Lorem ipsum dolor sit amet consectetur adipisicing elit. Possimus architecto minus facere vero?
@@ -1,64 +0,0 @@
 # section information
 section:
  name: Pengalaman
  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. adalah perusahaan yang dikenal luas untuk pengembangan cloud-native. Itu membangun alat untuk 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: Okt 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. adalah perusahaan gateway untuk masuk ke Example co. Jadi, tidak ada yang istimewa di sini.
  positions:
  - designation: Software Engineer
    start: Maret 2016
    end: Mei 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: Perusahaan penghitung magang (ICC) bertanggung jawab untuk menghitung Insinyur magang di seluruh dunia.
  positions:
  - designation: Intern
    start: Jun 2015
    end: Jan 2016
    responsibilities:
    - Count lost of interns.
    - Count more interns.
    - Count me as an intern.
@@ -1,64 +0,0 @@
 # section information
 section:
  name: Projek
  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: Profesional
  filter: "profesional"
 - name: Akademik
  filter: "akademik"
 - name: Hobi
  filter: "hob1"
 # your projects
 projects:
 - name: Kubernetes
  logo: /images/sections/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/sections/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"]
 - 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/sections/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/sections/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"]
@@ -1,11 +0,0 @@
 # section information
 section:
  name: Artikel Akhir
  id: recent-posts
  enable: true
  weight: 5
  showOnNavbar: true
  # Can optionally hide the title in sections
  # hideTitle: true
 # no additional configuration is required
--- a/Show More
+++ b/Show More