Description:
Currently, the list of submitted projects is hardcoded directly into the template. As the repository of projects grows, this approach will become increasingly difficult to maintain and makes it harder to implement dynamic features like search, filtering, and pagination.
Proposed Solution:
Extract the existing hardcoded project data into a structured JSON file (or an array of JSON objects).
Update the frontend template to loop through this JSON data and render the project components dynamically.
To add, the total projects should be dynamic. Not sure yet about countries and community.
<div class="stats-bar">
<div class="stat">
<span class="stat-number">4</span>
<span class="stat-label">Projects</span>
</div>
<div class="stat-divider"></div>
<div class="stat">
<span class="stat-number">3</span>
<span class="stat-label">Countries</span>
</div>
<div class="stat-divider"></div>
<div class="stat">
<span class="stat-number">1</span>
<span class="stat-label">Community</span>
</div>
</div>This separation of data and presentation will make future community contributions and UI updates much cleaner.
Description:
Currently, the list of submitted projects is hardcoded directly into the template. As the repository of projects grows, this approach will become increasingly difficult to maintain and makes it harder to implement dynamic features like search, filtering, and pagination.
Proposed Solution:
Extract the existing hardcoded project data into a structured JSON file (or an array of JSON objects).
Update the frontend template to loop through this JSON data and render the project components dynamically.
To add, the total projects should be dynamic. Not sure yet about countries and community.
This separation of data and presentation will make future community contributions and UI updates much cleaner.