New template proposal: Bäumlihof
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- json
- Domain
- data
Research direction
Use the raw JSON in the issue to create a template entry under data/. First inspect nearby files there to match the existing schema and naming conventions. Confirm the Bäumlihof year 9 entry includes the listed subjects, weights, and counted flags and is accepted by the project's existing template loading flow.
Written by the indexing model from the issue text.
Description
Proposed by a student, via the app's "Propose a template" flow.
- School: Bäumlihof
- Year: 9
- Their own semester name (context only, not the template name): 3. Sek. 2 Semester
| Subject | Weight | Counts |
|---|---|---|
| Deutsch | 1.0 | ✅ |
| NT | 1.0 | ✅ |
| Französisch | 1.0 | ✅ |
| Mathe | 1.0 | ✅ |
| Englisch | 1.0 | ✅ |
| Rzg | 1.0 | ✅ |
| Handarbeit | 1.0 | ✅ |
| Musik | 1.0 | ✅ |
| Sport | 1.0 | ✅ |
| Wah | 1.0 | ✅ |
Raw JSON (for turning this into data/*.json)
{
"school": "Bäumlihof",
"description": "9",
"subjects": [
{
"name": "Deutsch",
"weight": "1.0",
"counted": true
},
{
"name": "NT",
"weight": "1.0",
"counted": true
},
{
"name": "Französisch ",
"weight": "1.0",
"counted": true
},
{
"name": "Mathe",
"weight": "1.0",
"counted": true
},
{
"name": "Englisch ",
"weight": "1.0",
"counted": true
},
{
"name": "Rzg",
"weight": "1.0",
"counted": true
},
{
"name": "Handarbeit ",
"weight": "1.0",
"counted": true
},
{
"name": "Musik",
"weight": "1.0",
"counted": true
},
{
"name": "Sport",
"weight": "1.0",
"counted": true
},
{
"name": "Wah",
"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
-
resource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hesreallyhim/awesome-claude-code#3214 · 1 comment ·
Maintainers usually reply within 1 day
-
room-commons replace accepts an empty old string and silently prepends the new text to the pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
doobidoo/mcp-memory-service#1650 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ml-explore/mlx-lm#2002 ·
Maintainers usually reply within 2 days