Refactor: Extract hardcoded projects list into JSON and render dynamically
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- frontend
Research direction
Locate the frontend template containing the hardcoded submitted projects and the stats bar, then inspect how the project components are currently rendered. Move the project data into a structured JSON source and render the project list dynamically; clarify whether country and community statistics are also part of done, since the issue leaves those totals unresolved.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- HTML
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pythonph/osspyasia
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in pythonph/osspyasia
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bramus/rich-input#7 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·