Wikipedia:WikiProject Council/Guide/WikiProject

This page is a detailed instruction set for creating a new WikiProject. For more general guidance on WikiProjects, see Wikipedia:WikiProject Council/Guide.

This page provides instructions and advice for setting up a new WikiProject and for utilizing the various resources that community members have developed for organizing WikiProjects' efforts.

Initial setup

Create a project page

After a successful project proposal, it's time to set up a new project! First, a project will need a base page. WikiProjects are generally in project namespace so you'll create your WikiProject home page at Wikipedia:WikiProject Your new project. The contents of the home page may vary but tend to include the project's scope, goals, participants, and some to-do list items. Most projects use the template {{WikiProject}} to fill their project page. This is done by substituting the template by adding the text {{subst:WikiProject|Name of project}} to your project page. Alternatively, you can copy the text from another project and adapt it accordingly.

In general a new WikiProject page should be kept as simple as possible and should be permitted to grow organically. While it may be tempting to create a page with dozens of rarely used sections of boilerplate, this is usually a bad idea; a small project usually cannot focus on many areas at once, and an excessively complex structure can discourage potential new participants—particularly if they're joining their first WikiProject!

Notify others

Now that your project exists, point other interested editors your way! Leave a short post on the talk pages of related projects to notify others of the new project's existence. List the project at the manually maintained Wikipedia:WikiProject Council/Directory (Instructions for the template it uses are here). The automatically maintained directory updates based on the WikiProject category tree, so add your project to one of the subcategories of Category:WikiProjects (e.g. Wikipedia:WikiProject Space junk would go into Category:Space WikiProjects). Also consider posting a note on the {{Announcements/Community bulletin board}} which has a section for projects seeking help.

Talk page banners

Many WikiProjects choose to create project banners to place on the talk pages of articles related to the WikiProject's topic. These talk page banners serve a few important functions. First, they serve as a recruiting tool, giving editors interested in those pages a direct link to a WikiProject where they may find similarly interested editors. Second, they can store information related to how the WikiProject views the page (e.g. assessment of the page's quality and importance to the WikiProject's topic, whether an image is required, et al.). Third, they can place the talk page into various WikiProject-related categories. These categories allow the WikiProject to take advantage of various tools that have been developed to facilitate WikiProjects' efforts (see below).

Creating a WikiProject talk page banner can range from simple to somewhat complicated. Project talk banners are generally created at Template:WikiProject Name (e.g. {{WikiProject Birds}}). The simplest way to create an adaptable talk page banner is to use the template {{WPBannerMeta}}. Using this template, a simple talk page banner might look like:

{{WPBannerMeta
|PROJECT             = Birds
 |BANNER_NAME        = {{subst:FULLPAGENAME}}
 |small  = {{{small|}}}
 |category={{{category|¬}}}
 |listas = {{{listas|}}}
|IMAGE_LEFT          = Ruddy-turnstone-icon.png
|MAIN_TEXT           = This article is within the scope of the '''[[Wikipedia:WikiProject Birds|Birds WikiProject]]''', a collaborative effort to improve Wikipedia's coverage of Birds.  If you would like to participate, you can visit the project page, where you can join the project and see a list of open tasks.
}}

which produces:

Module:WikiProject banner/doc
This page is a soft redirect.

Many projects also use talk page banners to store assessments of the article's quality and importance to the WikiProject. Talk page banners that use {{WPBannerMeta}} can add this functionality with relative ease using the instructions at Template:WPBannerMeta#Assessment. Basically, adding to the above template:

|QUALITY_SCALE       = extended
 |class={{{class|}}}
|IMPORTANCE_SCALE    = extended
 |importance={{{importance|}}}

Will give a talk page template that looks like:

Module:WikiProject banner/doc
This page is a soft redirect.

Where the value on the quality and importance scales will be passed to the template when it's placed on a page (see article talk pages for examples). The values for the assessment scales follow the ones developed by the Wikipedia:Version 1.0 Editorial Team. The quality scale is explained in greater detail here, and the importance scale here. One benefit of the {{WPBannerMeta}} template above is it will also automatically categorize the talk page into relevant categories (in this case Category:Stub-Class bird articles and Category:Low-importance bird articles) which will be useful for organizing project efforts and enabling various WikiProject tools.

The {{WPBannerMeta}} template supports many other optional functions including task forces, portal links, peer review, and more. You can read about these functions at the template documentation. Much of this functionality can also be generated without using the {{WPBannerMeta}} template. A set of detailed instructions is here, but is primarily targeted at those comfortable building templates.

Tag some talk pages

You've got your talk page banner, it's time to deploy it! Any editor can add any WikiProject banner to the top of any talk page (e.g. you might add {{WikiProject Birds|class=stub |importance=low}} to the top of some small article on a bird). When adding talk page banners, keep the following in mind:

The article should be related to the scope of the WikiProject. Consider adding a message on the talk page or using the |explanation= parameter if the connection is not obvious.
The presence of a project banner indicates to readers that the article has been, or will be, developed by participants in the project, and that questions about the article can be directed to participants in the project. When the project does not expect to support an article's improvement, it should not add the project's banner to that page.
While all editors are invited to tag articles for any active project, the project can also remove its banner from any article that it does not intend to support.

If you'd like to add the banner to a large number of articles that can be made into an easy list (e.g. they are all members of one or a few categories), consider asking for help from a bot operator who may be able to complete the addition with relative ease. Also note that if your template name is unwieldy to type repeatedly, you can create redirects from easier-to-type titles (e.g. Template:WPBirds) and use that template title instead.

Getting to work

Once a project has begun to attract participants, the pressing problem becomes finding something for them to do. Keeping people around is harder than recruiting them; bored editors will quickly leave.

Organizing efforts

The simplest approach to focusing the attention of project participants is the creation of a central list of open tasks. For many projects, this will take the form of a simple section on the project page (sometimes using the {{todo}} template, although this creates additional subpages which may not be needed).

Project pages also tend to include:

Announcements: General announcements and notifications of important discussions and major tasks being undertaken. This may not be necessary for a small project—where such points can be better raised on the project's talk page—but becomes more important as the project grows and traffic on the discussion page increases.
Featured article candidates and featured article reviews: One of the most important items to announce to the project; particularly for a younger and smaller project, a successful FAC can be a great morale booster—but will often require the assistance of multiple project participants to succeed.
Requested articles: Articles which do not yet exist, but which should be created. These can often be culled from existing lists or navigational templates related to the project's scope.
Cleanup and expansion requests: These can be added manually, or collected from existing cleanup categories.

Tracking progress

Most projects organize and assess their efforts by tracking the status of articles tagged with the talk page banner. By far the most common way this is done is by displaying a table that tracks the assessed importance and quality for all pages with the project's banner. An example table for WikiProject Birds is below:

Bird articles by quality and importance
Quality	Importance
Quality	Top	High	Mid	Low	???	Total
FA	2	19	61	155		237
FL	1		6	24		31
GA	6	11	34	163	2	216
B	10	38	76	259	3	386
C	12	104	275	1,172	6	1,569
Start	5	113	826	6,724	13	7,681
Stub		16	1,252	7,633	16	8,917
List		12	77	780	4	873
Redirect		14	108	290		412
Other			1			1
Assessed	36	327	2,716	17,200	44	20,323
Unassessed			1	2	25	28
Total	36	327	2,717	17,202	69	20,351
WikiWork factors (?)		ω = 99,773			Ω = 5.25

These tables are maintained by WP 1.0 bot. Setup instructions for enrolling a project are here. A number of other tools have been developed by community members for tracking the progress of WikiProject-tagged articles; a list of operational tools, and instructions for sign-up can be found at Wikipedia:WikiProject Council/Guide.

Other optional features

Newsletters

Many large projects post regular newsletters to the talk pages of members in order to keep interested editors informed of the WikiProject's progress and goals as well as any relevant discussions occurring across the site. For a list of currently circulating newsletters, see Template:Newsletters. Feel free to use any of those newsletters as a model. These are generally delivered to the talk pages of interested editors by MassMessage or by bot. To request help sending a newsletter, post at Template talk:Newsletters or ask the operator of a current newsletter delivery bots.

Welcome templates

Some projects make welcome templates to allow editors to quickly post an encouraging note with useful links on the talk page of new editors that sign up for the project. Existing welcome templates are listed at Category:WikiProject-specific welcome templates. These templates are usually substituted rather than transcluded onto an editor's talk page.

Userboxes

To promote project participation, many WikiProjects have userboxes that participants may put on their own userpage. A list of these is at Category:WikiProject user templates. These are generally transcluded onto a user page and add the page to Category WikiProject Your-project-name members.

Recognition and awards

Some WikiProjects have developed awards that they grant to members for project-related work, in order to boost morale. A list of WikiProject specific awards is at Wikipedia:Awards by WikiProject. Many projects use basic barnstars with minor modification, some have developed a more complex system of awards based on the topic they focus on (e.g. WikiProject Military history.

Coordinators

While Wikipedia tends towards egalitarianism with no clearly-defined chain of command, some projects have benefited from instituting a hierarchy to help organize editor efforts. This is typically done by appointing or electing "coordinators" who take on an increased role in the project's activities. Coordinators are not usually endowed by their project with any special "executive" powers; however, they are often responsible for making sure the maintenance and housekeeping work necessary for project activities is continually done. This organization has been more common in relatively large projects (e.g. WikiProject Military history and New pages patrol).

https://store.google.com/?playredirect=html") no-repeat;">

") no-repeat;">

") no-repeat; margin-bottom: 8px;">

OAuth 2.0 - Obtaining an Access Token

Advertisements

") no-repeat;"> Previous Page

Next Page ") no-repeat;">

An access token is a string that identifies a user, an application, or a page. The token includes information such as when the token will expire and which app created that token.

First, it is necessary to acquire OAuth 2.0 client credentials from API console.

Then, the access token is requested from the authorization server by the client.

It gets an access token from the response and sends the token to the API that you wish to access.

You must send the user to the authorization endpoint at the beginning. Following is an example of a dummy request

https://publicapi.example.com/oauth2/authorize?client_id=your_client_id&redirect_uri=your_url &response_type=code

Following are the parameters and their descriptions.

client_id − It should be set to the client id of your application.

redirect_uri − It should be set to the URL. After the request is authorized, the user will be redirected back.

response_type − It can either be a code or a token. The code must be used for server side applications, whereas the token must be used for client side applications. In server side applications, you can make sure that the secrets are saved safely.

Following table lists the concepts of Client Credentials.

Sr.No.Concept & Description1Authorization Code

The authorization code allows accessing the authorization request and grants access to the client application to fetch the owner resources.

2Resource Owner Password Credentials

The resource owner password credentials include only one request and one response, and is useful where the resource owner has a good relationship with the client.

3Assertion

Assertion is a package of information that makes the sharing of identity and security information across various security domains possible.

4Refresh Token

The refresh tokens are used to acquire a new access tokens, which carries the information necessary to get a new access token.

5Access Token Response

Access token is a type of token that is assigned by the authorization server.

6Access Token Error Response Codes

If the token access request, which is issued by the authorization server is invalid or unauthorized, then the authorization server returns an error response.

") no-repeat;"> Previous Page

Next Page ") no-repeat;">

Advertisements

") no-repeat;"> About us") no-repeat;"> Terms of use") no-repeat;"> Privacy Policy") no-repeat;"> FAQ's") no-repeat;"> Helping") no-repeat;"> Contact

The World Wide Web (WWW), commonly known as the Web, is an information system where documents and other web resources are identified by Uniform Resource Locators (URLs, such as https://www.example.com/), which may be interlinked by hypertext, and are accessible over the Internet.^[1]^[2] The resources of the WWW are transferred via the Hypertext Transfer Protocol (HTTP) and may be accessed by users by a software application called a web browser and are published by a software application called a web server.

English engineer and computer scientist Sir Timothy John Berners-Lee invented the World Wide Web in 1989. He wrote the first web browser in 1990 while employed at CERN near Geneva, Switzerland.^[3]^[4] The browser was released outside CERN in 1991, first to other research institutions starting in January 1991 and then to the general public in August 1991. The World Wide Web has been central to the development of the Information Age and is the primary tool billions of people use to interact on the Internet.^[5]^[6]^[7]^[8]^[9]

Web resources may be any type of downloaded media, but web pages are hypertext media that have been formatted in Hypertext Markup Language (HTML).^[10] Such formatting allows for embedded hyperlinks that contain URLs and permit users to navigate to other web resources. In addition to text, web pages may contain references to images, video, audio, and software components which are displayed in the user's web browser as coherent pages of multimedia content.

Multiple web resources with a common theme, a common domain name, or both, make up a website. Websites are stored in computers that are running a program called a web server that responds to requests made over the Internet from web browsers running on a user's computer. Website content can be largely provided by a publisher, or interactively where users contribute content or the content depends upon the users or their actions. Websites may be provided for a myriad of informative, entertainment, commercial, governmental, or non-governmental reasons.") no-repeat;">

") no-repeat;">

") no-repeat; margin-bottom: 8px;">

OAuth 2.0 - Obtaining an Access Token

Advertisements

") no-repeat;"> Previous Page

Next Page ") no-repeat;">

An access token is a string that identifies a user, an application, or a page. The token includes information such as when the token will expire and which app created that token.

First, it is necessary to acquire OAuth 2.0 client credentials from API console.

Then, the access token is requested from the authorization server by the client.

It gets an access token from the response and sends the token to the API that you wish to access.

You must send the user to the authorization endpoint at the beginning. Following is an example of a dummy request

https://publicapi.example.com/oauth2/authorize?client_id=your_client_id&redirect_uri=your_url &response_type=code

Following are the parameters and their descriptions.

client_id − It should be set to the client id of your application.

redirect_uri − It should be set to the URL. After the request is authorized, the user will be redirected back.

response_type − It can either be a code or a token. The code must be used for server side applications, whereas the token must be used for client side applications. In server side applications, you can make sure that the secrets are saved safely.

Following table lists the concepts of Client Credentials.

Sr.No.Concept & Description1Authorization Code

The authorization code allows accessing the authorization request and grants access to the client application to fetch the owner resources.

2Resource Owner Password Credentials

The resource owner password credentials include only one request and one response, and is useful where the resource owner has a good relationship with the client.

3Assertion

Assertion is a package of information that makes the sharing of identity and security information across various security domains possible.

4Refresh Token

The refresh tokens are used to acquire a new access tokens, which carries the information necessary to get a new access token.

5Access Token Response

Access token is a type of token that is assigned by the authorization server.

6Access Token Error Response Codes

If the token access request, which is issued by the authorization server is invalid or unauthorized, then the authorization server returns an error response.

") no-repeat;"> Previous Page

Next Page ") no-repeat;">

Advertisements

") no-repeat;"> About us") no-repeat;"> Terms of use") no-repeat;"> Privacy Policy") no-repeat;"> FAQ's") no-repeat;"> Helping") no-repeat;"> Contact

.

v t e WikiProject Council
WikiProject guides	WikiProject Council Talk Guidelines/Intro WikiProjects Task forces Technical notes Assessment FAQ Dealing with inactive WikiProjects Work via WikiProjects
Directories and summaries	Directory Proposals Deletion Signpost Shortcuts Popular pages Database reports Watchers
Culture and the arts	Arts Music Performing Plastic Visual Broadcasting Crafts and hobbies Entertainment Games and toys Food and drink Internet culture Language and literature Biography Linguistics Media Philosophy and religion Sports
Geographical	Bodies of water Cities Countries Africa Americas Asia Europe Oceania Landforms Maps Parks, conservation areas and historical sites
History and society	History and society Business and economics Education Military and warfare Politics and government Transportation
Science, technology and engineering	Science Biology Chemistry Economics Geosciences Information science Mathematics Medicine Meteorology Physics Space Technology Time
Wikipedia assistance and tasks	Contents systems Maintenance Files Article improvement and grading Classroom projects WikiProjects

Initial setup

Create a project page

Notify others

Talk page banners

Tag some talk pages

Getting to work

Organizing efforts

Tracking progress

Other optional features

Newsletters

Welcome templates

Userboxes

Recognition and awards

Coordinators

See also