add Ko-fi bean

This commit is contained in:
Julian Tabel
2026-03-20 16:38:54 +01:00
parent c9d42b091f
commit 5bd4ca7d3e
8 changed files with 109 additions and 13 deletions

View File

@@ -963,10 +963,29 @@
}
}
]
},
{
"role": "user",
"content": "I want to add a draft to integrate Ko-fi. While the idea is not to make money from this, if this where to be hosted somewhere, it will cost something, and maybe people want to help out with that.",
"timestamp": 1774021092843
},
{
"role": "assistant",
"content": "Created **Ko-fi Integration** (`nuzlocke-tracker-oar4`) as a `draft` / `deferred` feature. It has open questions to work through when you're ready to refine it — things like placement, widget vs. link, and whether supporters get any acknowledgment.\n\nAnything else?",
"timestamp": 1774021107517,
"toolCalls": [
{
"name": "Bash",
"args": {
"command": "beans create --json \"Ko-fi Integration\" -t feature -d \"Add Ko-fi integration to allow visitors to contribute toward hosting costs. This is not about monetization — it's a way for users who enjoy the tool to optionally help cover server/infrastructure expenses.\n\n## Open Questions\n\n- [ ] Where should the Ko-fi link/button live? (footer, about page, dedicated page, or subtle banner?)\n- [ ] Should it be a simple outbound link to a Ko-fi page, or use Ko-fi's embeddable widget/overlay?\n- [ ] Should there be any acknowledgment for supporters (e.g., a thank-you page, supporter list)?\n- [ ] Should this be gated behind user auth (only shown to logged-in users) or visible to everyone?\n- [ ] Any legal/tax considerations to document?\" -s draft -p deferred",
"description": "Create Ko-fi draft bean"
}
}
]
}
],
"createdAt": 1774018905931,
"updatedAt": 1774020533491
"updatedAt": 1774021107517
}
]
}