Change Details

This is the third task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Create views and templates to 1) register and view a //bug// and 2) list all //bugs// registered. **Steps:** # Read the third and fourth parts of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial03/ | Writing your first Django app ]] tutorial. # Create one view to register a bug into the database. ## Create a html template with a simple form to add the bug to database. # Create another view to view the fields of the //bug//. ## Create a html template with a simple list of the fields of the //bug//. # And finally, create a view to list all the bugs in the database. ## Create a html template with a simple list with links to the detail page of each //bug//. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.

IMPORTANT: Make sure to read the [Outreachy participant instructions](https://www.mediawiki.org/wiki/Outreachy/Participants) and [communication guidelines](https://www.mediawiki.org/wiki/New_Developers/Communication_tips) thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up Gerrit, etc. When in doubt, ask your question on [Zulip](https://www.mediawiki.org/wiki/Outreach_programs/Zulip) first! This is the third task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Create views and templates to 1) register and view a //bug// and 2) list all //bugs// registered. **Steps:** # Read the third and fourth parts of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial03/ | Writing your first Django app ]] tutorial. # Create one view to register a bug into the database. ## Create a html template with a simple form to add the bug to database. # Create another view to view the fields of the //bug//. ## Create a html template with a simple list of the fields of the //bug//. # And finally, create a view to list all the bugs in the database. ## Create a html template with a simple list with links to the detail page of each //bug//. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.

IMPORTANT: Make sure to read the [Outreachy participant instructions](https://www.mediawiki.org/wiki/Outreachy/Participants) and [communication guidelines](https://www.mediawiki.org/wiki/New_Developers/Communication_tips) thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up Gerrit, etc. When in doubt, ask your question on [Zulip](https://www.mediawiki.org/wiki/Outreach_programs/Zulip) first! This is the third task for T346641: Assist Capacity Exchange Development, aimed at getting you familiar with the basic structure of the development of the Capacity Exchange platform. **Objective of the task:** Create views and templates to 1) register and view a //bug// and 2) list all //bugs// registered. **Steps:** # Read the third and fourth parts of the [[https://docs.djangoproject.com/en/4.2/intro/tutorial03/ | Writing your first Django app ]] tutorial. # Create one view to register a bug into the database. ## Create a html template with a simple form to add the bug to database. # Create another view to view the fields of the //bug//. ## Create a html template with a simple list of the fields of the //bug//. # And finally, create a view to list all the bugs in the database. ## Create a html template with a simple list with links to the detail page of each //bug//. # Commit your changes to GitHub and send us a link to your project (by email, on our talk page, or replying to this tickect, as you prefer). # **Make sure** to also register it as a contribution on the Outreachy website! We'll send you a reply to say whether it is accepted or not.