There are two events' data YAMLs one is not rendered.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 4
Description
There are data files in _data/events.yaml and also in _data/ospo/events.yaml. The latter seems not to be rendered anywhere.
I strongly propose we merge. This is confusing and messy. In fact the whole _data/ospo subdirectory should be put at top level. Avoid unnecessary nesting.
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.
Research direction
Start by comparing _data/events.yaml with _data/ospo/events.yaml, then search the site templates and configuration for references to _data/ospo. Determine which data is rendered and update the relevant references while merging the event data and flattening the directory. Done means the site still renders all events with one authoritative data location and no unnecessary _data/ospo nesting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, yaml
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100