An itinerary is a guide for traveling along a specific route through several destinations or attractions, giving suggestions of where to stop, what to see, how to prepare, etc. If you think of our destination guides as dots on a map, an itinerary describes a line that connects those dots.
Valid itinerary article subjectsویرایش
An itinerary article should be a guide for traveling along a specific route and not merely a suggested sightseeing schedule. Examples of good itinerary subjects are Hajj (a traditional pilgrimage route) or The Wire Tour (a guide for visiting filming locations for a television show). Invalid itinerary topics would include "One week in Sydney" or "Best of Bhutan"; information that would be included in such itineraries should instead be added to the appropriate city or region articles.
Two questions that can help determine whether or not a subject is a good candidate for an itinerary article are the following:
- Is the itinerary article about a specific route? Travelers can agree on what content would be included in an article such as Appalachian Trail, but it is completely subjective what should be included in vague conceptions such as "Ten days in Slovakia" or "Cultural tour of West Africa".
- Should the content in the itinerary article be covered elsewhere on Wikivoyage? An article such as "Visiting Cairo's museums" would probably just duplicate content that should instead be placed in the main Cairo articles.
In general, if there is any question whether a subject is a good itinerary topic or not, start out by first including the information in the appropriate city or region article(s), and ask in the Pub whether a separate itinerary article makes sense.
For any type of itinerary, a map is very, very useful for planning and visualizing. See Project:How to draw a map for details on how to draw one yourself.
Itinerary article titlesویرایش
The following are some guidelines for naming itinerary articles:
- Use the traditional or legal name for a route if one exists. For example, the Annapurna Circuit, Route 66, Trans-Canada Highway.
- Articles on historical routes can use titles like On the trail of Marco Polo, but where the route has a name, such as Lewis and Clark Trail, use that instead.
The closer article titles come to these guidelines, the more likely readers and contributors will recognize them as itineraries.
In the past Wikivoyage permitted the creation of itinerary articles that were not about a specific route such as "Two months in Europe by rail" or "One day in Tokyo", but this practice is now deprecated for several reasons:
- "Personal" itineraries encourage creation of arbitrary articles that aren't collaborative. While everyone can agree on what should go in an itinerary article like Alaska Highway, a "One day in Tokyo" article is personalized to the taste of the author (not our diverse readership), thus defeating a primary advantage of Wiki.
- "Personal" itineraries often just duplicate content that should be in the main destination article. There is nothing that would be placed in the "A Long Weekend in Bangkok" article that should not be in the existing Bangkok articles.
- There are an infinite combination of "personal" itinerary articles, making it difficult for readers to know where to find information. "A Weekend in Sydney" might be a good article, but the same could be said about "An afternoon in Sydney, "Two weeks in Sydney", "A month in Sydney", or even "Another Weekend in Sydney!"
In order to keep itineraries actually useful to travelers, "personal" itineraries are now tagged for merging to the appropriate city or region destination article.
"One year" deletion ruleویرایش
Since just about any topic can be an itinerary, itineraries must either be actively worked on or achieve some level of completion to be kept. (Sufficiently famous, marked routes such as Alaska Highway or Annapurna Circuit are exempt from this rule.) As such, itineraries that have been at outline status or less for one year without being substantially edited are subject to deletion via the votes for deletion process.