Skip to content

Milestones

List view

  • In this milestone, we aim to enhance the testing and debugging capabilities of our application. This involves two main tasks: 1. **Integrate Playwright with BrowserStack for automated cross-browser testing:** We will set up Playwright to automate browser actions for testing and integrate it with BrowserStack to enable automated cross-browser testing. This integration should be configurable based on the environment (development, production). The existing functionality of the application should not be impacted by this integration. Upon completion, we will update the documentation to include instructions on how to use Playwright with BrowserStack for testing. 2. **Integrate Django Debug Toolbar for in-depth performance insights and debugging:** We will integrate the Django Debug Toolbar to provide insights into the application's performance and issues. This integration should be configurable based on the environment (development, production). The existing functionality of the application should not be impacted by this integration. Upon completion, we will update the documentation to include instructions on how to use Django Debug Toolbar for debugging. By the end of this milestone, our application should have enhanced testing and debugging capabilities, with a smooth workflow for managing and updating tests and debugging issues.

    No due date
    0/2 issues closed
  • In this milestone, we aim to establish and configure localization for our application. This involves four main tasks: 1. **Configure wagtail-localize for localization of Wagtail component fields:** We will set up wagtail-localize to manage the localization of our Wagtail component fields. This will enable us to handle and translate content in various languages directly within Wagtail. 2. **Configure localization flow for static strings within templates:** We will set up a process for localizing static strings within our templates. This task involves adding template strings across the codebase and integrating the 'make messages' command into our Docker setup to generate .po files. 3. **Set up Weblate pipeline for static strings:** We will establish a Weblate pipeline to oversee the translation of static strings. This will allow translators to work on translations directly in Weblate, and the translated strings will be integrated into our codebase through automated pull requests. 4. **Create documentation outlining the localization process:** We will produce comprehensive documentation that outlines the localization process, providing clear instructions and guidelines for future reference. By the end of this milestone, our application should be equipped to support multiple languages, with a streamlined workflow for managing and updating translations.

    No due date
    4/5 issues closed