Post History

A wiki with a dictionary of terms sounds like a great idea.  Here are some thoughts on how we could implement it.  It partly depends on being able to use in-page anchors (so you could link to a specific part of a page); that appears to be possible if one uses HTML for those links (and anchors) instead of Markdown.

We could create a Wiki category (or choose another name if you like).  This category would support the article post type but not questions and answers.  There could be a "main" page that lists all terms with short definitions, each with an anchor for direct linking.  When a topic calls for more explanation and somebody wants to provide it, that person would add another (article) post and link to it from the definition on the main page.  To keep the main page discoverable regardless of posts' sorting order, we could link to it in the category description.  Initially there would be one post, probably a few more soon, and I'm guessing there wouldn't be more than would fit on a page for quite some time.

We could link to the main page from the help.  The reason I'm not suggesting putting the list in the help directly is that help can be edited only by moderators while anybody can edit (or suggest edits to) articles.

Articles require tags, same as questions.  We can either share the tag set used for Q&A or create a separate one.  We should think about what kinds of tagging (and tagging relations) we want.  A search by tag finds all posts with that tag in all categories.

One thing that is not currently possible is some sort of Markdown extension to easily link to definitions from other posts.  You would have to use the HTML links I mentioned earlier, instead of having some syntax around a word that would automatically generate that link.  This sounds like something that could be done in a userscript; that's not as good as having it built in for all users, *but* I suspect that the people who'll think to add glossary links are going to be the more-invested users who are probably more willing to use a userscript, so that might be ok.  I think building that in would be fairly low on the developers' priority list right now; there's a lot of other work we need to do yet.