1,623
edits
| Line 32: | Line 32: | ||
**If we allow generated content be inserted using a syntax like {localizationTable(articleList, startIndex, numberOfArticles, statusFilter)}, that would give us a lot of flexibility in how we want to present the work. | **If we allow generated content be inserted using a syntax like {localizationTable(articleList, startIndex, numberOfArticles, statusFilter)}, that would give us a lot of flexibility in how we want to present the work. | ||
***For example, if we wanted to provide a separate list of the articles waiting for review, we could use {localizationTable(KB, 0, 0, needsReview)} | ***For example, if we wanted to provide a separate list of the articles waiting for review, we could use {localizationTable(KB, 0, 0, needsReview)} | ||
***Another example, if we wanted to list the '''next 15 articles''' in need of review or translation (rather than just showing the status of the first 15 articles), we would use: {localizationTable(KB, 0, 15, untranslated+needsReview)} | ***Another example, if we wanted to list the '''next 15 articles''' in need of review or translation (rather than just showing the status of the first 15 articles as shown in the mockup), we would use: {localizationTable(KB, 0, 15, untranslated+needsReview)} | ||
*** This way, we have the flexibility to change the way we present the information | *** This way, we have the flexibility to change the way we present the information. The system should also be flexible enough to work well for other localizable TikiWiki installations. This would even allow locale leaders to customize their view based on what works best for them. | ||
* Because the [http://support.mozilla.com/en-US/kb/Weekly+common+issues Weekly Common Issues] list is calculated using a combination of TikiWiki data and web analytics software (in our case Omniture), we need the ability for an external system to "tell" TikiWiki the priority of the KB. Marc Laporte mentioned a tracker db; seems like a fine solution to me. So, a tracker would contain a list of articles in a specific order. | * Because the [http://support.mozilla.com/en-US/kb/Weekly+common+issues Weekly Common Issues] list is calculated using a combination of TikiWiki data and web analytics software (in our case Omniture), we need the ability for an external system to "tell" TikiWiki the priority of the KB. Marc Laporte mentioned a tracker db; seems like a fine solution to me. So, a tracker would contain a list of articles in a specific order. | ||
*We need to be able to put data in this tracker using e.g. a bash script or similar. | *We need to be able to put data in this tracker using e.g. a bash script or similar. | ||
edits