Issues for code that functions correctly but is not optimized for long-term development and maintenance. It may be poorly structured, contain redundant or inefficient code, lack proper documentation, or deviate from coding best practices. The Technical Debt milestone aims to address these issues and improve the quality, readability, and maintainability of the codebase.
The milestone emphasizes refactoring and improving the codebase to enhance maintainability, efficiency, and ease of editing.
List view
0 issues of 64 selected
- Status: Open.#5040 In hackforla/website;
- Status: Open.#4922 In hackforla/website;
- Status: Open.#3526 In hackforla/website;
- Status: Open.#3525 In hackforla/website;
- Status: Open.#3523 In hackforla/website;
- Status: Open.#2226 In hackforla/website;
- Status: Open.#1900 In hackforla/website;
- Status: Open.#2601 In hackforla/website;
- Status: Open.#2148 In hackforla/website;
- Status: Open.#3522 In hackforla/website;
- Status: Open.#3524 In hackforla/website;
- Status: Open.#3527 In hackforla/website;
- Status: Open.#3529 In hackforla/website;
- Status: Open.#2658 In hackforla/website;
- Status: Open.#4296 In hackforla/website;
- Status: Open.#4362 In hackforla/website;
ER from TLDL: Audit paragraphs on website
Status: Open.#4679 In hackforla/website;- Status: Open.#5277 In hackforla/website;
- Status: Open.#5248 In hackforla/website;
- Status: Open.#5474 In hackforla/website;
- Status: Open.#5440 In hackforla/website;
- Status: Open.#4370 In hackforla/website;
ER: Review the project.yml file template and files to fix the section for SDG info
Status: Open.#6277 In hackforla/website;- Status: Open.#6288 In hackforla/website;
- Status: Open.#6819 In hackforla/website;