I'm Tahmina Rasoli! , a junior Web Developer 🚀 from Afghanistan.

Contact:

• 💬 Ask me about anything, I am happy to help;
• 📫 How to reach me: @thmrasoli;
• 📝Resume

If you like what I do, maybe consider buying me a coffee/tea 🥺👉👈

 I came from Afghanistan, a men dominated country where women confront a lot of challenges by going out to work or study. Specially, in the IT domain which is also men dominated field in my country. I have been always curious about working in an environment where is no discrimination and everyone has a voice.

Bachelor degree from Computer Science faculty Kabul university.

I have six years of working experience as a web content officer at Nai Supporting Open Media in Afghanistan, a Cyber and Information local expert at the Ministry of Communication and IT of Afghanistan, and as an IT assistant at UNESCO Kabul. for the time bieng, I study with Hack your Futur Belguim program, which is a web development course for newcomers.

I want to specialize in UX/UI design, and my goal is to pursue my higher education in UX/UI area. I will start my new career as UX/UI designer.

Languages and Tools:

I study HTML, CSS, Javascript, Nodejs, Github, UX/UI design. I have some self-study UI design projects using Figma.

My native language is Dari(persian), I speak Pashto (one of my country's local language), I speak English, also Dutch is a language that I am learning. I speak Urdo (learned from movies 😄)

I am a self-study hard working and dedicated person. I am always looking for new learning opportunities to build my capacity and learn new things.

📈 My GitHub Stats

1. git clone git@github.com:HackYourFutureBelgium/template-markdown.git
2. cd template-markdown
3. npm install

• npm run format: Makes sure all the code in this repository is well-formatted (looks good).
• npm run lint:ls: Checks to make sure all folder and file names match the repository conventions.
• npm run lint:md: Will lint all of the Markdown files in this repository.
• npm run lint:css: Will lint all of the CSS files in this repository.
• npm run validate:html: Validates all HTML files in your project.
• 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 file so they won't cause an error.
• npm run accessibility -- ./path/to/file.html: Runs an accessibility analysis on all HTML files in the given path and writes the report to /accessibility_report

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 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.

• 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
• Turn on GitHub Actions
• in the Branches section of your repo's settings make sure:
  • The repository requires a review before pull requests can be merged.
  • The master/main branch must "Require status checks to pass before merging"
  • The master/main branch must "Require require branches to be up to date before merging"