Ayman profilee 3

.cspell.json

@@ -1,6 +1,16 @@
 {
   "language": "en",
-  "words": ["HackYourFutureBelgium", "HackYourFuture", "Nepo"],
+  "words": [
+    "HackYourFutureBelgium",
+    "HackYourFuture",
+    "Nepo",
+    "Afnan",
+    "Fadi",
+    "Bootcamp",
+    "Ayman",
+    "Laravel",
+    "Alnajjar"
+  ],
   "ignorePaths": [
     "node_modules/**",
     "package.json",

.github/workflows/code-quality-checks.yml

@@ -1,32 +1,23 @@
 name: Code Quality Checks
 
-on: [push, pull_request, workflow_dispatch]
+on:
+  push:
+    branches: [master, main]
+  pull_request:
+    branches: [master, main]
 
 jobs:
-  format_check:
+  lint:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
-      - run: npm install
-      - run: npm run format:check
-
-  spell_check:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - run: npm install
-      - run: npm run spell-check
+      - name: Checkout
+        uses: actions/checkout@v3
 
-  lint_ls:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
       - run: npm install
-      - run: npm run lint:ls
+      - run: npm audit fix
 
-  lint_md:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - run: npm install
-      - run: npm run lint:md
+      - run: npm run format
+      - run: npm run format-check # Change format:check -> format-check
+      - run: npm run spell-check
+      - run: npm run lint-ls # Change lint:ls -> lint-ls
+      - run: npm run lint-md

README.md

@@ -1,22 +1,25 @@
-# (project name)
+# Meet The Team
 
-<!-- describe your project -->
+We are students in the Post Bachelor Coding Bootcamp, seeking to expand our
+knowledge and develop our skills in the software engineering
 
 ## Getting Started
 
 <!-- a guide to using this repository -->
 
-1. `git clone git@github.com:HackYourFutureBelgium/<project-name>.git`
+1. `git clone [markDownProject](https://github.com/Zakey-Pilot/markdown-intros)`
 2. `cd project-name`
 3. `npm install`
 
-## Code Quality Checks
+## Code Quality Scripts
 
 - `npm run format`: Makes sure all the code in this repository is well-formatted
   (looks good).
-- `npm run lint:ls`: Will lint the folder and file names in this repository to
+- `npm run format-check`: Makes sure all the code in this repository is
+  well-formatted (looks good).
+- `npm run lint-ls`: Will lint the folder and file names in this repository to
   make sure they match the repo conventions.
-- `npm run lint:md`: Will lint all of the Markdown files in this repository and
+- `npm run lint-md`: Will lint all of the Markdown files in this repository and
   let you know if there are any style mistakes to fix.
 - `npm run spell-check`: Goes through all the files in this repository looking
   for words it doesn't recognize. Just because it says something is a mistake

package.json

@@ -4,10 +4,10 @@
   "description": "Starter repository for markdown projects at DeNepo",
   "scripts": {
     "format": "prettier --write ./",
-    "format:check": "prettier --check ./",
+    "format-check": "prettier --check ./",
     "spell-check": "cspell \"./**\"",
-    "lint:ls": "ls-lint",
-    "lint:md": "markdownlint --config ./.markdownlint.jsonc --fix ./ "
+    "lint-ls": "ls-lint",
+    "lint-md": "markdownlint --config ./.markdownlint.jsonc --fix ./ "
   },
   "author": "DeNepo",
   "license": "MIT",

people/asmaa.md

@@ -0,0 +1,51 @@
+# Meet The Team
+
+We are students in the Post Bachelor Coding Bootcamp, seeking to expand our
+knowledge and develop our skills in the software engineering
+
+## Getting Started
+
+<!-- a guide to using this repository -->
+
+1. `git clone [markDownProject](https://github.com/Zakey-Pilot/markdown-intros)`
+2. `cd project-name`
+3. `npm install`
+
+## Code Quality Scripts
+
+- `npm run format`: Makes sure all the code in this repository is well-formatted
+  (looks good).
+- `npm run format-check`: Makes sure all the code in this repository is
+  well-formatted (looks good).
+- `npm run lint-ls`: Will lint the folder and file names in this repository to
+  make sure they match the repo conventions.
+- `npm run lint-md`: Will lint all of the Markdown files in this repository and
+  let you know if there are any style mistakes to fix.
+- `npm run spell-check`: Goes through all the files in this repository looking
+  for words it doesn't recognize. Just because it says something is a mistake
+  doesn't mean it is! It doesn't know every word in the world. You can add new
+  correct words to the [./.cspell.json](./.cspell.json) file so they won't cause
+  an error.
+
+## Continuous Integration (CI)
+
+When you open a PR to `main`/`master` in your repository, GitHub will
+automatically do a linting check on the code in this repository, you can see
+this in the[./.github/workflows/lint.yml](./.github/workflows/lint.yml) file.
+
+If the linting fails, you will not be able to merge the PR. You can double check
+that your code will pass before pushing by running `npm run lint:md` locally.
+
+## Repo Setup
+
+- Give each member **_write_** access to the repo (if it's a group project)
+- Turn on GitHub Pages and put a link to your website in the repo's description
+- Go to _General_ Section > check **Discussions**
+- In the _Branches_ section of your repo's settings make sure the
+  `master`/`main` branch must:
+  - "_Require a pull request before merging_"
+  - "_Require approvals_"
+  - "_Dismiss stale pull request approvals when new commits are pushed_"
+  - "_Require status checks to pass before merging_"
+  - "_Require branches to be up to date before merging_"
+  - "_Do not allow bypassing the above settings_"

people/ayman.md

@@ -0,0 +1,23 @@
+# Hi there, I'm Ayman Alnajjar! 👋
+
+---
+
+🌍 About Me I'm a passionate Full-Stack Web Developer from Gaza, Palestine with
+a Computer Science degree. I specialize in building web applications with a
+strong focus on both front-end and back-end development.
+
+---
+
+## 💻 Tech Stack
+
+🔹 Frontend: HTML, CSS, JavaScript, React.
+
+🔹 Backend:PHP(Laravel), Node.js.
+
+🔹 Database: MySQL, PostgreSQL, MongoDB.
+
+🔹 OtherTools: Git,Docker, REST APIs.
+
+🚀 I'm Working On I'm always exploring new technologies and working on exciting
+projects to enhance my skills. My main focus is on web development, API
+integrations, and scalable applications.

people/mohammed.md

@@ -0,0 +1,51 @@
+# Meet The Team
+
+We are students in the Post Bachelor Coding Bootcamp, seeking to expand our
+knowledge and develop our skills in the software engineering
+
+## Getting Started
+
+<!-- a guide to using this repository -->
+
+1. `git clone [markDownProject](https://github.com/Zakey-Pilot/markdown-intros)`
+2. `cd project-name`
+3. `npm install`
+
+## Code Quality Scripts
+
+- `npm run format`: Makes sure all the code in this repository is well-formatted
+  (looks good).
+- `npm run format-check`: Makes sure all the code in this repository is
+  well-formatted (looks good).
+- `npm run lint-ls`: Will lint the folder and file names in this repository to
+  make sure they match the repo conventions.
+- `npm run lint-md`: Will lint all of the Markdown files in this repository and
+  let you know if there are any style mistakes to fix.
+- `npm run spell-check`: Goes through all the files in this repository looking
+  for words it doesn't recognize. Just because it says something is a mistake
+  doesn't mean it is! It doesn't know every word in the world. You can add new
+  correct words to the [./.cspell.json](./.cspell.json) file so they won't cause
+  an error.
+
+## Continuous Integration (CI)
+
+When you open a PR to `main`/`master` in your repository, GitHub will
+automatically do a linting check on the code in this repository, you can see
+this in the[./.github/workflows/lint.yml](./.github/workflows/lint.yml) file.
+
+If the linting fails, you will not be able to merge the PR. You can double check
+that your code will pass before pushing by running `npm run lint:md` locally.
+
+## Repo Setup
+
+- Give each member **_write_** access to the repo (if it's a group project)
+- Turn on GitHub Pages and put a link to your website in the repo's description
+- Go to _General_ Section > check **Discussions**
+- In the _Branches_ section of your repo's settings make sure the
+  `master`/`main` branch must:
+  - "_Require a pull request before merging_"
+  - "_Require approvals_"
+  - "_Dismiss stale pull request approvals when new commits are pushed_"
+  - "_Require status checks to pass before merging_"
+  - "_Require branches to be up to date before merging_"
+  - "_Do not allow bypassing the above settings_"

people/rahaf.md

@@ -0,0 +1,51 @@
+# Meet The Team
+
+We are students in the Post Bachelor Coding Bootcamp, seeking to expand our
+knowledge and develop our skills in the software engineering
+
+## Getting Started
+
+<!-- a guide to using this repository -->
+
+1. `git clone [markDownProject](https://github.com/Zakey-Pilot/markdown-intros)`
+2. `cd project-name`
+3. `npm install`
+
+## Code Quality Scripts
+
+- `npm run format`: Makes sure all the code in this repository is well-formatted
+  (looks good).
+- `npm run format-check`: Makes sure all the code in this repository is
+  well-formatted (looks good).
+- `npm run lint-ls`: Will lint the folder and file names in this repository to
+  make sure they match the repo conventions.
+- `npm run lint-md`: Will lint all of the Markdown files in this repository and
+  let you know if there are any style mistakes to fix.
+- `npm run spell-check`: Goes through all the files in this repository looking
+  for words it doesn't recognize. Just because it says something is a mistake
+  doesn't mean it is! It doesn't know every word in the world. You can add new
+  correct words to the [./.cspell.json](./.cspell.json) file so they won't cause
+  an error.
+
+## Continuous Integration (CI)
+
+When you open a PR to `main`/`master` in your repository, GitHub will
+automatically do a linting check on the code in this repository, you can see
+this in the[./.github/workflows/lint.yml](./.github/workflows/lint.yml) file.
+
+If the linting fails, you will not be able to merge the PR. You can double check
+that your code will pass before pushing by running `npm run lint:md` locally.
+
+## Repo Setup
+
+- Give each member **_write_** access to the repo (if it's a group project)
+- Turn on GitHub Pages and put a link to your website in the repo's description
+- Go to _General_ Section > check **Discussions**
+- In the _Branches_ section of your repo's settings make sure the
+  `master`/`main` branch must:
+  - "_Require a pull request before merging_"
+  - "_Require approvals_"
+  - "_Dismiss stale pull request approvals when new commits are pushed_"
+  - "_Require status checks to pass before merging_"
+  - "_Require branches to be up to date before merging_"
+  - "_Do not allow bypassing the above settings_"

planning/backlog.md

@@ -0,0 +1,45 @@
+# Backlog
+
+## Must-Haves
+
+are necessary for basic usability:
+
+- **user story name**: As a recruiter I want to view the team description so
+  that i have a general knowledge about team
+  - Given I'm in opened browser when I click on the repository link then the
+    description shows up
+  - ...
+- **user story name**: As a recruiter I want to view the profiles for each
+  member so that I can view their information
+  - Given I'm in description screen when I clicks on the profile link then
+    navigate to profile screen
+  - ...
+- ...
+
+## Should-Haves
+
+will complete the user experience, but are not necessary:
+
+- **user story name**: As a recruiter I want to see the previous work of the
+  team so that i can discover team experience
+  - Given I'm in description screen when I clicks on the previous work link then
+    navigate to previous work screen
+  - ...
+
+## Could-Haves
+
+would be really cool ... if there's time:
+
+- **user story name**: As a [type of user] I want to [do something] so that [I
+  achieve some goal]
+  - Given [context] when [a specific action is performed] then [a set of
+    consequences should occur]
+  - ...
+- **user story name**: As a [type of user] I want to [do something] so that [I
+  achieve some goal]
+  - Given [context] when [a specific action is performed] then [a set of
+    consequences should occur]
+  - ...
+- ...
+
+---

planning/communication.md

@@ -0,0 +1,52 @@
+# Communication
+
+## Group Rules
+
+- be polite
+- be on time
+
+---
+
+## Communication Schedule
+
+| Day    |   How   | The topic of discussion  |
+| ------ | :-----: | :----------------------: |
+| Monday | 16 - 18 | review the finished task |
+
+## Communication Channels
+
+how often will we get in touch on each channel, and what we will discuss there:
+
+- **Issues**:
+- **Pull Requests**:
+- **GitHub Discussions**
+- **Slack/Discord**:
+- **Video Calls**:
+
+---
+
+## Availability
+
+### Availability for calling/messaging
+
+| Day    | Monday  | Tuesday | Wednesday | Thursday | Friday  | Saturday | Sunday  |
+| ------ | :-----: | :-----: | :-------: | :------: | :-----: | :------: | :-----: |
+| _name_ | 13 - 20 | 13 - 20 |  13 - 20  | 13 - 20  | 13 - 20 | 13 - 20  | 13 - 20 |
+
+### How many hours everyone has per day
+
+- name: _5h_; extra comments?
+- name: _6h_;
+- name: _5h_;
+- name: _4h_;
+- name: _3h_;
+
+## Asking for Help
+
+There's a fine line between confidently learning from your mistakes, and
+stubbornly getting no where. Here is a general guide for when to ask for help
+based on how long you've been stuck on the same problem:
+
+1. _0 -> 30 min_: Try on your own
+2. _30 -> 60 min_: Ask your group for help
+3. _60+ min_: Tag your coaches in Slack or GitHub