Clean up butler/config
Open
- Dominant language
- Go
- Stars
- 12
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I don't know why I put all the stuff that I did under butler/config. This needs to be re-thought out.
Contributor guide
Research direction
Start by inspecting the contents of butler/config and how the rest of the Butler CMS project uses them. The issue provides no target structure, entry point, tests, or definition of done, so the desired reorganization would need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100