5 replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
source | link

Are we talking about the static FAQ pagethe static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for thatwe already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.
4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorerthe data explorer (once it includes the beta sitesonce it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.
3 Migration of MSO links to MSE links
source | link

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorerthe data explorer (once it includes the beta sitesonce it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.

Are we talking about the static FAQ page? I would keep this clean and only put questions about this site there.

What do we expect from this list?

  • If you want to use it to prevent duplicates, you expect every user looks there first. What percentage of visitors will do this? We already have an automatic duplicate question search when you start typing your question. But this only works with questions in the Stack Exchange system, not with the text of the FAQ.
  • If you want a list of most popular questions (which is probably a good indicator for frequently asked), you can sort the questions by votes (starred questions). If you want more detail, you can use the data explorer (once it includes the beta sites).
  • If you want a list of stuff you should know about a topic, we have the tags for that. Tags can only be changed by people who have more than 500 rep (only in the private beta everyone can edit them), so there should not be much abuse that cannot be resolved in meta, or in extreme cases by user bans.

Or, in reverse, Why I think a static text is not the best way

  • You can hope people will read the FAQ first to prevent beginner questions, but I suspect they will not. Certainly not if the FAQ it too long. And a short list of questions might not include the question they have.
  • I suspect most people search for answers via a search engine, and if they phrase their question in a totally different way, they will not hit the FAQ. If all FAQ questions are SE questions, we can easily close them as duplicates, so future searches for this formulation will hit that page, with a clear link to the "real" answer page.
  • The FAQ is not included in the search for duplicate questions, or even in the site search. Yes, this can change, but you will need good reasons to convince the owners why this cannot be handled via regular questions.
  • Will we put all questions on one page (since there currently is no way to use sub-pages)? This will make a very long list, if we want to include FAQ questions on different subjects (admin, theming, plugins, ...). People will need to search the list anyway, so why not split them up in different questions? Or do I have a wrong idea about how people read FAQs?
  • The FAQ will need to be curated, which requires discussion about what to include and what not, and in what order. But by definition, a FAQ contains (or should contain) those questions that are asked most frequently. As I said, we already have a good proxy for that. Yes, more views could be requested, and if they are useful for all sites, they probably will be implemented.
2 Clearer list of arguments
source | link
1 Post Made Community Wiki
source | link