Change Details

This task is one of two application microtasks for T317083 **Overview** For this task, you're required to set up the infrastructure for the Frontend Web Application.  **Tools you could use are as follows:** 1. Any frontend framework or library of your choice 2. Any testing frameworks/libraries of your choice 3. Git 4. Any repository hosting service of your choice This task would give a sense of your Frontend skills. Don't worry, the project in itself would entail more coding and UI styling. Don't be under pressure to impress, feel free to reach out to any mentor for additional support if anything seems unclear or you get stuck on any part of the task. Also feel free to use any other tool that you consider beneficial to your project. **Steps to follow** - Create a Frontend project with support for Unit Testing. - Initialise Git on the project, if you haven't done so already, and add the remote url of your repository. - Add the boilerplate code into a commit. The [[ https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines | commit message guidelines ]] used by developers in the foundation might be useful when creating your commits. - Push up the change to the repository hosting service of your choice. - Design 3 Mock pages: Home, Leaderboard, and a Records Dashboard. You are required to build this pages with hardcoded strings, that means none of this pages should make request to the API for data. Feel free to be creative with your designs, and you can also seek some inspiration from the [[ https://citationhunt.toolforge.org/ | Citation Hunt ]] tool. - Each page should have a [[ https://en.wikipedia.org/wiki/Navigation_bar | Navigation bar ]] containing links to the other pages. - The Dashboard is required to show the following metrics with mock figures (feel free to add other analytics you think may be useful to monitor): Total number of Tools in the records, number of tools with missing information, percentage of tools with missing information compared with the total number of tools in the records, number of tools edited using this record management tool - Add these UI to a commit and push up the changes. - Ensure your code is well documented in the README.md file. - If you feel you have completed all the steps in this task, you may request feedback, and we will provide high-level feedback on what is good and what is missing. To do so, email both of the mentors (sstefanova@wikimedia.org and dadedoyin@wikimedia.org) with the link to your public PAWS notebook. We will try to make time to provide this feedback once to anyone who would like it. - When you feel you are happy with the state of your repository, you should include the public link in your final Outreachy project application as a recorded contribution. We encourage you to record contributions as you go, as well to track progress. All the best!

This task is one of two application microtasks for T317083 **Overview** For this task, you're required to set up the infrastructure for the Frontend Web Application.  **Tools you could use are as follows:** 1. Any frontend framework or library of your choice 2. Any testing frameworks/libraries of your choice 3. Git 4. Any repository hosting service of your choice This task would give a sense of your Frontend skills. Don't worry, the project in itself would entail more coding and UI styling. Don't be under pressure to impress, feel free to reach out to any mentor for additional support if anything seems unclear or you get stuck on any part of the task. Also feel free to use any other tool that you consider beneficial to your project. **Steps to follow** - Create a Frontend project with support for Unit Testing. - Initialise Git on the project, if you haven't done so already, and add the remote url of your repository. - Add the boilerplate code into a commit. The [[ https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines | commit message guidelines ]] used by developers in the foundation might be useful when creating your commits. - Push up the change to the repository hosting service of your choice. - Design 3 Mock pages: Home, Leaderboard, and a Records Dashboard. You are required to build this pages with hardcoded strings, that means none of this pages should make request to the API for data. Feel free to be creative with your designs, and you can also seek some inspiration from the [[ https://citationhunt.toolforge.org/ | Citation Hunt ]] tool. - Each page should have a [[ https://en.wikipedia.org/wiki/Navigation_bar | Navigation bar ]] containing links to the other pages. - The Dashboard is required to show the following metrics with mock figures (feel free to add other analytics you think may be useful to monitor): Total number of Tools in the records, number of tools with missing information, percentage of tools with missing information compared with the total number of tools in the records, number of tools edited using this record management tool - Add these UI to a commit and push up the changes. - Ensure your code is well documented in the README.md file. - If you feel you have completed all the steps in this task, you may request feedback, and we will provide high-level feedback on what is good and what is missing. To do so, email both of the mentors (`sstefanova@wikimedia.org` and `dadedoyin@wikimedia.org`) with the link to your public PAWS notebook. We will try to make time to provide this feedback once to anyone who would like it. - When you feel you are happy with the state of your repository, you should include the public link in your final Outreachy project application as a recorded contribution. We encourage you to record contributions as you go, as well to track progress. All the best!

This task is one of two application microtasks for T317083 **Overview** For this task, you're required to set up the infrastructure for the Frontend Web Application.  **Tools you could use are as follows:** 1. Any frontend framework or library of your choice 2. Any testing frameworks/libraries of your choice 3. Git 4. Any repository hosting service of your choice This task would give a sense of your Frontend skills. Don't worry, the project in itself would entail more coding and UI styling. Don't be under pressure to impress, feel free to reach out to any mentor for additional support if anything seems unclear or you get stuck on any part of the task. Also feel free to use any other tool that you consider beneficial to your project. **Steps to follow** - Create a Frontend project with support for Unit Testing. - Initialise Git on the project, if you haven't done so already, and add the remote url of your repository. - Add the boilerplate code into a commit. The [[ https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines | commit message guidelines ]] used by developers in the foundation might be useful when creating your commits. - Push up the change to the repository hosting service of your choice. - Design 3 Mock pages: Home, Leaderboard, and a Records Dashboard. You are required to build this pages with hardcoded strings, that means none of this pages should make request to the API for data. Feel free to be creative with your designs, and you can also seek some inspiration from the [[ https://citationhunt.toolforge.org/ | Citation Hunt ]] tool. - Each page should have a [[ https://en.wikipedia.org/wiki/Navigation_bar | Navigation bar ]] containing links to the other pages. - The Dashboard is required to show the following metrics with mock figures (feel free to add other analytics you think may be useful to monitor): Total number of Tools in the records, number of tools with missing information, percentage of tools with missing information compared with the total number of tools in the records, number of tools edited using this record management tool - Add these UI to a commit and push up the changes. - Ensure your code is well documented in the README.md file. - If you feel you have completed all the steps in this task, you may request feedback, and we will provide high-level feedback on what is good and what is missing. To do so, email both of the mentors (`sstefanova@wikimedia.org` and `dadedoyin@wikimedia.org`) with the link to your public PAWS notebook. We will try to make time to provide this feedback once to anyone who would like it. - When you feel you are happy with the state of your repository, you should include the public link in your final Outreachy project application as a recorded contribution. We encourage you to record contributions as you go, as well to track progress. All the best!