Adding arabic tranlations

.github/workflows/automerge-prs.yml

@@ -0,0 +1,33 @@
+name: automerge
+on:
+  pull_request:
+    types:
+      - labeled
+      - unlabeled
+      - synchronize
+      - opened
+      - edited
+      - ready_for_review
+      - reopened
+      - unlocked
+  pull_request_review:
+    types:
+      - submitted
+  check_suite:
+    types:
+      - completed
+  status: {}
+jobs:
+  automerge:
+    runs-on: ubuntu-20.04
+    steps:
+      - name: automerge
+        uses: "pascalgn/[email protected]"
+        env:
+          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
+          MERGE_LABELS: "auto-merge,!work in progress"
+          MERGE_REMOVE_LABELS: "auto-merge"
+          MERGE_FORKS: "false"
+          MERGE_RETRIES: "6"
+          MERGE_RETRY_SLEEP: "10000"
+          MERGE_DELETE_BRANCH: "true"

.github/workflows/lint-and-generate-html-from-markdown.yml

@@ -0,0 +1,30 @@
+name: Lint & Generate HTML from Markdown
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+
+defaults:
+  run:
+    shell: bash
+    working-directory: .operations
+
+jobs:
+  lint:
+    name: Lint
+    runs-on: ubuntu-20.04
+    env:
+      NODE_ENV: test
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v3
+        with:
+          node-version: "18"
+
+      - run: npm install
+      - run: npm run lint

.github/workflows/update-date-in-last-update-badge.yml

@@ -0,0 +1,39 @@
+name: Update date in last update badge
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  run:
+    name: Update the date in last update badge to today
+    runs-on: ubuntu-20.04
+
+    # Limit this action to only run on the main repo and not on forks
+    if: github.repository_owner == 'goldbergyoni'
+
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v3
+
+      - name: Update last update badge
+        run: |
+          # Make file runnable
+          chmod +x "${GITHUB_WORKSPACE}/.github/workflows/update-last-update-badge.sh"
+          # Run script
+          "${GITHUB_WORKSPACE}/.github/workflows/update-last-update-badge.sh" "${GITHUB_WORKSPACE}/README.md"
+
+      - name: Commit & Create Pull Request
+        uses: peter-evans/create-pull-request@v4
+        with:
+          commit-message: update the last update badge to today [skip ci]
+          author: Update Last Update Badge Action <${{ github.actor }}@users.noreply.github.com>
+          branch: update-last-update-badge
+          delete-branch: true
+          title: 'Update last update badge to today [skip ci]'
+          labels: |
+            update-last-update-badge
+            auto-merge
+
+          # Force empty body as the action have default body
+          body: ''

.github/workflows/update-last-update-badge.sh

@@ -0,0 +1,61 @@
+#!/bin/bash
+set -e
+
+INPUT_FILE=$1
+
+url_encode() {
+    # url_encode <string>
+    local length="${#1}"
+    for (( i = 0; i < length; i++ )); do
+        local c="${1:i:1}"
+        case $c in
+            [a-zA-Z0-9.~_-]) printf "$c" ;;
+            *) printf '%%%02X' "'$c" ;;
+        esac
+    done
+}
+
+is_there_last_update_badge() {
+    local input_file=$1
+    local updated_badge_regex=$2
+
+    if grep -q "$updated_badge_regex" "$input_file"; then return 0
+    else return 1
+    fi
+}
+
+is_last_update_badge_date_is_today() {
+    local input_file=$1
+    local updated_badge=$2
+
+    if grep -q "$updated_badge" "$input_file"; then return 0
+    else return 1
+    fi
+}
+
+
+# We use already encoded string emoji because I'm on Windows and the calendar emoji failed to render
+CALENDAR_EMOJI_ENCODED='%F0%9F%93%85'
+
+# Date format example: March 03, 2021
+CURRENT_DATE=`date +"%B %d, %Y"`
+
+# We explicitly matching the img.shields.io/badge because when we change the provider of the badge the input will be changed too
+LAST_UPDATE_BADGE_REGEX='<img id="last-update-badge" src="https:\/\/img\.shields\.io\/badge\/[^>]*>'
+
+UPDATED_BADGE_URL="https:\/\/img.shields.io\/badge\/${CALENDAR_EMOJI_ENCODED}$(url_encode " Last update - ${CURRENT_DATE}-green").svg"
+UPDATED_LAST_UPDATE_BADGE="<img id=\"last-update-badge\" src=\"$UPDATED_BADGE_URL\" alt=\"Last update: $CURRENT_DATE\" />"
+
+
+if ! is_there_last_update_badge "$INPUT_FILE" "$LAST_UPDATE_BADGE_REGEX"; then
+    # Print with red foreground
+    echo -e "\033[31mError: Can't find Last update badge\033[m"
+    exit 1
+fi
+
+if is_last_update_badge_date_is_today "$INPUT_FILE" "$UPDATED_LAST_UPDATE_BADGE"; then
+    echo "No need to update the $INPUT_FILE, the last update badge already pointing to today"
+    exit 0
+fi
+
+sed -i "s@$LAST_UPDATE_BADGE_REGEX@$UPDATED_LAST_UPDATE_BADGE@" "$INPUT_FILE"

.operations/CONTRIBUTING.md

@@ -1,44 +1,61 @@
 # Contribution guidelines
 
-## What you should know first?
-
-### Lovely & friendly atmosphere
+## Lovely & friendly atmosphere
 
 Our code of conduct is 5 words long: we are all friends here
 
 We recognize that being professional and kind are the same thing and strive to maximize our professionalism
 
-### Maintenance work
+## Handling issues and PRs
 
-Our operations manual [can be found here](https://github.com/goldbergyoni/nodebestpractices/blob/master/.operations/operations-manual.md)
+<br/>
+In a nutshell, every issue is an opprtunity to gain new knowledge and attract new contributor. Therefore we aim for vast response and welcoming words 💚
 
-### Writing guidelines
+When merging a new PR, add the contributor to our credits list using the all-contributors bot. Just include this text as a PR comment:
 
-Our content writing guidelines [can be found here](https://github.com/goldbergyoni/nodebestpractices/blob/master/.operations/writing-guidelines.md)
+`@all-contributors please add @username for content`
 
+The specific PR/issue resolustion depends on its kind:
 
-## Contribution model
+**A. New best practice or fundamental changes to existing content -** In that case, involve at least 1 other members to solicit enough feedback for this change. Start by greeting the contributor, ensure the formalities are fine, ensure it conforms to our [writing guidelines](./writing-guidelines.md), ensure enough information was provided and then get at least 1 more collaborators and allow at least a week for comments
 
-### Steering committee 🏆
+**B. Plain text change (e.g. Grammar correctness) -** When super-simple wording edits are proposed (i.e. not new content rather language correctness), one can just greet, approve and merge immediately
 
-Members of the steering committee work together to provide guidance and future direction to the project. Each committee member has a particular expertise which they share their knowledge on, and work to lead further improvements to the project in that area. The steering committee members are responsible for approving new best practices, and ensuring current best practices remain relevant.
+**C. Translations to a new (not existing) language -** When offered to add new language, greet the person and paste our [translation guidelines](./common-answers.md)
 
-### Collaborators 👍
+**D. Edits to existing translations -** If the change can be inferred by the reviewer (e.g., a change of a symbol, number or just date update) then feel free to merge alone. If familiarity with the language is needed, tag the original translator and ask for feedback. The translators name can be found in the home page under "Translations"
 
-Collaborators are members who are contributing to the repository on a regular basis, through suggesting new best practices, triaging issues, reviewing pull requests and more. Along with the steering committee, each collaborator leads a project tracked under our Github projects.
+**D. Dicussions and ideas -** When a technical discussion or just general conversation is brought into a new issue, apply your own judgements whether to tag other collaborators
 
-The role is in place to help the steering committee ensure that the content provided is of a high standard, up-to-date with the industry, and available in many languages. Members who frequently participate in these activities will be invited to become a collaborator, based on the quality of their contributions.
 
-The steering committee periodically reviews the collaborator list to identify inactive collaborators. Inactive collaborators can choose to either continue in or step down from their role, in which case they are acknowledged as a past collaborator. They may later request that the steering committee restore them to active status.
+## Assets to be aware of
 
-### Other contributions ✨
+- Our content writing guidelines [can be found here](./writing-guidelines.md)
+- Common questions and answers to issues/PRs [can be found here](./common-answers.md)
 
-This project follows the [All Contributors Specification](https://allcontributors.org/), which means we recognize all types of contributions, whether they are new suggested best practices/ideas, translations, or new content.
+## Precommit
 
-If you have contributed to the project in some way and aren't listed, please add an entry for yourself by using the @all-contributors-bot in a Pull Request or issue. Examples:
+Before pushing, verify your Markdown passes [the linter](https://www.npmjs.com/package/markdownlint-cli) :
 
-`@all-contributors-bot please add @js-kyle for code`
+```bash
+npm run lint
+```
+For example fix basic errors : 
 
-`@all-contributors-bot please add @brunoscheufler for content`
+```bash
+npm run lint --fix
+```
 
-Contribution types are listed [here](https://allcontributors.org/docs/en/emoji-key).
+## Contribution model
+
+### Steering committee 🏆
+
+Members of the steering committee work together to provide guidance and future direction to the project. Each committee member has a particular expertise which they share their knowledge on, and work to lead further improvements to the project in that area. The steering committee members are responsible for approving new best practices, and ensuring current best practices remain relevant.
+
+### Collaborators 👍
+
+Collaborators are members who are contributing to the repository on a regular basis, through suggesting new best practices, triaging issues, reviewing pull requests and more. Along with the steering committee, each collaborator leads a project tracked under our Github projects.
+
+The role is in place to help the steering committee ensure that the content provided is of high standard, up-to-date with the industry, and available in many languages. Members who frequently participate in these activities will be invited to become a collaborator, based on the quality of their contributions.
+
+The steering committee periodically reviews the collaborator list to identify inactive collaborators. Inactive collaborators can choose to either continue in or step down from their role, in which case they are acknowledged as a past collaborator. They may later request that the steering committee restore them to active status.

.operations/.common-answers.md → .operations/common-answers.md

@@ -1,17 +1,17 @@
 **Welcoming new translators**
 
-@name - Welcome aboard, it's great to have you here 🎆
+@name - Welcome aboard, it's great to have you here! 🎆
 
-Having A Slovak translation could be awesome! At the end, we can Tweet about this, put in our news section, include your name at the top of the translated language and also at the main home page contributors list
+Having A Slovak translation could be awesome! At the end, we can Tweet about this, put in our news section, include your name at the top of the translated language and also at the main home page contributors list.
 
 Let's go for this? Few basic guideliness:
 
-- Work on your own fork - Fork this repo, create a branch for yourself, translate & collaborate with other translators, then finally when ready create a PR
+- Work on your own fork - Fork this repo, create a branch for yourself, translate & collaborate with other translators, then finally when ready create a PR.
 
-- Focus on translation, not content editing - The focus is on translation, should you want to modify the content or the graphics - let's PR first in English and then translate to other languages. Also the format of the text should remain intact (same design)
+- Focus on translation, not content editing - The focus is on translation, should you want to modify the content or the graphics - let's PR first in English and then translate to other languages. Also the format of the text should remain intact (same design).
 
-- Duplicate the readme and the inner pages - Tthe content should be translated over a page duplication. Readme.MD became Readme.{translated-language}.MD (e.g. readme.french.md), all other files should be duplicated similarly. So the number of English & translated pages should be the same. You may see examples in currently translated languages
+- Duplicate the readme and the inner pages - The content should be translated over a page duplication. readme.md became readme.{translated-language}.md (e.g. readme.french.md), all other files should be duplicated similarly. So the number of English & translated pages should be the same. You may see examples in currently translated languages.
 
-Collaborate - once you do the basic setup (branch, duplicate pages), we can announce the work on a new language and get others involved and help you in translation (if you wish)
+Collaborate - once you do the basic setup (branch, duplicate pages), we can announce the work on a new language and get others involved and help you in translation (if you wish).
 
-We're here to help - let us know whether we can do anything to support you. We can Tweet about this work, put homepage banner or anything else
+We're here to help - let us know whether we can do anything to support you. We can Tweet about this work, put homepage banner or anything else.