|
=== Identifikasi cakupan terbaik ===
Selanjutnya, identifikasilah cakupan paling bagus untuk projek Anda. ProyekWiki yang sukses memiliki cakupan yang tidak dibuat-buat dan cukup untuk menarik minat para editor dan menjaga keberlangsungannya. Sebagai contoh, apakah [[Tulip]] terlalu kecil sebagai suatu cakupan proyek, yang mungkin hanya bisa terdiri dari beberapa puluh artikel dan enam peserta proyek (yang beberapa juga tidak banyak kerja)? Kriteria-kriteria ini seharusnya bisa membuat Anda mempertimbangkan bahwa cakupan yang lebih luas lebih bagus. Dengan memasukkan seluruh [[Liliaceae|keluarga lily]], tulip juga termasuk, atau semua [[bunga]], atau subyek yang lebih luas tentang taman dan hortikultura.
Next, identify the best scope for your project. Successful WikiProjects have a scope that is natural and broad enough to attract and sustain editor interest. For example, are [[Tulip]]s too small a project scope, such that it might only ever have a few dozen articles and six project participants (some of whom don't do much)? Either of those criteria should be enough to make you think that maybe a larger scope would be better. You might be able to get a more reasonably sized project by including the entire [[Liliaceae|Lily family]], which includes tulips, or all [[flower]]s, or the larger subject of gardening and horticulture.
ohibits two separate groups of editors from being interested in the same articles.
The risks of a narrow scope are:
* '''Not enough people''': Your group may die from administrative overload, and become one of the more than 400 [[:Category:Inactive WikiProjects|Inactive WikiProjects]].
* '''Not enough pages''': People will quickly complete the work and get bored. Your project may die from administrative overload, and likewise become inactive.
* '''Too much overlap''': If the scope is too closely related to an existing project, then having separate projects is usually inefficient and counterproductive, because you wind up dividing the few interested editors across multiple projects. This approach maximizes administrative hassles and minimizes collaboration. However, there is no rule that prohibits two separate groups of editors from being interested in the same articles.
;How to estimate the number of pages in your proposed scope:
# Go to the main article. Click on [[Special:WhatLinksHere|"What links here"]], and see how many articles are connected to this one. This is probably your number, unless you limit the scope in some way (e.g., only including {{em|significant}} tulip {{em|growers}} (not just fanciers) from before 1900 in the Biography category).
# Look in the [[Help:Categories|categories]] associated with your key articles. The proposed WikiProject Tulips, for example, would want to consider categories like [[:Category:Flowers]] and [[:Category:Tulipa]].
Having considered the probable size of the scope, ask yourself, "Is this a 'natural' scope?" Will other people be able to easily understand what kind of articles the group is working on? WikiProjects are allowed to have strange, arbitrary, or unpredictable scopes ("Tulips, except for my least favorite species, plus my favorite photo software"), but we strongly recommend that you adjust or expand the scope to be more sensible.
At the end of this step, you should know approximately how many articles are likely to be within the project's scope, what the names of the key articles and categories are, and [[elevator pitch|how to describe the scope briefly]]. That information will help you determine the best structure.
=== Identifikasi struktur terbaik ===
| 