Implement reusable tree components and reuse the tree on the product tree, shareable tree and summary tree.

Skill and expertise implementation in a tree way and Expertise should be shown based on skill selected.

Please have a look at the "interactive product tree" UX that is now implemented in this UX Prototype codebase: https://github.com/OpenUnited/ux-prototype Your task is to implement that in the Platform codebase so that we can get this new interactive way of managing Product Trees live: https://github.com/OpenUnited/platform You will use the same CSS / JS (e.g. Tailwind CSS) as the UX Prototype implementation, and you will also follow the conventions in the Platform codebase including use of HTMX and preference for hyperscript, simple javascript where required etc.

**Objective:** - To ensure code quality, consistency, and adherence to best practices by integrating a pre-commit hook that automates the execution of essential tools during the commit process. **Tools to be Integrated:** - Black: For code formatting and styling - Isort: For maintaining consistent import order - Flake8: For static code analysis and linting - Django Migrations Check: To detect and prevent missing Django database migrations **Task Requirements:** - **Install Required Tools**: Ensure that Black, Isort, Flake8, and Django are installed and available in the project's development environment. - **Configure Pre-Commit Hook**: Set up a pre-commit hook using a tool like pre-commit or husky to trigger the execution of the specified tools during the commit process. - **Integrate Tools with Pre-Commit Hook**: Configure the pre-commit hook to run the following tools in sequence: - Black: To format code according to the project's coding standards. - Isort: To organize imports in a consistent manner. - Flake8: To perform static code analysis and linting. - Django Migrations Check: To verify that all necessary Django database migrations are present and up-to-date. **Test Pre-Commit Hook:** - Verify that the pre-commit hook is functioning correctly by attempting to commit code with intentional formatting issues, import inconsistencies, linting errors, or missing migrations. **Document Pre-Commit Hook Configuration**: Maintain clear documentation on the pre-commit hook configuration, including the tools used, their versions, and any custom settings or configurations.

Simplify test setup including adding convert the tests to pytest and add python test fixtures for all models.

Simplify test setup including data factory and use ChatGPT to help speed this up if applicable. Add test coverage tools to show the coverage report with HTML and console.

change "type" on BountyDeliveryAttempt to be a "status" implemented in a way that is consistent with other status fields

Revise the Attachments (single model for attachments) data model and ensure all UX flows related to attachments are working well. Create one attachment model and remove all attachments, relating as many as needed to whichever model requires attachments. Create a reusable template and mixin which should be used as a plugin.

Refine the statuses (Challenge etc) and ensure that we have these changes covered in tests, please also check that things in "Draft" status are not publicly displayed etc. (we have this issue on a production where bounties belonging to "Draft" status challenges display)

The task of optimizing search functionality for both mobile and desktop users has been successfully completed. This involved adding a tailored search feature for mobile devices and refactoring the existing desktop search to enhance performance and user experience. With these enhancements, users across all platforms can now enjoy a seamless and efficient search experience.

In this update, I have successfully resolved issues on the profile update page, specifically addressing the dynamic forms for updating skills and expertise. Additionally, I have made significant improvements to the portfolio page for better functionality and user experience.

Fix the issues in bounty claim, delivery and review.

Update the product slugs in the fixture data to reflect newly added products instead of the old ones.

Fix the general UI/UX and logic issues in product, challenge and bounty creation

Implement a initiative details view showing the detailed info of the initiative. It should also show a list of available challenges of the initiative. Implement a card-based view for the challenges. The cards should also show the status and available bounties of each challenge.

Replace existing bounty data with meaningful and product related data in the fixtures.