Add pagination to challenge all API and also handles on frontend to handle pagination.

• Add basic view to create challenge #11
• Add view to update challenge
• Add placeholders on inputs to provide info.
• Simplify challenge creation and update UI/UX.
• Limit permission to create and update challenge.
• #29

Show expired on due date component if challenge due date is passed as currently it shows -<no of days> instead of expired. This should be done on both challenge detail and challenge card component.

• Calculate challenge progress
• Add challenge instructions

Add arrow like in the image to switch content between 2 fields, that will ease the current hassle of copying the existing "name" content which is in english to below "name:en"

• Show appropriate error messages on backend.
• Show appropriate error popups on frontend.
• Add not found page

Campaigns are important to create and manage multiple challenges.
It will consist of following features:

• Allow drawing campaign AOI or upload geojson.
• Just like Tasking Manager projects the campaigns AOI should have ability to be splitted into multiple challenges under one or multiple localization theme.
• Creation of challenge templates.
• Allow campaign favorite function.
• Ability to feature Campaign.

closed by #14

As the project grows, it is crucial to provide comprehensive and well-structured documentation to guide new development contributors when they join the project. This issue aims to develop detailed documentation that will serve as a reference for new team members, enabling them to get up to speed and make meaningful contributions quickly.

Acceptance Criteria

• There is a getting started guide doc that includes step-by-step instructions for setting up the development environment. It should include the below details.
  • Project architecture, explaining the overall structure and how different components interact.
  • An overview of the coding standards and best practices followed within the project.
  • Document the tools and libraries used in the project, along with instructions on integrating them.

Allow creation of private challenge which will be displayed only to challenge creators on challenges list.

closed y #14

Is there is no changes required, clicking done does nothing making confusion so, probably giving user a message "You haven't made any changes, click skip or make changes and click done"

Add a bot that collects user feedback and saves in database.

Display proper error messages if any error occurred while creating challenge. The message should be clearly understandable by user and properly indicate where and why the error occurred. Also disable users clicking create button if the error is not server related.

Add a job on cirlce ci that will be triggered on every pull request.
This job should test frontend build and backend image build for now.
This should also check the code formatting.
Later we need to add tests for both backend and frontend in the job.

Add login with OSM using OSM OAuth2. This also involves creating a user table in database, required endpoints for user login fetching osm access token form osm that will be used in editor to upload changes. Also connect challenge creator and feature actioned by to user maintaining a relationship.

Currently localizer only supports fetching nodes form the overpass query. Add support for ways and relations (if required)