mazzzystar / mazzzystar/tinymind
[Discussion] do we really need comment?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 807
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
It's true "Comment" is a common requirement for a blog service, but we also have to admit that "comment" make the system more complicated, for this software on technically, also for the blogger mentally.
Personally I like having interactions with the readers, getting feedbacks from the blog visitors is always feeling good, if there's light (technically and mentally) way to enable the "Comment", I would second on it.
Contributor guide
No contributing guide indexed for this repository
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 reading the issue discussion and reviewing how the blog currently handles reader interactions. The issue does not name files, entry points, or tests, and it leaves the desired comment behavior unresolved. Done would require an agreed lightweight approach and a defined scope before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100