New template proposal: NKSA
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- json
- Domain
- content
Research direction
Start by checking the existing template files in data/ and how the app turns submitted proposals into templates. Add the NKSA Year 10 subjects with the listed weights and counted flags, trimming accidental trailing spaces from subject names. Done means the template follows the existing data format and appears correctly in the app.
Written by the indexing model from the issue text.
Description
Proposed by a student, via the app's "Propose a template" flow.
- School: NKSA
- Year: 10
- Their own semester name (context only, not the template name): 2026/2027 - 1
| Subject | Weight | Counts |
|---|---|---|
| AGSW | 1.0 | ✅ |
| BiG | 1.0 | ✅ |
| Chemie | 1.0 | ✅ |
| Deutsch | 1.0 | ✅ |
| Englisch | 1.0 | ✅ |
| Französisch | 1.0 | ✅ |
| Geografie | 1.0 | ✅ |
| Geschichte | 1.0 | ✅ |
| Informatik | 1.0 | ✅ |
| Mathematik | 1.0 | ✅ |
| Wirtschaft | 1.0 | ✅ |
| Sport | 1.0 | — |
| Biologie | 1.0 | ✅ |
Raw JSON (for turning this into data/*.json)
{
"school": "NKSA",
"description": "10",
"subjects": [
{
"name": "AGSW",
"weight": "1.0",
"counted": true
},
{
"name": "BiG",
"weight": "1.0",
"counted": true
},
{
"name": "Chemie",
"weight": "1.0",
"counted": true
},
{
"name": "Deutsch",
"weight": "1.0",
"counted": true
},
{
"name": "Englisch",
"weight": "1.0",
"counted": true
},
{
"name": "Französisch ",
"weight": "1.0",
"counted": true
},
{
"name": "Geografie ",
"weight": "1.0",
"counted": true
},
{
"name": "Geschichte",
"weight": "1.0",
"counted": true
},
{
"name": "Informatik",
"weight": "1.0",
"counted": true
},
{
"name": "Mathematik ",
"weight": "1.0",
"counted": true
},
{
"name": "Wirtschaft",
"weight": "1.0",
"counted": true
},
{
"name": "Sport",
"weight": "1.0",
"counted": false
},
{
"name": "Biologie",
"weight": "1.0",
"counted": true
}
]
}
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 9h 6m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 FidelisFactory/FidelisFactory.github.io
-
template-proposal
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Improve landing pageOpenhelp wanted website
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FidelisFactory/FidelisFactory.github.io#2 · 1 comment ·
All issues in FidelisFactory/FidelisFactory.github.io
Similar issues
-
good first issue priority: low size: XS testing
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
cubrid-lab/cubrid-mcp-server#385 ·
Maintainers usually reply within 1 day
-
good first issue priority: low size: S testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cubrid-lab/cubrid-cookbook-python#447 ·
Maintainers usually reply within 1 day
-
Python PointcloudOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ArduCAM/Arducam_tof_camera#125 ·
-
area:curator enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
CassioDalla/Scrinalia#150 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100