Willipedia:Naming conventions

This is a draft of a policy being worked on by the Willipedia board. It has no effect until approved by board consensus.

1. Singular vs. Plural nouns

wiki link

willi rule of thumb: when the main focus of an article will be to define or give the history of the subject, use a singular noun (broomball, Mountain Day). when listing and explaining instances of the subject -- especially when defining what the title means would be silly for willipedia -- use a plural (Pranks, Classes).

1. Use -ing Verbs

wiki link

for activities, common practices, and the like, try to use the most basic but most unique gerund verb applicable. Instead of "Great places to ski" use "Skiing" and, after talking generally a little about skiing at williams, have a section on "places" if you wish.

When what would otherwise be a section gets large and detailed/complex enough to be its own article (Skiing cheaply) use the shortest descriptive title you can (Skiing cheaply vs. Ways you can ski cheaply) and be sure to link to this article in a (perhaps empty) section of the main article.

1. General philsophy

Use the most general title you can about your subject, when you feel a Williamsian can write something meaningful about the general title (i.e., even if you can't)

example: you want to write about the awesome beech in the forest garden for tree climbing. start/edit "Tree climbing"

example: you want to write about cheap places to ski. start/edit "skiing" and start a section in it on going cheaply. hope you or someone else will write the preface on generally skiing at williams

example: you want to write about great spots to hang hammocks on campus. "Hammocking" is the most general title, but is there something meaningful to write on "hammocking" besids where to do it? This is arguable. Start/edit "hammocking" with a section on places, or start/edit "hammock spots". Someone can always create "hammocking" and link to/move your content later.

http://en.wikipedia.org/wiki/Wikipedia:Naming_conventions#Be_precise_when_necessary