Currently, the design of the campaigns view is very similar to the courses view for an individual course, but for courses, all the tabs (Home, Articles, etc) are rendered client-side in React, due to which we're not able to add features.
Moving to single-architecture would improve user experience as they can easily navigate from tab to tab, preserving data between tabs after initial render, so that the page feels faster.
Campaign pages will be nicer, and the architecture more consistent, if we use React pretty much everywhere and get progressively closer to a single-page app. Moreover, it will enable the filtering of the courses/campaigns, sorting courses into related campaigns or allow actions on multiple courses of a campaign at once to improve the user experience or the Dashboard.
This involves converting:
- Campaign overview
- Campaign course tab
- Campaign articles tab
- Campaign user tab
and eventually all campaign tabs from haml to react
For Wiki Education Dashboard Outreachy proposals this round, because of the large number of people interested who are already active in contributing to the project, we're asking applicants to come up with their own project ideas. If you're just getting started and are interested in applying for a Wiki Education Dashboard project, the best way to begin is to:
- email firstname.lastname@example.org to request an invite to our Slack channel
- set up the Dashboard development environment, and report any problems you run into in the process: https://github.com/WikiEducationFoundation/WikiEduDashboard/blob/master/docs/setup.md
- browse the issues and find one to take on, especially one tagged 'help wanted' or 'newcomer-friendly': https://github.com/WikiEducationFoundation/WikiEduDashboard/issues
Wiki Education Dashboard is built primarily with Ruby on Rails and React.