Return to Question

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

###What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

###What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

###OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

###Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

###What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

###What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

###OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

###Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

###What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

###What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

###OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

###Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

###What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

###What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

###OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

###Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?

I would like to propose a new PostType to the tetralogy. PostType = Wiki.

###What should be Wiki?

I think the ideal candidates for wiki style posts would be posts that are long and already are community wiki.

For example this query captures quite a few of them: http://odata.stackexchange.com/stackoverflow/q/66

###What is different about Wiki posts?

• Wiki posts are owned by the community.
• You can gain reputation by improving Wiki posts.
• Wiki posts do not fit the current Q&A model, the question is the title, the answer is the body.
• Wiki posts only have commenting, there is no answering allowed.
• Wiki posts have a special UI
• Wiki posts have search priority (maybe)

###OK, give some examples

List of freely available programming books is a wonderful post with lots of information, the trouble is, there is no incentive to keep it up to date. And the answers, well they are noisy and a repeat of what is at the top.

One more is Git for beginners. The big trouble is that you need a page reload every time you want to navigate to a section. And scroll-up foo.

Another C++ for a C# developer. It's really useful information that would cover probably a few hundred questions and really is a community effort.

The seminal Hidden Features of C#? would by amazing if it was just a single document with collapsible sections. After you work through 2 of them you just get tired of refreshing your web browser.

This one, The .NET SDK Programs - What does each tool do?, fits the wiki mold so tightly it's scary. It's a perfect candidate.

###Other ideas around post type wiki

• Wikis could be used for some static pages on the site like this one.
• On meta we could use a wiki for the long requested change log
• If we allow an abstract for wikis (8 lines of so) they could be associated with a tag and show up in the box when a tag is selected.

So:

1. Do we need this kind of post?
2. What are the mechanics involved in building this?