codeuino / codeuino/codebadge-backend
Create an Admin Dashboard
- 主要言語
- Vue
- スター
- 15
- フォーク
- 23
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### **What you will need to know?**
Javascript - Intermediate/Advance level (How to use requests and response using AJAX/Fetch asynchronously)
### **Create an Admin Dashboard**
Admin Dashboard inside CodeBadge platform will be a place where all the management work takes place by Organization Admins. This shall be a new tab which would be visible only to the organization admin(s) (which can be identified while fetching the user roles for user contribution tracking from [official GitHub API](https://developer.github.com/v3/)). This should give admin the access to various major features such as creating/editing/deleting badges which are to be awarded to the top contributors. Along with this, admin should have access to complete organization analytics such as monthly contribution rate, last active date of users, all-time contributions, etc. Same provided API would help you in providing all this kind of analytical data. You can use [ChartsJS](https://www.chartjs.org/) library for representation of these analytics.
### **Requirements**
* HTML, CSS, Javascript - Intermediate/Advance level
### **Steps to Follow**
* Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
* Install CodeBadge on your system go through [readme.md]() in development branch for this purpose
* After installing CodeBadge install dependencies of backend and frontend, go through [readme.md]() inside both the folders
Link to readme https://github.com/codeuino/Codebadge/blob/master/README.md
* To run the project follow the given step in [readme.md]() for both frontend and backend.
* Checkout to a different feature branch in git and start with the coding part.
* Make sure to commit your work daily and create a single PR for all your commits, per feature.
### **Acceptance Criteria**
* Code is short, clean and properly indented.
* Unused code/comments/variables should not be lying in the code unnecessarily exploiting memory.
* Minimal number of re-iterations in order to improve efficiency and keep the commit history clean.
* Best practices should be used in case of multiple approaches, mentors are always there to help you for this 👍
### **Rejection Criteria**
* Not following/Violating [Code of Conduct](https://github.com/codeuino/Codebadge/blob/master/CODE_OF_CONDUCT.md) can lead to rejection.
* Coding etiquettes must be taken care of, for eg, always committing code in a different feature branch, same PR is edited in case of re-iteration of code, etc.
### **Expected Outcome**
An Admin Dashboard tab inside CodeBadge platform which won't be visible to general members/contributors of the community but only to org admin(s), showing various kind of analytics as to how the organization is performing/growing as well as features to create/edit 'CodeBadges'.
### **How to excel fast in the community**
- Share the issues you encounter along the way and help others solve theirs.
- Chime in below in a comment to cooperate with others who are also working on this task.
- Report back at the above issue once you succeed, to encourage others and share what worked for you!
### **Resources & References (Where to Start)**
You'll need to go through the docs of [official GitHub API](https://developer.github.com/v3/) for fetching various analytics and [ChartsJS](https://www.chartjs.org/) library for pictorial representation of the same data.
### **Extras**
Just follow the readme whenever you are stuck . Visit [Codeuino's Website](https://codeuino.slack.com/) in case of any doubts.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
まずリポジトリの README と frontend および backend フォルダー内の README ファイルを読み、プロジェクトの実行方法を理解します。次に、issue で参照されている公式の GitHub API ドキュメントと Chart.js ドキュメントを確認します。完了の条件は、管理者専用のダッシュボードタブがバッジ管理をサポートし、組織のコントリビューション分析を表示することです。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- chart.js, github, javascript
- 領域
- analytics, authorization, backend, frontend
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100