|
|
| Line 1: |
Line 1: |
| − | <noinclude><small> < [[ContentCreation]] </small> <br><br>
| + | #REDIRECT [[Project:Common Answers]] |
| − | <big>[[DevelopmentPriorities]] < </noinclude>[[CommonAnswers]] ('''3''') <noinclude></big>
| |
| − | | |
| − | * Track frequent questions (searches)
| |
| − | * Track the quality of the answers to frequent searches
| |
| − | | |
| − | Provide good wiki pages to answer common searches. Also show a page that tracks which are the most common searches, and how good the answer page for the search is.
| |
| − | | |
| − | [[NeedsAcceptanceTest]]
| |
| − | | |
| − | ==Generating the Common Answers List By Hand==
| |
| − | Common Answers will derive directly from metrics on web queries in the following areas: | |
| − | | |
| − | * Top queries on AboutUs - Derived from an internal list
| |
| − | * Top Web Queries - Derived from [http://www.searchengineguide.com/wt/ SearchEngineGuide.com]
| |
| − | | |
| − | These lists will be updated weekly at [[CommonAnswersCue]] and culled to eliminate redundancy (pages already in existence on the site) and inappropriate content (i.e. adult or illegal). This will be done by hand for the time being. Ideally we will be up to date with all time sensitive searches but also provide full content on "historically" (past three months or so) popular material. Over time our information will only improve.
| |
| − | | |
| − | ''We talked in today's strategy meeting about building out subdomains and reaching out to the blogosphere. We could start with the [http://technorati.com/pop/blogs/ Technorati Top 100]. Just a thought.''
| |
| − | *[[User:Blake Hinckley|Blake Hinckley]]
| |
| − | | |
| − | ==Concerns==
| |
| − | How to eliminate redundancy and work already done. We will need a bot for this later that will check to see if an article is present (# of bites combined with # of edits?).
| |
| − | : ''Why should pages not be edited if they have been in the past? It seems like if it's a hot topic there's something to be written about it. ''
| |
| − | | |
| − | We should rethink the name common answers and come up with something more obvious and catchy.
| |
| − | | |
| − | | |
| − | </noinclude>
| |
