From 201af4a23e071fe5a1790fd4b7a8067574b35276 Mon Sep 17 00:00:00 2001 From: AymanAlnajjar Date: Sun, 9 Feb 2025 23:47:01 +0200 Subject: [PATCH 1/7] late night meeting commit --- .cspell.json | 2 +- README.md | 15 ++++++----- package.json | 6 ++--- planning/backlog.md | 45 +++++++++++++++++++++++++++++++++ planning/communication.md | 52 +++++++++++++++++++++++++++++++++++++++ planning/constrains.md | 33 +++++++++++++++++++++++++ planning/user-persona.md | 31 +++++++++++++++++++++++ 7 files changed, 174 insertions(+), 10 deletions(-) create mode 100644 planning/backlog.md create mode 100644 planning/communication.md create mode 100644 planning/constrains.md create mode 100644 planning/user-persona.md diff --git a/.cspell.json b/.cspell.json index 029995d..e9f7a2f 100644 --- a/.cspell.json +++ b/.cspell.json @@ -1,6 +1,6 @@ { "language": "en", - "words": ["HackYourFutureBelgium", "HackYourFuture", "Nepo"], + "words": ["HackYourFutureBelgium", "HackYourFuture", "Nepo", "Afnan", "Fadi"], "ignorePaths": [ "node_modules/**", "package.json", diff --git a/README.md b/README.md index 9bdbbee..83358f3 100644 --- a/README.md +++ b/README.md @@ -1,22 +1,25 @@ -# (project name) +# 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 -1. `git clone git@github.com:HackYourFutureBelgium/.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 diff --git a/package.json b/package.json index d0e9c48..049ccdd 100644 --- a/package.json +++ b/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", diff --git a/planning/backlog.md b/planning/backlog.md new file mode 100644 index 0000000..681c657 --- /dev/null +++ b/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] + - ... +- ... + +--- diff --git a/planning/communication.md b/planning/communication.md new file mode 100644 index 0000000..4508e10 --- /dev/null +++ b/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 diff --git a/planning/constrains.md b/planning/constrains.md new file mode 100644 index 0000000..5ac80a1 --- /dev/null +++ b/planning/constrains.md @@ -0,0 +1,33 @@ +# Constraints + +Some boundaries around our project. + +## External + +- The deadline +- The template repository restrictions + +## Internal: Involuntary + +- Some of our members have electricity and internet issues +- We can't meet IRL +- Difficulty in arranging an appointment with each other at the same time + + + +## Internal: Voluntary + +- The number of hours you want to spend working +- Making the project in English Language + + diff --git a/planning/user-persona.md b/planning/user-persona.md new file mode 100644 index 0000000..56c6a52 --- /dev/null +++ b/planning/user-persona.md @@ -0,0 +1,31 @@ +# User Personas + +- Technical Recruiter +- Non-Technical Recruiter + +--- + +## Their Role + +- **Bio**:Afnan is a technical project manager from Jordan +- **Needs/Goals**: She wants to recruit a full-time team to build a new web + banking application. +- **Frustrations**:Finding a cohesive and skilled team that can efficiently + complete the project on time. +- **Scenario 1**:Afnan is a project manager at a software house and has been + assigned to hire a development team experienced in Next.js and TypeScript. She + searches online and discovers our team’s repository on GitHub. After reviewing + our skills and past projects, she finds that we meet the project requirements + and decides to reach out. + +--- + +- **Bio**: Fadi is the CEO of an accounting firm from Palestine. +- **Needs/Goals**: He needs a team to lead a digital transformation initiative + to optimize and modernize his company’s accounting processes. +- **Frustrations**:Hiring an experienced development team that understands + business needs and can implement an efficient digital solution. +- **Scenario 2**:Fadi is looking to digitalize his accounting firm to improve + workflow and efficiency. A trusted colleague recommends our team. He explores + our repository, reviews our previous work, and finds that we have the + expertise to successfully handle his project. From f991861611af741617bbbda73e9aa1afe50cda21 Mon Sep 17 00:00:00 2001 From: AymanAlnajjar Date: Mon, 10 Feb 2025 00:00:52 +0200 Subject: [PATCH 2/7] late night meeting updates --- people/asmaa.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++ people/ayman.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++ people/mohammed.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++ people/rahaf.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 204 insertions(+) create mode 100644 people/asmaa.md create mode 100644 people/ayman.md create mode 100644 people/mohammed.md create mode 100644 people/rahaf.md diff --git a/people/asmaa.md b/people/asmaa.md new file mode 100644 index 0000000..83358f3 --- /dev/null +++ b/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 + + + +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_" diff --git a/people/ayman.md b/people/ayman.md new file mode 100644 index 0000000..83358f3 --- /dev/null +++ b/people/ayman.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 + + + +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_" diff --git a/people/mohammed.md b/people/mohammed.md new file mode 100644 index 0000000..83358f3 --- /dev/null +++ b/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 + + + +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_" diff --git a/people/rahaf.md b/people/rahaf.md new file mode 100644 index 0000000..83358f3 --- /dev/null +++ b/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 + + + +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_" From 4bebfc38e56eda8e56d18b04b3daab5e2512c051 Mon Sep 17 00:00:00 2001 From: Mohammed Naser Abu Shuqair Date: Mon, 10 Feb 2025 09:35:14 +0200 Subject: [PATCH 3/7] add mohammed profile --- people/mohammed.md | 77 ++++++++++++++++------------------------------ 1 file changed, 26 insertions(+), 51 deletions(-) diff --git a/people/mohammed.md b/people/mohammed.md index 83358f3..8298725 100644 --- a/people/mohammed.md +++ b/people/mohammed.md @@ -1,51 +1,26 @@ -# 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 - - - -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_" +# Hi πŸ‘‹, I'm Mohammed Abu Shuqair + +A Humble Mobile developer from Palestinian + +## Professional Summary + +Skilled Flutter Developer with over 2 years of experience in designing, +developing, and deploying mobile applications for both iOS and Android +platforms. Strong foundation in software engineering principles, object-oriented +programming, and design patterns. Proven track record of delivering +high-quality, efficient, and scalable mobile solutions with a focus on enhancing +user experience. Proficient in state management, RESTful APIs, and agile +development methodologies. Seeking to contribute my expertise to a +forward-thinking tech company focused on building innovative mobile +applications. + +- 🌱 I’m currently learning **Markdown** + +- πŸ’¬ Ask me about **Flutter,Dart,OOP,SOLD** + +- πŸ“« How to reach me **** + +- πŸ“„ Know about my experiences + [cv on google docs](https://docs.google.com/document/d/1b3wU07atbRME8LfNhLyRsinMGkfSYMgzNsdYXSXi-p8/edit?tab=t.0) + +- ⚑ Fun fact **I am a Real Madrid fan** From a1bb284eafe48bffee1e290e92bec7247c0fb409 Mon Sep 17 00:00:00 2001 From: Mohammed Naser Abu Shuqair Date: Mon, 10 Feb 2025 09:55:07 +0200 Subject: [PATCH 4/7] fix linting and spell checking --- .cspell.json | 10 +++++++++- planning/constrains.md | 3 ++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/.cspell.json b/.cspell.json index e9f7a2f..d64b563 100644 --- a/.cspell.json +++ b/.cspell.json @@ -1,6 +1,14 @@ { "language": "en", - "words": ["HackYourFutureBelgium", "HackYourFuture", "Nepo", "Afnan", "Fadi"], + "words": [ + "HackYourFutureBelgium", + "HackYourFuture", + "Nepo", + "Afnan", + "Fadi", + "Bootcamp", + "Shuqair" + ], "ignorePaths": [ "node_modules/**", "package.json", diff --git a/planning/constrains.md b/planning/constrains.md index 5ac80a1..3f83fbd 100644 --- a/planning/constrains.md +++ b/planning/constrains.md @@ -14,7 +14,8 @@ Some boundaries around our project. - Difficulty in arranging an appointment with each other at the same time From 94e355f7de0ebed33eeb4f034a5ab8e9235a618c Mon Sep 17 00:00:00 2001 From: Mohammed Naser Abu Shuqair Date: Mon, 10 Feb 2025 09:59:09 +0200 Subject: [PATCH 5/7] fix formatting --- planning/constrains.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/planning/constrains.md b/planning/constrains.md index 3f83fbd..b541d73 100644 --- a/planning/constrains.md +++ b/planning/constrains.md @@ -14,7 +14,7 @@ Some boundaries around our project. - Difficulty in arranging an appointment with each other at the same time - -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_" +# 🌟 Asmaa Alnajjar – Engineer, Developer & Creative Mind + +I am a Computer and Telecommunications Engineer with a passion for web development, UI/UX design, and technology-driven solutions. My expertise lies in creating efficient, user-friendly, and visually appealing websites using modern frameworks and best practices. + +## πŸ› οΈ Technical Skills + +πŸ’» **Web Development:** HTML, CSS, JavaScript, React.js, Next.js, Node.js + +🎨 **UI/UX & Design:** Figma + +πŸ—„οΈ **Databases:** SQL & NoSQL + +## 🀝 Soft Skills + +🎯 **Attention to Detail:** Committed to delivering high-quality work with precision and accuracy. + +πŸ“’ **Communication & Teaching:** Breaking down complex topics for easier understanding. + +🌟 **Empathy & Team Collaboration:** Committed to building strong professional relationships and supporting team success. + +## Previous Work + +**[CryptoZakat](https://www.cryptozakat.io):** Designed and developed a responsive website using Next.js, Figma, and integrated it with RESTful APIs to ensure seamless data flow and functionality. diff --git a/planning/constrains.md b/planning/constrains.md index b541d73..5ac80a1 100644 --- a/planning/constrains.md +++ b/planning/constrains.md @@ -14,8 +14,7 @@ Some boundaries around our project. - Difficulty in arranging an appointment with each other at the same time From 0d7fe36995d9d5e93b9da215b6b63fceeb50c878 Mon Sep 17 00:00:00 2001 From: asmaaamin Date: Mon, 10 Feb 2025 14:56:56 +0200 Subject: [PATCH 7/7] run check scripts --- .cspell.json | 5 ++++- .github/workflows/code-quality-checks.yml | 6 +++--- people/asmaa.md | 18 +++++++++++++----- 3 files changed, 20 insertions(+), 9 deletions(-) diff --git a/.cspell.json b/.cspell.json index c9c72bd..737a693 100644 --- a/.cspell.json +++ b/.cspell.json @@ -7,7 +7,10 @@ "Afnan", "Fadi", "Asmaa", - "Alnajjar" + "Alnajjar", + "Zakat", + "Bootcamp", + "Shuqair" ], "ignorePaths": [ "node_modules/**", diff --git a/.github/workflows/code-quality-checks.yml b/.github/workflows/code-quality-checks.yml index c106825..e39b2f8 100644 --- a/.github/workflows/code-quality-checks.yml +++ b/.github/workflows/code-quality-checks.yml @@ -17,7 +17,7 @@ jobs: - run: npm audit fix - run: npm run format - - run: npm run format-check # Change format:check -> format-check + - 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 + - run: npm run lint-ls # Change lint:ls -> lint-ls + - run: npm run lint-md diff --git a/people/asmaa.md b/people/asmaa.md index aede8e2..716fdb9 100644 --- a/people/asmaa.md +++ b/people/asmaa.md @@ -1,6 +1,9 @@ # 🌟 Asmaa Alnajjar – Engineer, Developer & Creative Mind -I am a Computer and Telecommunications Engineer with a passion for web development, UI/UX design, and technology-driven solutions. My expertise lies in creating efficient, user-friendly, and visually appealing websites using modern frameworks and best practices. +I am a Computer and Telecommunications Engineer with a passion for web +development, UI/UX design, and technology-driven solutions. My expertise lies in +creating efficient, user-friendly, and visually appealing websites using modern +frameworks and best practices. ## πŸ› οΈ Technical Skills @@ -12,12 +15,17 @@ I am a Computer and Telecommunications Engineer with a passion for web developme ## 🀝 Soft Skills -🎯 **Attention to Detail:** Committed to delivering high-quality work with precision and accuracy. +🎯 **Attention to Detail:** Committed to delivering high-quality work with +precision and accuracy. -πŸ“’ **Communication & Teaching:** Breaking down complex topics for easier understanding. +πŸ“’ **Communication & Teaching:** Breaking down complex topics for easier +understanding. -🌟 **Empathy & Team Collaboration:** Committed to building strong professional relationships and supporting team success. +🌟 **Empathy & Team Collaboration:** Committed to building strong professional +relationships and supporting team success. ## Previous Work -**[CryptoZakat](https://www.cryptozakat.io):** Designed and developed a responsive website using Next.js, Figma, and integrated it with RESTful APIs to ensure seamless data flow and functionality. +**[CryptoZakat](https://www.cryptozakat.io):** Designed and developed a +responsive website using Next.js, Figma, and integrated it with RESTful APIs to +ensure seamless data flow and functionality.