Home

Welcome to the Codidact wiki!

Our goal is to enable community-driven and community-governed high-quality Q&A. We want to build a place for questions, a place for answers, a place for community. We'll learn from our experiences on other platforms, both the positive lessons and the negative ones, and do our best to build a platform that puts communities first and focuses on quality.

To do this, we'll build an open-source platform for Q&A sites and host an instance of it for interested communities. On our instance, content will always be free and never hidden behind paywalls or subscription fees. We'll seek donations to fund that instance, and when it comes time to create a legal entity, it will be non-profit so that shareholders' financial goals don't work against communities' interests.

Every community is different and needs vary. One size does not fit all, so our platform will be highly customizable. We will work with individual communities that want to join to learn what they need and help them create it.

We aspire to create software that is as accessible as possible, including localization.

Current Focus: Minimum Viable Product (MVP)

• Requirements
• [Functional specification]((https://github.com/codidact/docs/wiki/Functional-Specification)
• Forum discussions -- of particular note is the MVP tag. Help us prioritize and refine feature ideas! All are welcome.

For actual development:

• GitHub
• Coding standards
• Co-Design CSS framework
• Technology stack
• Database schema is currently being discussed on the forum

We have a Discord server for casual chat. Please bring conversations that require broader input to the forum. We're trying to move artifacts out of there so nobody has to dig through Discord, and are archiving some old channels there.

Who are we? Lots of folks, many of whom are dissatisfied Stack Exchange moderators and users. See also: organizational structure.

We share many goals and some people with another project you might want to know about: TopAnswers.

Project TODO list:

• Settle on a license for the software.

• Decide on the community management approach.

• Decide on which site(s) to build first.