Post History

I hear the walk-before-we-run argument. I think this would be a good thing to try once we reach running speed, though.

Personally, I don't like self-answered questions; I think they're an awkward fit for Q&A sites. I'm primarily here to scratch my itch to help people—when I see a question that's relevant to my interests, only to realize that the asker never wanted help with the question at all, I feel a little let down. Spreading knowledge proactively is a noble goal and I don't want to discourage it, but I think there ought to be a more fit-for-purpose way to do it than the self-answer approach, which I think is kind of a hack.

The proper comparison with articles here would not be Wikipedia articles, IMO, but articles on GitHub wikis for specific projects. Wikipedia is a bad place for rando project documentation because it doesn't meet notability requirements. GitHub wikis are a good place to put that documentation, but GitHub issues are, in some projects' opinions, bad places to ask questions, and so you see a lot of `README.md` instructions asking users to consult both the wiki on GitHub and Some Other site when they have questions. Enabling articles would let projects define a one-stop shop for knowledge base articles *and* Q&A, which I think would make a certain amount of sense.