Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Community Wiki Posts [duplicate]

+4
−0

Closed as duplicate by Moshi‭ on Oct 26, 2020 at 22:17

This question has been addressed elsewhere. See: Do we have/should we have community wikis?

This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.

Also see the more active discussion on https://meta.codidact.com/questions/278386


Will there ever be something akin to StackExchange Community Wikis? While I'm not sure of the specifics (I've never interacted with its posts), I believe that it allows such things as letting the community review edit suggestions instead of the original poster.

The use case that I'm thinking of is for the Resources category of Language, where I'm active-ish. Since one of the roles of the category was to be a community wiki of sorts, it would help streamline updating the resources (right now, if the poster takes a break from the site, we're stuck unless someone with direct edit privileges steps in)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+4
−0

I think you're asking about what SE calls community wiki, as opposed to the community user. On SE, the Community user owns things that are otherwise ownerless, like posts from deleted users. Community wiki, on the other hand, is a status that an individual post has, meaning "make it easy for people to edit this".

I've been wondering if we need that too. I've been further wondering: should this be something set for individual posts, or should it be possible to change editing restrictions on a category-by-category basis? The latter can be implemented using the former, of course, but: do we need to be able to set this status on selected posts in other categories, like that one answer in the Q&A category, or does having categories (which SE doesn't) naturally push sites toward the wikis being in, well, a wiki category? (Or resources, or whatever a community decides to call it.)

I think we'll want to do something here. I'd like feedback on what fits our platform best.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (1 comment)