New template proposal: Bezirksschule Wohlen
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- json
- Domain
- content
Research direction
Start by checking the existing files in data/ to see how school templates are named and structured. Add a template for Bezirksschule Wohlen using the supplied school, description, and subject data; it is done when the new template follows the existing format and includes all ten subjects with weight 1.0 and counted true.
Written by the indexing model from the issue text.
Description
Proposed by a student, via the app's "Propose a template" flow.
- School: Bezirksschule Wohlen
- Year: B2e (8.Klasse)
- Their own semester name (context only, not the template name): Semester 01
| Subject | Weight | Counts |
|---|---|---|
| Mathematik | 1.0 | ✅ |
| NT | 1.0 | ✅ |
| Französisch | 1.0 | ✅ |
| RZG | 1.0 | ✅ |
| WAH | 1.0 | ✅ |
| Deutsch | 1.0 | ✅ |
| Englisch | 1.0 | ✅ |
| Sport | 1.0 | ✅ |
| BG | 1.0 | ✅ |
| Italienisch | 1.0 | ✅ |
Raw JSON (for turning this into data/*.json)
{
"school": "Bezirksschule Wohlen",
"description": "B2e (8.Klasse)",
"subjects": [
{
"name": "Mathematik",
"weight": "1.0",
"counted": true
},
{
"name": "NT",
"weight": "1.0",
"counted": true
},
{
"name": "Französisch",
"weight": "1.0",
"counted": true
},
{
"name": "RZG",
"weight": "1.0",
"counted": true
},
{
"name": "WAH",
"weight": "1.0",
"counted": true
},
{
"name": "Deutsch",
"weight": "1.0",
"counted": true
},
{
"name": "Englisch",
"weight": "1.0",
"counted": true
},
{
"name": "Sport",
"weight": "1.0",
"counted": true
},
{
"name": "BG",
"weight": "1.0",
"counted": true
},
{
"name": "Italienisch",
"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
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gramaziokohler/compas_timber#870 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
autowarefoundation/autoware_carla_scenario#500 ·
Maintainers usually reply within 1 day
-
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100