FujoWebDev / FujoWebDev/ao3-content-layer-example
Allow setting different path for content file
Open
good first issue
- Dominant language
- Astro
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This could be configured when creating the loader
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the loader creation entry point and the code that chooses the content file path. Determine how a path option would be passed during loader configuration. Done means callers can select a different content-file path without breaking the existing default behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100