The eagle-eyed among us have already noticed that a few hours ago, I added a qpixel repository to our organisation. For the unacquainted: qpixel is the software that’s running writing.codidact.com - the site that’s hosting the Writing community to avoid it dying out completely on Stack Exchange.
Prompted by some discussion around our tech stack in the past week or so, we’ve been kicking ideas around between the leads. It seems that a number of the concerns folks have expressed come back to the central idea that we’re not working quick enough. The impetus that Stack Exchange has given us by being terrible won’t last forever; we need to have something to show communities when they come knocking.
So, putting those two things together: here’s the plan.
Point the First: we take what we have in qpixel, and update it to work for us. There’s a small number of significant changes we need to make for it to work for us, and a larger number of small polishes. We’ll use this to host communities for now, while…
Point B: qpixel isn’t Codidact; it’s still very much SE-style Q&A, even with updates. So we’re going to keep working on Codidact, because that’s our new format, and because that has the potential to be much better than SE-style Q&A. It’ll take longer to launch, but that’s okay - we’ll be able to host communities in the meantime, and let them switch over once we’re ready.
Point III: The point (ha!) of this plan is twofold. One: we get the ability to get communities on board soon (a few weeks to a month, with any luck). Two: the folks we currently have who can’t contribute to .NET Core, for some reason, may be able to contribute to a Rails app instead: that way, we engage more of our people, and keep ourselves growing.
There’s bits of work to be done before we’re quite ready for this, but stay tuned