Welcome to the Judaism community on Codidact!
Will you help us build our community of learners? Drop into our study hall, ask questions, help others with answers to their questions, share a d'var torah if you're so inclined, invite your friends, and join us in building this community together. Not an ask-the-rabbi service, just people at all levels learning together.
Post History
I like the idea of returning to our weekly topic challenges! Instead of collecting new suggestions each week, which would mean either lots of repetition or suggestions getting dropped, I suggest re...
Answer
#2: Post edited
by
Monica Cellio
·
2020-07-13T18:20:06Z (over 4 years ago)
- I like the idea of returning to our weekly topic challenges!
- Instead of collecting new suggestions each week, which would mean either lots of repetition or suggestions getting dropped, I suggest reusing a single post to collect suggestions for a while, and each week the person running the challenge picks one. Usually this would be the top-voted one not already used, but if there's something seasonal that makes more sense that particular week, that should be ok too. When a topic is chosen, the answer suggesting it gets edited to say it's been used (and linking to the challenge).
- I said "for a while", because if there were only one suggestion post then over time it would become hard to manage (and hard to find the still-unused topics). Maybe make a new topic-collection post each quarter? Resubmitting things would be fine but this way it wouldn't be every week.
- If I recall correctly, on Mi Yodeya we made a new meta post for each challenge, with each question that was asked as part of the challenge being linked in an individual answer. (So you'd ask a challenge question on main and then add a meta answer linking to it.) We *could* do that, but I wonder if we'd rather have a single post that collects all the links? The individual posts don't need to be votable *on meta*, after all. A downside of this approach is that we don't have the "anybody can edit this specific post" concept like SE does (community wiki), so some people will have to propose edits. But approving those edits should be pretty easy and pending edits are pretty visible, so this doesn't seem like a big problem for this case.
- I like the idea of returning to our weekly topic challenges!
- Instead of collecting new suggestions each week, which would mean either lots of repetition or suggestions getting dropped, I suggest reusing a single post to collect suggestions for a while, and each week the person running the challenge picks one. Usually this would be the top-voted one not already used, but if there's something seasonal that makes more sense that particular week, that should be ok too. When a topic is chosen, the answer suggesting it gets edited to say it's been used (and linking to the challenge).
- I said "for a while", because if there were only one suggestion post then over time it would become hard to manage (and hard to find the still-unused topics). Maybe make a new topic-collection post each quarter? Resubmitting things would be fine but this way it wouldn't be every week.
- If I recall correctly, on Mi Yodeya we made a new meta post for each challenge, with each question that was asked as part of the challenge being linked in an individual answer. (So you'd ask a challenge question on main and then add a meta answer linking to it.) We *could* do that, but I wonder if we'd rather have a single post that collects all the links? The individual posts don't need to be votable *on meta*, after all. A downside of this approach is that we don't have the "anybody can edit this specific post" concept like SE does (community wiki), so some people will have to propose edits. But approving those edits should be pretty easy and pending edits are pretty visible, so this doesn't seem like a big problem for this case.
- ----
- **Update:** On request and confirmed by our moderator, I've created a new [Challenges](https://judaism.codidact.com/categories/34) category. I have enabled both Question and Article post types; if Article doesn't work out we can always remove it. I suggest that you use questions to collect suggestions and articles for individual challenges; in the latter you'd describe the challenge and then the community can edit it to add links to questions that were asked in response to that challenge.
- On links, we don't have the SE link-magic that turns raw links into the titles of their posts, sorry. So editing will be a little more work than it would have been otherwise, at least for now.
#1: Initial revision
by
Monica Cellio
·
2020-07-12T02:39:08Z (over 4 years ago)
I like the idea of returning to our weekly topic challenges! Instead of collecting new suggestions each week, which would mean either lots of repetition or suggestions getting dropped, I suggest reusing a single post to collect suggestions for a while, and each week the person running the challenge picks one. Usually this would be the top-voted one not already used, but if there's something seasonal that makes more sense that particular week, that should be ok too. When a topic is chosen, the answer suggesting it gets edited to say it's been used (and linking to the challenge). I said "for a while", because if there were only one suggestion post then over time it would become hard to manage (and hard to find the still-unused topics). Maybe make a new topic-collection post each quarter? Resubmitting things would be fine but this way it wouldn't be every week. If I recall correctly, on Mi Yodeya we made a new meta post for each challenge, with each question that was asked as part of the challenge being linked in an individual answer. (So you'd ask a challenge question on main and then add a meta answer linking to it.) We *could* do that, but I wonder if we'd rather have a single post that collects all the links? The individual posts don't need to be votable *on meta*, after all. A downside of this approach is that we don't have the "anybody can edit this specific post" concept like SE does (community wiki), so some people will have to propose edits. But approving those edits should be pretty easy and pending edits are pretty visible, so this doesn't seem like a big problem for this case.