text:
Wikivoyage:Dive guide article status criteria

Wikivoyage criteria:

 * Has enough information to be useful for an adventurous diver. That is, by using the information in the article, they can (for example) get to a destination, find some local dive sites and service providers, and have some pointers for what to see or do.
 * In general, usable articles are not really complete articles, however. They may not offer many options for where to dive and get diving services. They may not contain much information about what can be seen at the sites, or what conditions may be expected. This prevents them from being considered true "guide" articles.
 * The format and article structure should reasonably approximate the manual of style. Some relevant sections may be missing or incomplete.

Diver criteria:

 * Must contain a listing of at least one relevant dive site, and where applicable, at least one service provider in the region.
 * Some of the dive sites must be of Usable standard of higher.
 * Information should be provided in most of the headings.
 * Sufficient information should be provided that a competent diver with some local knowledge can use the guide and at least one included dive site sub-article to plan a safe dive at the relevant site. (involvement of a local guide may be required where appropriate)

Wikivoyage criteria:

 * Effectively covers most aspects of the topic with no obvious omissions.
 * If practical, it should contain a listing of relevant destinations.
 * The format should closely match the manual of style.

Diver criteria:

 * Must contain a listing of relevant dive sites.
 * Some of the dive sites must be of Guide standard or higher.
 * Most of the dive sites must be of Usable standard of higher.
 * Information should be provided in most of the headings.
 * Sufficient information should be provided that a competent diver with some local knowledge can use the guide and most included dive site sub-articles to plan a safe dive at the relevant site. (involvement of a local guide may be required where appropriate)

Checklist:

 * All subheadings have useful information ("No special equipment required" is useful information, a blank space is not.)

Star status criteria for regional dive guide
This is a guideline. If you have a better idea, Plunge forward, but try to explain your reasons.

Wikivoyage criteria

 * Covers the topic fully.
 * Layout and listings either match the manual of style exactly or are the exception that proves the rule.
 * Prose is not only near-perfect grammatically but also tight, effective, and enjoyable.
 * At least one good-quality photo or illustration accompanies the article.
 * If practical it has a map identifying relevant destinations.

Diver criteria

 * A diver unfamiliar with the region should be able to decide if it will be to his/her liking, and within his/her competence/skills/fitness to dive in the region at a typical site.
 * The diver should also be able to decide on what personal equipment to bring, and what to rent or buy when visiting the region.
 * The diver should be able to plan for emergencies, both medical and equipment related, and know what support is available in both these fields.
 * Pricing need not be in great detail, but it should be possible to use the guide to contact suppliers of ordinary recreational diving equipment and services most convenient to the region (If such exists - offshore atolls may have no facilities whatsoever. In this case refer to the most appropriate major centre)

Checklist
General
 * Standard template used or other appropriate layout complying with the Wikivoyage style conventions.
 * Correct English usage: Spelling, grammar, consistent with either local English usage or UK or US English conventions.
 * Correct technical terminology understandable by native English speaking recreational divers.
 * All sections of the template contain substantial and useful information unless not applicable to the region, in which case this should be specified.

Section checklist

Leader paragraph
 * Leader paragraph explains what the article is about and who it is for.
 * Basic geographic extent of the region is stated.

Understand

General topography
 * Some information is provided on the physical geography of the region.
 * Extent of the region is clearly defined. (a map or other illustration is sufficient)
 * Major landforms defining the region are mentioned and named and if necessary, explained.
 * Topography of both underwater and land is described. Some form of relief map drawing or illustration should be present.

Climate, weather and sea conditions
 * If applicable, a description of the regional climate, weather systems, oceanogrphy in terms of tides, currents, seasonal water condition variations, max and min values

Marine ecology
 * If applicable, a description of the regional marine/aquatic ecology.

Equipment
 * Special equipment and training required or recommended for diving in the region, both general and sub-region specific.

Respect
 * Explain any special procedures or precautions to avoid ecological or archaeological damage.
 * Any local legislation affecting diving in the region is explained sufficiently to allow a reasonably prudent diver to confidently avoid contravention. Information must be accurate and current.

Get help
 * List of emergency contact phone numbers for the region, and where there is no appropriate emergency service within the region, contact details for the most appropriate services outside the region.
 * These numbers should include where possible: Recompression chamber facilities, Hospital, Clinic or doctor, Diving medical practitioner (specialist), DAN local contact number, Police, Ambulance, Fire department, any specialist rescue organisations that may be of use, Sea rescue/Coastguard.

Get service Learn Buy Rent Do Fix
 * A listing of Dive schools, Dive shops, Air filling facilities, Scuba and cylinder service facilities, Dive charter boats, liveaboards, etc IN the region should be provided. Any known idiosyncracies or specialist abilities (such as affiliated training agency, or foreign languages spoken) should be mentioned.
 * If there is no representative of any specific class of service business in the region, the nearest convenient agency outside the region should be listed, with approximate distance and any other critical information.
 * It is not necessary to list every dive school, shop, charter business, air filling station, or equipment service agent in the region, but at least one reputable representative of each of these classes should be listed with adequate contact information. If dry suits are recommended in the region, a dry-suit repair agent should be listed.
 * List names of dive schools in the region
 * List names of dive shops in the region
 * List names of places that rent dive gear
 * List names of operators, charter boats, liveaboards operating in or from the area.
 * List names of people or organisations which service and repair: Scuba regulators, BCDs, Cylinders, Drysuits.

Details
 * List contact details of places listed in "Learn", "Buy", "Rent", "Do" and "Fix". Use the Other listings insertion template.

Get around
 * Explains how to get around the region to dive sites and launch areas as a diver with dive equipment. Options of private and public transport as available should be discussed.

Stay safe
 * A comprehensive description of regional hazards, the risks connected to them, and appropriate mitigation where applicable.
 * Information should apply to a significant percentage of the sites in the region.
 * Hazards specific to only a few sites should be covered in the dive site sub-articles.

See (Listing of dive sites)

Number of dive sites listed should be appropriate to region size. In general a region should not contain less than one city or other significant destination unit. Sites which would ordinarily be reached on a day excursion from a destination such as a city would be in one dive guide, even if there are a large number of them. Alternatively, unless there is a good reason, such as the conditions are very different from the nearest other sites, it would not be appropriate to have a regional guide for a smaller number of sites than about 5, even if the sites are on different islands or near different cities. A guide should not cross national borders except in special circumstances.

If there are more than 100 local sites in the region, the number of sites may be limited to 100, and/or this number used for the percentage calculations. This condition is intended to prevent an area with large number of dive sites becoming too difficult to get to star level.

(these numbers are only for guidance, if there is a good reason to differ, explain and go by consensus after discussion on the Star nominations page)
 * At least three listed local dive sites must be at star standard (unless there are fewer than three sites in the region, in which case all must be of star standard.
 * At least 90% of locally known named sites should be listed (or 100, whichever is less).
 * At least 50% of the listed sites should be of guide standard or better (or 50, whichever is less).
 * At least 75% of the listed sites should be of usable standard or better. (or 75, whichever is less)
 * All listed sites should at least be described to outline level, unless newly discovered or potential sites, and not yet explored, or up to 5% of listed sites known to be dived, but information is not available.

 * listing of dive sites should normally provide a paragraph describing each site in general terms. No great detail is required. Try to distinguish the site from its neighbours.
 * A star rated region need not be delisted if a few newly discovered sites are added which do not yet meet the criteria.

Wikivoyage criteria

 * Has enough information to be useful for an adventurous diver. That is, by using the information in the article, they can get to the dive site and have some pointers for what to see or do.
 * In general, usable articles are not really complete articles, however. They may not offer many options for what to do on a dive. They may not contain much information about what can be seen at the site, or what conditions may be expected. This prevents them from being considered true "guide" articles.
 * The format and article structure should reasonably approximate the manual of style. Some relevant sections may be missing or incomplete.

Diver criteria:

 * A suitably competent diver with moderate local knowledge should be able to plan a dive using the information provided. (in conjunction with a regional diving guide if applicable.)

Checklist:

 * Template may be present but is not essential. Layout is logical and appropriate.
 * Information on position of the site is sufficient to get there, possibly with the help of a local guide or service provider.
 * Some information on depth and, if applicable, site specific hazards is given.
 * There are no obvious critical omissions.

Wikivoyage criteria:

 * Effectively covers most aspects of the topic with no obvious omissions.
 * If practical, it should contain a listing of relevant destinations. (not relevant to dive site)
 * The format should closely match the manual of style.

Diver criteria:

 * A suitably competent diver with little local knowledge should be able to plan a safe dive using the information provided.(in conjunction with a regional diving guide if applicable.)

Checklist:

 * Template present, all appropriate headings present
 * Style basically correct and complies with Wikivoyage recommendations.
 * A map or aerial photo is present for shore access sites, and displays useful information. A map should comply with the Wikivoyage map style conventions where this does not adversely affect usefulness.
 * For an acceptable style for a dive site map see examples:[[Image:Map_of_the_CT_dive_site_Pinnacle.png|thumb|Example 1]]Star Walls Reef Complex map.png
 * GPS position data or other means of identifying position accurately without local knowledge. This can often be found by using Google Earth. Maps from Google Earth are not acceptable for copyright reasons.
 * All subheadings contain useful information unless the subheading does not apply to the site, in which case it is not shown.
 * At least one photograph of marine organism or feature of the site.
 * The site should be a sub-article of a regional dive guide. (if there are very few sites in the region the sites may be included in the regional guide to a number not exceeding 9).
 * If there are a large number of photos you want to provide with the site, you can put them into a Gallery which is a sub article of the dive site sub-article. An example can be seen at Diving the Cape Peninsula and False Bay/Pinnacle/Gallery
 * For photos which are needed in the text of the article to illustrate specific aspects, but are too many to keep against the right margin, an alternative is to use small galleries within the main text at the appropriate place. This looks neater than an overlong column at the right. This is acceptable practice as it has been used in Star articles such as Singapore.

Wikivoyage criteria:

 * Covers the topic fully.
 * Layout and listings either match the manual of style exactly or are the exception that proves the rule.
 * Prose is not only near-perfect grammatically but also tight, effective, and enjoyable.
 * At least one good-quality photo or illustration accompanies the article.
 * If practical it has a map identifying relevant destinations.

Diver criteria:

 * A diver competent to dive the site but without any local knowledge should be able to plan a safe and enjoyable dive using the information provided (in conjunction with a regional diving guide if applicable.)
 * Conditions during the dive should come as no surprise.

Checklist:
Leader paragraph
 * The site is named
 * Type of site specified
 * Geographical location given in general terms
 * Nearest major landmark, near
 * Nearest City in
 * Region in
 * Country.

Understand (content in understand section should be relevant to all drop points)
 * A map showing the position and layout of the site in some detail, preferably to scale.
 * Reason/s why one would choose to dive the site.

Position
 * GPS position for the site. Should put a diver at least somewhere on the site, specify where if possible
 * Alternative range and bearing or cross bearings to well defined and reasonably close landmarks. Photos of landmarks desirable.
 * distance from launch site or harbour for boat access (km or N.miles). Distance should be along the usual route, not as the crow flies.

Name
 * Optional image of whatever the site is named after. (particularly desirable for wreck sites, where a photo or painting of the vessel or a similar vessel is preferred.)
 * Explanation of origin of the site name, translation if applicable.

Depth
 * Maximum depth to be expected on the site
 * If applicable, shallowest point of the site
 * Average depth of a dive can be added if it will be useful.

Visibility
 * Range of visibility to be expected when conditions are generally considered suitable for diving.

Topography
 * Description of the layout of the site
 * General idea of slope, profile and rugosity
 * Description of major features and landmarks
 * Condition of wreckage if applicable

Geology
 * Only for rocky reefs
 * Type of rock, (geological age, name of formation optional)
 * Strike and dip optional if applicable

Conditions
 * What weather conditions will result in good diving conditions.
 * Any specific weather conditions which will result in unpleasant or hazardous diving conditions.
 * Any special oceanographic or weather conditions the site is known for. (sudden offshore winds, upwellings, currents, plankton blooms, thermoclines etc) if applicable
 * Information sufficient to allow a reasonably competent diver with a moderate understanding of the local weather and climate to forecast conditions during a planned dive over a short period (3 to 4 hours) when on site.

Facilities
 * Generally only for shore access dives
 * Facilities must be in close walking range of parking area or entry points
 * Facilities appropriate to divers and accompanying family only.(parking, ablution, fast food, dive services, picnic areas, security, beach, shade, etc)

Get in

Shore entry Boat entry
 * Adequate directions to reach the site
 * A map or aerial photo indicating the position of entry/exit areas (only for shore entry ) if the main site map is not sufficient.
 * Sufficient text for a person who has no local knowledge at all to find the site and identify any access areas with confidence.
 * Photos of the standard entry and exit points if applicable.
 * Location of slipway/harbour/launch site/pickup area.
 * Distance of boat ride and/or duration of boat ride.

Do (new section for sites with more than one drop point)

Paragraph describing the area served by the drop point in whatever detail seems useful to a diver and is available.
 * Optional section intro
 * Optional sub-region title
 * Listing for each drop point using bulleted list of format: : Hdd°mm.mmm' Hdd°mm.mmm'. (or other locally popular format)

Suggested Routes (Routes should be listed here if there is a "Do" section)
 * generally at least one suggested or recommended route, with an indication of what the diver may expect to see. This may be a drift dive if applicable. "Follow the divemaster" is not really a route and will only be accepted if there are really good reasons, which are adequately explained.
 * Some indication should be given of how long a dive on the route will take, and if it is a long route, an approximate distance. This is not essential if it is shown to scale on a map.

See

Marine life and/or Features
 * Photos of at least three organisms or features one may reasonably expect to see at the site
 * Photos of organisms that are special in some way may be included even if not frequently seen, but it should not be suggested that a visitor is likely to see them
 * Description of what a diver may see during a dive
 * if the photos were not taken at the site this should be mentioned.

Photography
 * advice on photographic equipment (macro/wide angle, need for external lighting) if appropriate.
 * photographic opportunities that may be expected or hoped for if applicable.

Suggested Routes (Routes should be listed here if there is no "Do" section)
 * generally at least one suggested or recommended route, with an indication of what the diver may expect to see. This may be a drift dive if applicable. "Follow the divemaster" is not really a route and will only be accepted if there are really good reasons, which are adequately explained.
 * Some indication should be given of how long a dive on the route will take, and if it is a long route, an approximate distance. This is not essential if it is shown to scale on a map.

Stay safe

Hazards
 * Site specific hazards of any kind, including access hazards if applicable. "No site specific hazards known" is null default, and implies that the local hazards are adequately described in the regional article.
 * Comprehensive listing of site related hazards (not regional hazards already in regional guide, ordinary diving hazards nor obvious sea/weather condition hazards). Advice on mitigation is optional.
 * security problems and land based hazards may also be mentioned if applicable. (theft/mugging risk, animals stealing food etc)

Skills
 * Skills, competence or certification level required for diving at the site, if any.
 * Skills recommended for diving at the site, if any.
 * "No special skills required/recommended" is null default, this implies that a person trained to dive in the region will be able to handle the normal conditions for diving at the site.

Equipment
 * any equipment beyond the standard equipment listed for the region in the regional guide, either reqired or recommended for the site for safety of convenience. Reason should be specified if not obvious.
 * "No special equipment required/recommended" is null default, and implies that divers trained to dive in the region, or who have some experience diving in the region will know what is needed.


text:
Wikivoyage:Docents

Wikivoyagers have knowledge about our destinations that sometimes goes beyond what can be included in a guide. Often, visitors to Wikivoyage have a very specific question that is not answered by our usual guide format. To connect these folks, it would be great to make an explicit connection between some articles and contributors.

Docents for a particular destination are listed in the left-hand navigation area on the destination's page, between "In other projects" and "In other languages".

If you are curious which destinations currently have docents, here is a current list.

Becoming a docent
To become a docent for a destination, add the following template to the end of an article: Replace "Username" with your actual user name. If you have a divided user name, like John Smith, you need to put an underscore instead of a space: John_Smith instead of John Smith.

If there is already a docent listed, add your name on the next line:

At your user page, indicate how you would like to be contacted: on your talk page, via email, IM, IRC, etc. Link back to this page so people can understand the idea better.

Currently, there is no limit on the number of docents for a destination, but attempts should be made to keep the total number of docents under 3–5 depending on the size of the destination.

Stopping being a docent
If you decide you no longer want to be a docent, or you plan on being away for more than a week or two, just remove your username. If you aren't going to visit Wikivoyage frequently, but are still available to help, leave a note on your user talk page asking people to reach you by email.

If a docent has been unreachable for one week, without making note of their absence, their name can be removed from the docent list.

Nominating a docent
If you notice a user who seems to have a lot of good insider knowledge about a destination and you think they would be a great docent, put a comment on their talk page:

 * You sure seem to know a lot about insert place name here, have you considered becoming a Docent? --~

Rights and responsibilities

 * Docents should create a Docent section on their user page. In that area they can indicate how they would like to be contacted: on their talk page, via email, IM, IRC, etc. Link back to this page to help people better understand the whole idea.
 * Docents should try to integrate information back into the guide.
 * Docents are not "in charge" of an article. They have the same control over article content as any contributor. Issues should still be settled on the appropriate talk pages.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Wikivoyage:Docents


text:
Wikivoyage:Don't tout

In many countries business owners hire touts to solicit customers. Touts go to train stations, airports, or open plazas and urge travelers to visit their employers' business.

Wikivoyage specifically strives to avoid being an "advertising brochure" for any business, city, or service. Business employees, like everyone, are welcome to add information to Wikivoyage, but we're making a travel guide, not a business brochure, so Wikivoyage should not be used as a tool for advertising. Marketers and chain employees should not add listings directly – they are welcome to correct phone numbers and similar, but should suggest other changes on the talk page of the relevant article.

Identifying touting
Edits might be reverted as touting if any of the following guidelines aren't followed:

 * Don't list the same place many times. Yes, a guesthouse may have a restaurant, a bar, an Internet café and a dance show, but you need to pick one of "See", "Eat", "Drink", "Sleep" or "Connect" to slot it under.  That said, exceptions can be made on a case-by-case basis if, for example, a hotel has a famous, separately named bar or restaurant that also draws significant numbers of non-resident customers (use the article's talk page to discuss these rare instances).  Also note that businesses should be listed in only one article for the town or district in which the business operates; if an article about the town has not yet been created, create it.

 * Avoid first person pronouns. Never say our restaurant, or we provide.

 * Don't add listings for booking services or general travel planning. Wikivoyage has fairly strict criteria on what tour company listings are allowed in articles, and these criteria disallow listings for most travel agencies or tour resellers.
 * Don't add more than one URL for a place, neither on one page nor on different pages. There is never a reason to do so, and will mark your contributions as advertising spam in the eyes of other editors.

 * Describe, don't urge. Use the indicative mood to describe ("The food at Restaurant X is freshly prepared when ordered."), rather than the imperative mood for commanding ("Come to Restaurant X and sample its delicious fare straight from the oven!").

 * Don’t write in all-caps. On the internet writing in all capital letters is considered shouting and is highly discouraged.

 * Avoid using flowery, vague terms in descriptions, instead describe why it is so great. "This stunningly wonderful hotel is fabulously luxurious!" is meaningless; "More staff than guests, three heated swimming pools, and each room has a jacuzzi, a bearskin rug in front of the fireplace and panoramic windows with views of the Mighty Mountains" tells much more. "Good music, terrific staff and a great atmosphere" could apply to any bar; "Dark, smoky den crowded with local hipsters, with knowledgeable bartenders and live jazz on Fridays" gives some idea of what to expect.

 * Avoid superlatives (the best, the biggest, the tastiest, the most fascinating) unless they are objectively true and of specific interest to the traveler.

 * Don't move your listing to the top. In most cases listings should be ordered alphabetically within a section.  Moving a listing to the top of the list for any reason other than alphabetization is considered touting.

 * Be concise. One sentence to one paragraph of factual information is reasonable, an entire section (or subsection) of an article devoted to singing the praises of one random hotel or restaurant is not - especially if much of the listing is fluff (...it's great to enjoy leisurely, sunny summer afternoons here!) or the owner's opinion of their own product.

 * Avoid assertions of proximity to nearby attractions. The description section of a listing is for describing that listing, not the rest of the town (...conveniently located near <insert name of every major tourist attraction within the city>). If it's attached to the convention center or right on the pier then note that using the "directions" field of the listing template, but otherwise save descriptions of the area's attractions for the "See" section. Instead, contribute detailed lat-long coordinates of the property (see Wikivoyage:Geocoding)—it will be much more helpful for a traveler choosing a place to stay.

 * Avoid references to third-party ratings and rankings unless they are truly exceptional. For example, "Lonely Planet approved" should be avoided since there are thousands of businesses that are "Lonely Planet approved", but "rated the #2 hotel in the Middle East by Generic Travel Magazine in 2010" might be worth mentioning. Listings that include such references but provide no mention of why the business is highly rated offer little value to travelers; a long list of accolades is no substitute for actually describing the establishment.

 * Don't include referral codes in URLs. Some businesses use referral codes to track where traffic to their web site is coming from (example: http://example.com/site.html?from=wikivoyage).  Referral codes don't benefit travelers and will lead to removal of the listing.

Guidelines for business owners
If you own a business or work for a marketing company you should expect that your edits will come under more scrutiny than those contributed by travellers. As noted previously, business employees, like everyone, are welcome to add information to Wikivoyage, but anything seen as advertising is likely to be removed. Additionally, because the goals of creating a travel guide often differ from those of hotel chains, tourism boards, and other business entities, contributors should be aware that there are no guarantees that even properly-formatted listings will always be kept in Wikivoyage guides. To make a contribution that is less likely to be removed:

 * Follow all of the guidelines above to avoid having your contribution identified as touting.

 * Create a user account and identify yourself as the owner of the business on your user page (but don't advertise the business there). Doing so adds some transparency by clearly identifying you as a business owner, and also gives voyagers a way to contact you with questions.

 * Never remove competitors' listings from articles or edit them negatively. If there is a problem with a listing it can always be edited for accuracy, and if an establishment is truly vile it can be removed after being discussed on the article's talk page.  Removing the listings of competing businesses without discussion is strongly frowned upon.

 * Never remove negative comments left by others about your establishment. If you think the comments are unfair, say so on the Talk page and let the community reach a conclusion.

 * Include exact prices. We know you hate to do this, but listings without pricing information may be deleted. While it's best to avoid false precision (as the item you're promoting as "only €99.99" is indeed going to set the traveller back "about €100"), vague terms like "reasonable" or "affordable" are worse than useless.  If prices vary, provide a price range (example: "$100-$200, varies by season").

 * Do not edit war. If your listing is removed look at the article history or, if a message notification pops up on your screen, look at your user talk page to see why it was removed. Discuss it on the talk page for that article.  Repeatedly re-adding a removed listing without first discussing why it was removed makes it more likely that editors will see your contributions as advertising, and less likely that your listing will be allowed.

Guidelines for destination marketing organisations
Tourist bureaux are in a unique position as their extensive, up-to-date knowledge of individual destinations could greatly improve Wikivoyage. Unlike an individual business, a convention and visitor bureau is likely to make wholesale changes to a page which affect not one or a handful of listings but entire articles and destinations. This may produce a good article, this may produce an entire destination page which looks like a misplaced advertisement or reflects poorly on the host community.

 * Don't copy-paste verbatim from your existing brochures. Try to match the style of existing articles: informational, not promotional. We're looking for original content which puts the voyager first, and we need to be able to share that content freely without restrictive copyrights. Word this like a travel guide, not like a sales pitch.
 * Explain your changes. In one common pitfall, a new user removes outdated or erroneous information (for instance, deleting half a dozen restaurants from one city), only to have the next editor put everything back because they have no idea why content was removed. If a venue is closed or no longer in business, say so. If something in the article is factually wrong, say so. If someone undoes your contributions, discuss this on the talk page before being drawn into an edit war.
 * Lose the promotional tone. Many common clichés are best avoided as they're vague ("just steps away!") or read more like an advertisement than a fair and factual description.
 * Don't try to list absolutely every venue in the city. Your own local brochures may be a directory of every food or lodging business in town (or every member of your chamber of commerce), but we just want a few good options in each category. If a venue has seen better days or is not worth a visit, simply leave it out.
 * Include a complete description for the venues you do choose to list. At least, include the location, contact info, prices, a paragraph or so explaining what's special about this place. A list of every hotel in town with names, but no descriptions, tells the voyager little. A select few good options, with a full description and a pin on a locator map for each, is far more useful to the traveller.
 * Show us what's unique about your town or destination. Don't waste extensive time and effort describing individual franchise locations if every restaurant or café in an entire national chain serves exactly the same fare the same way... at least not if there are local independents which are offering the traveller something memorable or unique which deserves a local listing.
 * Don't list points of interest which belong in some other article. There's a great museum or a big shopping mall two towns away? Odds are, it's already listed in the article for that community - and, if it's missing, add it there instead of trying to turn it into a selling point for your own town. Save the "see" and "do" sections for unique or interesting things to see or do in your city, town or rural area; any links to the next town with an article can go in the "go next" section.

Marketers and SEOs

 * Note: Wikivoyage implements  so there is no SEO benefit to listing a website here.

Because there is an inherent conflict of interest when someone is being paid for their edits, if you are working for a hotel chain, a marketing agency, or a similar organization then you may not add listings for that business to Wikivoyage articles. Wikivoyage is not a yellow pages, so adding every individual location for a hotel brand or restaurant chain is not an appropriate use of this site. If a hotel is truly exceptional, or if a city has a very limited number of lodging options available, you may propose a listing to be added by suggesting it on the article's talk page, but do not add the listing yourself. Marketers that add multiple business listings should expect to see their contributions reverted, and in the worst case repeated violations of this policy may lead to blocking of the contributor's account and possibly blacklisting of the business in question.

Marketers and paid editors may make factual corrections to existing hotel listings, but these changes should be strictly limited to non-subjective information such as URLs or phone numbers. As explained above, do not remove negative information from a listing without first discussing the change; if a listing states that a hotel has a dated interior but the property has undergone recent renovation, point out this fact on the article's talk page and let someone else update the listing.

Examples
Good. The following is an example of a good business listing. It is properly formatted according to our manual of style, includes an estimated price range for a standard double room, and has a description that provides useful, factual information for a traveller:

Bad. This listing is for the same hotel, but the address is improperly formatted, there is no contact information, no price range, and the description is pure marketing fluff:

Edits inserting such listings are routinely reverted, and if repeatedly added, the listing may be blacklisted.

title: Wikivoyage:Don't tout


text:
Wikivoyage:Dual licensing

To enable collaboration between contributors, and to keep their contributions free for everyone to use, Wikivoyage content is released under a copyleft license called the Creative Commons Attribution-ShareAlike 3.0 License (sometimes called the by-sa license). Another, similar license, the GNU Free Documentation License (or GFDL), is used by other Free Content wikis to keep their content Free. Wikivoyage doesn't use the GFDL; see Why Wikivoyage isn't GFDL for details.

Some contributors may wish to release their contributions under another license (as well as the by-sa) such as the GFDL, in order to make their work accessible for these other sites (or for other reasons). This is called dual licensing. This page describes how to dual-license your work for Wikivoyage, as well as what the pitfalls of dual licensing can be. It's provided here as a service for those Wikivoyagers who insist on dual-licensing their work, and a clarification for other Wikivoyagers who have to edit and modify that work.

NOTE: The contributors to this article are either a) not lawyers or b) not giving you legal advice. If you need legal advice on this issue, please contact a lawyer familiar with Free Content licensing issues.

Advantages of dual licensing

 * You may have other personal reasons to be attached to the GFDL or other licenses.
 * Dual licensing allows material to be shared between projects, that use different incompatible licenses. The creater of the original version can submit his work under different licenses to different projects. But for updates to flow between the different projects, dual licensing is necessary.

Limitations of dual licensing
The major problem with dual licensing is that it's confusing for readers, re-distributors, and other contributors. It makes them go read pages like this one to figure out what their rights and responsibilities are. Because it's confusing, it keeps us from working together on articles -- which is one of the main reasons we use a copyleft license in the first place!

Mechanics of dual licensing
The following describes the mechanics of dual licensing. It refers to the GFDL specifically, but much of the discussion would apply to any other license.

 * 1) It is possible for the original creator of a Work (that is, a Wikivoyage article, image, or other media object) to release that work under the by-sa license as well as another license such as the GFDL.
 * 2) A contributor making a Derived Work (editing or adding to the article, resizing or fixing up an image, etc.) must choose one of the licenses or both -- either the GFDL, the by-sa, or both. Because of limitations in our software, if that contributor chooses to use only the GFDL to create a derived work, it can't be uploaded to Wikivoyage. (We don't have a way to separate out content that's not available under the by-sa license. If we need it, we might add that "feature", but we don't have it yet.) So, if a contributor edits and saves an article in Wikivoyage, it is explicitly licensed under by-sa only, unless otherwise specified.
 * 3) Once a Work has been edited by another contributor who doesn't want to dual-license it, it is under the by-sa license only. Nobody -- not even the original Creator -- can create a derived work from it that is dual-licensed.

The upshot: work can be dual-licensed in Wikivoyage only if one person has worked on the article or image, and if all subsequent contributors have also chosen to dual-license it.

How to dual-license your original contributions to Wikivoyage
First, remember that dual-licensing is your choice as a contributor. You cannot expect other collaborators to keep an article or image dual-licensed.

If you have an article in Wikivoyage that is your original work, and that no one else has worked on, you can dual license it. Simply add the following text to the talk page for the article or images:

 * All content on Wikivoyage is available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license. The author of this content has also granted you permission to use the content under a different license (see Project:dual licensing for details), if you so choose.

 * Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. See the Project:full text of the GNU Free Documentation License, Version 1.2 for details.

Once another contributor edits the article without explicitly dual-licensing the update, its latest version is (as mentioned above) no longer available under the GFDL. If you wish, you can make a link on the Talk: page pointing to the last GFDL'd version. This is your responsibility.

How to dual-license existing guides
You can't dual-license a guide that's already been edited by other people who didn't dual-license it. But if it's already been dual-licensed under the GFDL and by-sa 3.0, you can dual-license it under those two licenses. (It's not clear that you can dual-license it under other pairs of licenses, though.)

If you agree to keep a work dual-licensed, add a note on the talk page to that effect. If you don't, other editors can and should assume that you'd don't agree to the dual license, and will remove the dual-licensing statement.

Editing a dual-licensed article
If you edit an article or image that's dual-licensed, then please change the above license statement on the Talk: page to specify that only the older version(s) are dual-licensed. You can replace the license statement as so:

 * All content on Wikivoyage is available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license. Older versions of this document were also available under the GNU Free Documentation License, Version 1.2 (GFDL). The most recent version available under the GFDL is here. See Project:dual licensing for details.

This is a courtesy to the original author, who wished to distribute his/her work under a dual license. Alternately, you can simply delete the dual-licensing statement.

Dual licensing of Images and other media
The rules are the same for images and text. However images are usually not edited by multiple authors and the current Wikivoyage software does not handle updating of images well.

If you want to dual-license images or other media so that they can be used with other projects, consider uploading a copy to commons.wikimedia.org and put the relevant licenses in the "Summary" field using mediaWiki codes. For example:

Make a link to the MediaWiki "original".

title: Wikivoyage:Dual licensing


text:
Wikivoyage:Dutch Wikivoyage Expedition

This page intends to organize efforts to make a Dutch version of Wikivoyage. Until the version is created, all discussions should be in English, so others Wikivoyagers may join the discussion.

Rationale
Dutch (Nederlands) is a Germanic language mainly spoken in 3 countries, the Netherlands, Belgium and Surinam. With about 22 million native speakers it is a major language in the European Union.

Objectives
Attention should be spent on using general dutch (AN) and not Netherlands-dutch words or Belgian-dutch words.
 * Make a travel guide for Dutch speakers.

Name
Why not translate also the name.

 * because that would require a dedicated server
 * to reinforce and join forces in the brand wikivoyage
 * wikireizen?

Goal
See the Language version policy for see what it takes to start our own Wikivoyage.

Gather a minimum team
Members who would gladly like to contribute:
 * (WT-en) Guaka
 * (WT-en) Domie
 * (WT-en) Leviathan
 * (WT-en) Orange
 * (WT-en) Willem 11:22, 28 Jun 2005 (EDT)
 * (WT-en) Twopeak (but I'm not *that* active)

Next Steps
The interface localization file has to be translated (or modified from the one on Wikipedia), checked for correctness, and then we will vote for a go-between.

LanguageNl.php is for creating this collaboratively. It's started with the Wikipedia language interface file, but it needs to be changed to match Wikivoyage.

For comparison, the English file is at Project:LanguageEn.php. Major things to watch for:

 * Replacing "Wikipedia" with "Wikivoyage"
 * Differences in license policy (GFDL versus CC by-sa)

Hier is de versie: nl:Project:LanguageNl.php Nog aan te passen (dit wegdoen als de file compleet is)...

 * Hopefully correctly done this now. Let's get this thing started..! (WT-en) Guaka 15:53, 15 Dec 2005 (EST)

Go-between
We need one more step -- a go-between. Some language versions have just had someone come forward to do it; others have voted. It's up to the group here.

 * (WT-en) Guaka - If noone else wants to take this responsibility and noone has objections I am happy to be "go-between". 18:18, 15 Dec 2005 (EST)
 * Support. (WT-en) Jpatokal 22:08, 15 Dec 2005 (EST)
 * Me too. --(WT-en) Evan 13:04, 16 Dec 2005 (EST)

Translate those pages

 * Project:about to nl:Project:Wikivoyage
 * Project:FAQ to nl:Project:FAQ
 * Copyleft to nl:Project:Copyleft
 * Main Page to nl:Project:Hoofdpagina
 * Project:help to nl:Project:Help
 * Project:policies and guidelines to nl:Project:Richtlijnen
 * Project:manual of style to nl:Project:Stijlhandboek
 * Project:welcome, newcomers to nl:Project:Welkom Wiiihaaa, i finished this page, it awaits a few corrections

title: Wikivoyage:Dutch Wikivoyage Expedition


text:
Wikivoyage:Edit war

An edit war is when two or more contributors to an article on Wikivoyage continuously edit and re-edit the article to get across their point of view. For example, contributor A writes:

 * The best goth club in Toronto is the Nyghte Shayde Tavyrne.

Contributor B changes the article to:

 * The best goth club in Toronto is the Dimme Lyghte Tempyle.

Contributor A changes this back to NST. Contributor B changes it to DLT again. And so on, and so on, and so on. It's the wiki equivalent of two children shouting in each other's face: "Am not!" "Are too! "Am not!" "Are too!"

Edit wars are normally pretty bad things. They usually cause needless conflict and detract the attention of a lot of people from the task we have at hand. However, sometimes these conflicts are needed; sometimes we need to figure out an important issue of policy, of style, of whatever, and the edit war triggers that discussion.

What to do
If you get caught up in an edit war, here's what you need to do:

 * Step back for a second. No one is going to die because people don't really know the best goth club in Toronto for 12 or 24 hours. Bookmark the page, and come back to it later.
 * Use the talk page for the article to come to a consensus. This is what talk pages are for. Explain your position, and explain why you made the change. Say that you're trying to find a way out of the edit war.
 * Check your baggage. Are you remembering that the traveller comes first? How much of your editorial fervor really has to do with being fair, and how much has to do with some outside, non-travel issue?
 * Consider a neutral compromise. For the above problem, do we really need to say which goth club is really the "best"? Can't we just add listings for both goth clubs?
 * If you think there's a bigger question at hand, bring it up on the travellers' pub. Try to start a discussion about the bigger issue with all the community involved, rather than just those interested in goth clubs in Toronto.
 * Let the baby have their way. It is not your job in life to teach the other person in an edit war that they can't get away with their horrible actions. Just let them. If you don't think that there's a very serious problem with their version, just leave it. Trust that someone else will agree with you, and fix it themselves.

Severe edit wars
Note that we believe that Wiki works, and that an open page is the best policy. Any time two or more people can't work out their differences on talk pages, in public forums like the Travellers' pub, or between themselves, we've failed. An important part of what makes Wikivoyage powerful is that we believe in working things out directly, and not a lot of hierarchical nonsense.

However, that said, if an edit war has become severe, and discussion on talk pages isn't working, and the importance of the issue is worth undermining our principles of openness, then one of the administrators can declare a cooling-off period, protect the page in question so no other edits can take place, and demand that the interested parties come to consensus on a talk page.

We have very few protected pages on Wikivoyage, and this is a point of pride. When a protection happens it will make the next time more likely, and the third time after that. We'll get in a situation where people expect administrators to be the Big Boss and come in and tell everyone what to do. We don't want that. Let's avoid it.

You can contact an administrator to ask them to protect a page, but that doesn't mean they're going to do it. Make sure that all other means of solving the problem have been exhausted, and that a sufficient amount of time has passed that shows it won't be resolved without intervention. Remember that nobody likes a tattletale; you should be pretty darn sure that your problem is worth a cooling-off period.

Armistice
During the cooling-off period, the combatants should work out a new consensus version of the article on the article's talk page, such as Talk:Toronto. Once they've come to consensus, an admin will unprotect the page.

title: Wikivoyage:Edit war


text:
Wikivoyage:Education Expedition

The Education Expedition is a project to help educators use Wikivoyage as a teaching tool.

Rationale
Creating Wikivoyage content can be an extremely useful and satisfying project for students -- both adults and teens. Contributing to Wikivoyage exercises students' language and writing skills, photography and illustration, knowledge of history, geography, and business, as well as less traditional skills like collaboration and community development. Students also get the satisfaction of knowing that their work will be a real reference for others for years to come.

From Wikivoyage's perspective, we benefit from the work and local knowledge that students can provide. In addition, some students may catch the wiki bug and continue to contribute after their assignment is complete. Finally, students of English as a foreign language can provide valuable translation services between language versions.

Goals

 * Create best practices for educators
 * Create community guidance for interacting with classes and groups of students

Best practices for educators
These are some proposed ideas for educators; maybe they can be incorporated into a Project:Welcome, teachers and/or Project:Welcome, students.

 * Have definite tasks
 * Plan ahead
 * Introduce the site in the classroom or with guided navigation
 * Have all students sign in as users, so you can track their contributions
 * Have students organized in a group in some way (How can we do this? A Group: namespace?)
 * Describe your lesson plan on the site (How and where?); any instructions you have for your students can stay on the site
 * Have users describe themselves on their user page
 * Concentrate on stuff we need for Wikivoyage (see Project:Help wanted)
 * Factor communication, collaboration and community into your lesson plan
 * Use page history to grade user contributions; don't expect pages to stay untouched while you're grading!

Community practice
Some things we may want to do to help out students:

 * Treat students and teachers with the same respect we'd give to any new contributors
 * Encourage students and teachers to use best practices; point them to the appropriate pages
 * Highlight good ideas for class projects (How? Where?)
 * Create spaces for teacher/student interaction (How? Where?)

For English as a Second/Foreign Language Learners and Teachers
Wikivoyage can provide students with the opportunity to write about their hometowns and the attractions. Local input is always wanted. However, there are a number of caveats to keep in mind:

 * Wikivoyage is not a place to get free English editing advice.
 * All students (as well as the teacher) should create a user page so that they have their own space. However, do not use the user page as a personal web page
 * Ideally, if Wikivoyage is used in ESL classes, a native speaker (or a fluent non-native) teacher should take responsibility to make sure that the student created pages adhere to the Wikivoyage guidelines and the style manual and follow community guidelines
 * Because editing takes place quickly (sometimes within minutes!) it may be better if students can first create their contributions off of the main pages, utilizing talk pages or their user page as places to create their drafts
 * Have your class/students look at other pages to get an idea of what depth of information is considered appropriate. Consider printing up an example so that students can refer to it while they are using their computers
 * If you ask students to work outside of class, put the pages that they are working on your watchlist
 * Oftentimes, student computer skills, especially when working in a non-native language, may not be what you expect, so printing out the wiki markup page and stepping students through it may be required
 * Be on the lookout for students utilizing copyrighted works
 * Do not use Wikivoyage as a project that starts from zero with each new term. While it is possible to simply delete a page and start over, the principle of Wikivoyage is that it is the culmulative collection of information
 * The goal is for each section of an article to have 5-10 entries, so don't overload sections with entries
 * Get the students to put themselves in the place of a traveller. What information would a traveller like to know?
 * If the idea of creating an article from scratch is too daunting, or if something is already there, consider these suggestions to help Wikivoyage

title: Wikivoyage:Education Expedition


text: Wikivoyage:Esperanto Wikivoyage Expedition


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Kvartalogvidila skemo

Moved to .


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Landogvidila skemo

Moved to .


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Regionogvidila skemo

Moved to .


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Urbegogvidila skemo

Moved to


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Urbetogvidila skemo

Moved to


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Urbogvidila skemo

Moved to


text:
Wikivoyage:Esperanto Wikivoyage Expedition/Vocabulary

Moved to .


text:
Wikivoyage:Esperanto Wikivoyage Expedition/welcome

Bonvenon al Wikivoyage! Ni, Wikivoyagers, kiuj faris ĝin, esperas, ke al vi plaĉos kion vi vidas kaj ke vi aliĝos al ni, farante liberan, renovigatan, kompletan kaj korektan tutteran gvidilon por vojaĝantoj.

Serĉo de informo
Por trovi informon, kiun vi serĉas iru al Ĉxefpaĝo kaj trarigardu kategoriojn, listitajn tie. Celata gvidilo troveblas en sekcio de kontinento, en kiu ĝi lokiĝas. Ekzemple, se vi provas trovi Kairon, provu rigardi en Afriko; se vi serĉas Vankuveron, vidu en Norda Ameriko.

Ankaŭ haveblas sekcioj por marŝrutoj kaj vojaĝaj sekretoj.

Vi povas serĉi en Wikivoyage uzante Serĉo-kampon sur via ekrano. Simple entajpu nomon de loko, site, topic, food, beverage, idea or equipment kiujn vi serĉas kaj vi ricevos liston de artikoloj, kiuj mencias tiun lokon, site, topic, food, ktp. Se estas neniu paĝo, menciata ĝin, tio signifas, ke ni bezonas novan artikolon pri ĝi... kaj vi eble estos unua, kiu verkos ĝin!

Se vi havas specifajn demandojn, vi povas meti ilin al diskutpaĝo, aŭ vi povas demandi docenton por persona helpo. Kun ĝeneralaj demandoj skribu mesaĝon al nia Travellers' pub.

Vi povas uzi artikolojn el Wikivoyage preskaŭ ĉiumaniere, dank' al nia kopilefta licenzo.

Disvastigu viajn sciojn
Tio estas retejo kreata-de-legantoj; ĉiu informo, kiujn vi vidas en Wikivoyage estas kontribuo de Interet-uzantoj samkiel vi. Ni provas krei, ilustrigi kaj redakti vojaĝan gvidilon por tuta mondo, kaj ni bezonas vian helpon.

Tio estas grandega laboro. Kiel oni diras "Many hands make light work;" ĉio per kiu vi povas kontribui estas alte taksata. Vi ne devas esti "eksperto" en vojaĝado; por starti sufiĉas via intereso.

Vi ĉiam estas bonvenata por daŭri plu kaj fari ŝanĝojn de ajna paĝo en la retejo (inkluzive tiun ĉi). Simple musklaku ligilon Redakti paĝon, kaj vi ricevos formon, per kiu vi povos ŝanĝi enhavon de la paĝo. Musklaku Konservi, kaj via versio montriĝos en la retejo. (Se vi estas timema, bonvolu eksperimenti en grafiti-muro).

Se vi ekinteresiĝos, vi eble deziros legi niajn sekretojn por novaj kunlaborantoj. Nia listo de  avantaĝoj kaj malavantaĝoj donas bonajn ideojn pri tio, kion ni provas fari kun Wikivoyage. Se vi havas iun specifan informon por publikado, ni verkis kelkajn konsilojn pri tio kien vi povas meti ĝin (pun intended). Vi povas ankaŭ legi nian manlibron pri stilo por studi kiel aranĝi gvidilon. Okaze se vi ne volas sekvi tiun manlibron, estu originala.

Ekzistas ankaŭ aliaj manieroj helpi al Wikivoyage. Ni havas multe da taskoj farindaj. Kaj se vi havas specialajn scipovojn aŭ interesoj, aliĝu al konformaj Ekspedicioj.

Pli da informoj
We have quite a bit of help documentation to make reading and editing Wikivoyage as easy as we can.

If you have any questions about Wikivoyage, please read our FAQ first to see if it's already answered. If not, feel free to ask your question in the travellers' pub, where friendly Wikivoyagers will help guide your way.

We can't say how important it is to us that you are reading and contributing on Wikivoyage. If you need anything, just ask us (however you can). We want you to enjoy Wikivoyage, to find the info you need, and (we hope) to be inspired to share your knowledge with others.

See also: Welcome, Wikipedians


text:
Wikivoyage:Expeditions

A Wikivoyage Expedition is a special project for Wikivoyage articles or images. (Sure, we could call them "projects", but what fun is that?) Expeditions help Wikivoyagers collaborate and organize around certain subjects, be they based on shared interests, geography, or shared skills.

General expeditions

 * Airport Expedition — exploring how to best cover airport information on Wikivoyage
 * Banner Expedition — exploring how to use page banners on Wikivoyage
 * Climate Expedition — figuring out how to present useful climate information in articles
 * District Expedition — improving coverage of city districts
 * Dynamic maps Expedition — collaborating on tools to generate maps dynamically, especially interactive maps
 * Lede Paragraphs Expedition — improving lede paragraphs of articles
 * LGBT Expedition — improving coverage related to LGBT travel
 * Mapmaking Expedition — determining map file formats and mapmaking collaboration techniques, and discussing other issues for cartography
 * National Parks Expedition — improving global coverage of park articles
 * Offline reader Expedition — seeking ways to download articles to a portable computer or PDA
 * Rail Expedition — improving Wikivoyage's rail travel coverage, suceeding Rail travel Expedition
 * Regions map Expedition — promoting the use and creation of regions maps, especially where they are needed most
 * Rewriting Expedition — rewriting articles that previously had content similar to that of other sites
 * Stay safe expedition – into keeping warnings up to date
 * UX Expedition — User Experience improvements
 * World Heritage Expedition — updating and completing the UNESCO World Heritage Site list

Geographic expeditions

 * Africa Expedition
 * Albania Expedition
 * Australia Expedition
 * Brazil Expedition
 * Canada Expedition
 * Germany Expedition
 * Hungary Expedition
 * India Expedition
 * Kosovo Expedition
 * Nigeria Expedition
 * Nordic countries Expedition
 * Portugal Expedition
 * UK
 * England Expedition
 * Scotland Expedition
 * Wales Expedition
 * US
 * California Expedition
 * Massachusetts Expedition
 * Ohio Expedition

Starting a new Expedition
If you have a good idea for a new Expedition, here are the steps necessary to organize it.

 * 1) Make sure that the Expedition complies with Wikivoyage's goals. Will the Expedition help us reach our mission of creating a free, complete, up-to-date and reliable world-wide travel guide? Or is it a slippery slope into non-travel-oriented distraction?
 * 2) Propose the Expedition in the travellers' pub and get some feedback from other Wikivoyagers.
 * 3) Create a page in the Wikivoyage namespace called "Name of expedition Expedition" (note capitalization). On that page, give a rationale for why the Expedition is needed, and define the concrete goals of the Expedition.
 * 4) If additional pages are needed for the Expedition — for example, template pages — link to them from the Expedition page.

Archived expeditions
The following are previous expeditions that have been deemed not useful or no longer have support:

Archived general expeditions

 * Cultural Expedition – There is already a place within articles for information about local culture, do's and don'ts, etc.
 * News Expedition — Promoting the creation of high-quality news for the Main Page.
 * RDF Expedition – Exploring uses of Resource Description Framework for Wikivoyage.
 * Routes Expedition – Create articles about routes and destinations available along the way, not in itinerary format.
 * Education Expedition — using Wikivoyage as a teaching and learning tool for students
 * Writers' Expedition — Wikivoyage needs writers
 * Fellow traveller Expedition — coordinating and cooperating with other projects
 * Access Expedition — explored how to enhance the information in Wikivoyage for disabled and physically impaired Wikivoyagers . Dormant since 2012.
 * Business listings reliability Expedition — finding ways to make listings more reliable. Dormant since 2012.
 * Cruising Expedition — developing formats and policies for articles on cruising on small craft. No activity since April 2013.
 * Tourism Bureau Expedition — coordinating cooperation with tourism bureaus and convention and visitor bureaus
 * Search Expedition — improving Wikivoyage's search ranking, cross-linking and usage among travellers
 * Country surgeon Expedition — creating well crafted "See sections" for all country articles
 * Prose Improvement Expedition — improving the written style of Wikivoyage's articles
 * Phrasebook Expedition — exploring the place of phrasebooks and organizing their development

Archived geographical expeditions

 * Florida Expedition — was dedicated to achieving guide status for Florida. Dormant since 2012.
 * Maryland Expedition — was dedicated to improving Maryland beyond guide status. Minor updates in August 2013. Otherwise nothing since 2012.
 * Poland Expedition — was dedicated to achieving guide status for Poland. No real updates since 2012.

Completed expeditions

 * Ireland Expedition ✅ Oct 2021
 * Northern Ireland Expedition ✅ Oct 2021

title: Wikivoyage:Expeditions


text:
Wikivoyage:External links

External links are links to websites other than Wikivoyage. In general the Wikivoyage policy is that external links should be kept to a bare minimum, and only links to primary sources should be used. There should be no external links section in any article.

What to link to
External links should point to primary sources. For example:

 * The official tourist office or government website for a destination
 * The official website for a hotel
 * The official website for a restaurant or bar
 * The official website for a museum, park, or other attractions
 * The official websites of cultural and educational organizations offering programs of interest to travelers, such as foreign language instruction or cooking classes.

Using only primary sources makes our guide more succinct: while there is usually one, or sometimes two, primary sources for any subject, there can be hundreds or thousands of secondary sources. We also avoid subjectivity and conflict. It's difficult to decide collaboratively which of the thousands of English-language newspapers, magazines, and websites has done the very best travel article about New York City, but it's quite easy for everyone to agree that https://www.nyctourism.com/ is the official city visitor's guide. If the destination has both an official visitor's guide and a general government site, include only the visitor guide.

What not to link to
Avoid linking to secondary sources. For example, avoid links to:

 * Hotel or travel booking services or aggregators
 * Nightlife guides
 * Restaurant guides
 * Blogs, forums and social networking sites (Facebook, etc), with the exception of when a business has no other official web presence
 * Lists of links, service directories (including Wi-Fi directories)
 * Price comparison websites
 * Map services
 * Newspaper and magazine articles
 * Personal image galleries and photo/video sharing websites (Flickr, Webshots, YouTube, etc)
 * Personal travelogues
 * Search engine results (e.g., http://www.google.com/search?q=Montreal)
 * Encyclopedia articles, except for templated links in the "Wikipedia" field of listings and sidebar links generated using Wikidata – a special case. See Links to Wikipedia.
 * Other travel guides, including audio guides, audio tours, virtual tours and webcams
 * Vacation rental agencies that do not meet Wikivoyage's rental listing criteria
 * Real estate agents or agencies. Wikivoyage is not a relocation service, and therefore focuses on temporary accommodations.
 * Tour operators that do not meet Wikivoyage's tour listing criteria
 * Rental car operators in cities where they are common (10 or more operating in the city). Typically we don't provide details of national car rental chains in local guides. Providing details at the national level, and mentioning the name and location at local level is sufficient, if required.

We should avoid links to other travel guides, to ensure we have travel information in Wikivoyage, not linked from Wikivoyage. This is an incentive issue; if we have lots of links to other travel guides, we lose the impetus to create our own. In addition, one of our goals is to produce a guide useful for printing or offline use, and therefore we need information to be within the article rather than linked to at another site. See also the "Avoid references to third-party ratings and rankings unless they are truly exceptional" rule in Wikivoyage:Don't tout.

We also do not provide links to source information or provide references—travel guides do not use footnotes! If a source looks like it could be of use to subsequent editors of a guide, or if some information you add appears suspect, mention it (or link to it) on the talk page – not in the article itself.

An important exception to this is that we provide links to governmental sites in travel warnings.

External link format
There are three possible formats for "external" links. For the sake of consistency, we only use the first:

Good

 * Front-linked example. To create such a link, use the syntax  (with caption)

Note that  or   must be included in the link. The software won't recognize a link if the prefix is missing.

Bad
Don't use these:
 * Footnote style, . This would be created by.
 * Unpacked http://www.example.com/. This would be created by  (without   and  )

The predefined listing tags (see, do, eat, drink, buy, sleep) use the listing template, which frontlinks the listing name in the standard format if a target is specified in the url field.

External link usage
There are three possible uses for external links:

 * Links in listings: Please include primary source links for listing establishments (e.g., museum website, restaurant website, hotel website, etc.).
 * In-article text links: Links within the article text should be kept to a minimum and should point only to primary sources. Examples of valid links might include airline companies, bus companies, and sites offering daily updates and warnings about a destination's condition.
 * Official destination links: If an official website exists for the destination, it should be linked to only once, towards the end of the Understand section. If a destination maintains separate websites for tourism and for civic administration purposes,  both may be linked in the Understand section and should be identified clearly. (This policy was changed in 2020. Websites should no longer be linked in the lead paragraph, but since this affects almost every article it will take some time to implement this change.)

 * For example:
 * Visitor information
 * Marketing Edinburgh Official Guide
 * City of Edinburgh Council
 * Visit Scotland Edinburgh page
 * Only primary links should be used; a website that is not maintained by the destination would not be appropriate. For example, in the Disneyland article, a link to https://disneyland.disney.go.com and only to that website is appropriate.
 * Only primary links should be used; a website that is not maintained by the destination would not be appropriate. For example, in the Disneyland article, a link to https://disneyland.disney.go.com and only to that website is appropriate.

Don't mislead
What the reader expects to be at the end of a link, should be at the end of the link. A link to a service provider web page, where permitted by policy, should always be preceded by or labeled with the name of the service provider.

Use short readable links
Remember that for print versions of Wikivoyage, links will be presented in all their URLish ugliness. Readers of the print versions will have to type in by hand the URL that you add. For this reason, try to use the shortest URL possible for links, even if it means a little more work on the part of the reader when they click through a link. Where possible, try to trim out "housekeeping" stuff from the URL. You can almost always leave off,  ,   or   from a link, for example.

If http://www.example.com/ redirects automatically to a home page like http://www.example.com/home/index.asp?id=384&lang=en, use the shorter version, even though it's really going to the long version. Similarly, if http://www.example.net/ has a "splash screen" which eventually takes you to http://www.example.net/index2.htm or something, leave the top-level link in, even though the "real information" is located elsewhere.

Tip: For many hotel chains,  works as a quick and easy redirect. For example, Le Meridien Kuala Lumpur can be found at http://kualalumpur.lemeridien.com/ as well as http://www.starwoodhotels.com/lemeridien/property/overview/index.html?propertyID=1840&EM=VTY_MD_kualalumpur_1840_overview, and the short version will not break when the chain changes its reservation system (which seems to happen every few months).

Of course, if the page you're linking to isn't at the "root" of the site, it makes sense to leave the path part of the URL in. Don't change  to , since that top-level page probably doesn't have the same dance information.

Don't use links to redirection services, such as tinyurl, just to make the links shorter.

Languages
This version of Wikivoyage is for English-language speakers, so links should go to English versions of sites when possible. However, official primary links should always be added, even if they're not in English: some travellers can read the local language or decipher it with online translation; other travellers will still find pictures, maps, schedules, or prices handy, and they may be updated to include English in the future.

Many sites have the information in several languages, e.g., the local language and English. They handle this in different ways:

 * Some use the browser's language preference in which case you just use a link to the main page. This has the advantage that if a non-English speaker uses the English Wikivoyage and follows a link to a page also available in his/her language, the right version will be displayed. You will have to set your browser's language preference to English to test if there is an English version or you can enter the URL in a proxy such as Proxify. You can check the language preference of your browser also.
 * Some sites have an English version with a good permanent URL, such as: http://travel.example.com/english . Use that URL.
 * Some sites have a main page in a non-English language with a cryptic link to an English page, such as http://travel.example.com/fff?349sdshd.asp . This might not be a permanent link, so it is better to use the URL of the main page and let Wikivoyage users find the current link to the English version.

Unpack links
A link is not a substitute for actual information. Our goals include creating pages useful as printed guides. So, we need to include information that's at the other end of a link, even if it may seem redundant for on-line use.

For example, in a restaurant listing, get the address, phone number, hours, and prices for the restaurant, even if it's right there on an external web page. Someone using a printed guide won't have access to whatever's on that page.

Print version
When Wikivoyage articles are printed the Wikivoyage stylesheets are set up so that the full URL of a link will appear in text enclosed in parentheses immediately after the link text. For example, an attraction listing would print as:

 * Asian Civilisations Museum ( http://www.nhb.gov.sg/ACM ), 1 Empress Pl, ☎ +65 6332 7798.

Travel advisories
A warningbox or cautionbox may link to governmental travel advisories or breaking news reports of conflict or natural disaster. See the documentation for Template:Warningbox

Weather forecasts
A link to an official weather forecast for the destination is often placed in the text field of Climate. The ForecastNOAA template will link to the NOAA forecast if the destination is in the United States.

Wikipedia and Wikimedia
We have a special format that features links to Wikipedia and Wikimedia Commons in a special part of the page - see Links to Wikipedia.

Wikidata provides a means to link a Wikivoyage page to a page on the same topic in another Wikivoyage language or in another Wikimedia project (such as Wikipedia); see Cooperating with Wikidata and d:Wikidata:Wikivoyage/Resources.

The listing template supports links to a venue's official site, to a Wikidata entry and to an encyclopaedia article; see the template's documentation for details.

title: Wikivoyage:External links


text:
Wikivoyage:FAQ

Here are some Fearfully Anticipated Questions that Wikivoyagers have heard, or think they may hear, or wonder about themselves.

If you don't see your question answered here, ask it at the travellers' pub.

What is Wikivoyage?
Wikivoyage is a project to create a free, complete, up-to-date and reliable world-wide travel guide. It is built in collaboration by Wikivoyagers from around the globe. You can read more about Wikivoyage on the About page.

(Phew! That was an easy one.)

Who are you people?
We're Wikivoyagers. People from all over the world who are dedicated to making Wikivoyage the best darn travel guide around. Most of us are people who stumbled across the site, just like you, and decided to share our knowledge.

Who edits and organizes all this, though?
We do. Wikivoyagers. We create articles and then edit them, and we organize the articles into hierarchies and make links between them and have navigational pages, and things like that.

So, anyone can just drift in off the Internet and start writing travel articles?
That's the idea, yes. We use wiki software that lets any reader edit any page, instantly.

How is that supposed to ever work?
Doesn't seem like it ever could, does it? With anyone able to edit any page, things should just descend into terrible chaos, shouldn't they? Madness, mayhem, and a horrible bog of unusable drivel.

Strangely enough, it doesn't. People who care about having well-written travel articles on this site are the majority. People who just want to vandalize or delete things eventually get bored with it – you have to admit, it's not that much of a challenge – and the rest of us come in and clean up. Policy, and more specifically the Manual of Style, keeps the formatting of articles similar across all pages of the website.

The other great part is that wikis converge. One Wikivoyager adds as much as they know about a topic, and others start adding more information. Other people come through and condense it all so it reads well. As the topic changes – new hotels open in a city, new bus routes start between regions – more Wikivoyagers can add that in.

Do you have any proof that this works?
Well, we have the existence proof of other projects that create references collaboratively. Probably the most famous one is our own sister project, Wikipedia, the free encyclopedia. Many of our policies and guidelines are borrowed from that project. And what you find here on Wikivoyage was made that way!

OK, so, there's all this hippy-dippy love stuff about working together, but who's really in charge?
You are. Any Wikivoyager can change articles, rewrite navigation areas, even overwrite information about the site itself. We try to make decisions about policy and guidelines collaboratively, but if you have a good idea for how we should work, plunge forward and let us know.

That all said, there are certain Wikivoyagers who've been working on the site for a while, and they can become Administrators. Administrators generally get some higher access – like really deleting pages instead of blanking them – but not much power. They just implement what has been decided, with some leeway. It's more of a burden than a privilege, and not all experienced editors are administrators.

Who owns the site? Who operates the servers?
The content of the site is owned by Wikivoyage contributors, who each own the copyright to their own contributions, and agree to license them according to the Creative Commons by-sa license. If you've found a photo or another work by a single contributor on Wikivoyage, and would like to use it under terms different from that license, please contact the creator of that work directly.

The domain names wikivoyage.org, wikivoyage.net and wikivoyage.com, and the equipment the site runs on is owned and operated by the Wikimedia Foundation.

Who pays for all this?
Wikivoyage does not directly accept money from any attraction, restaurant, hotel, tour operator or other travel-related company in exchange for favorable coverage. (They're welcome to contribute in other ways, though.)

The Wikimedia Foundation is funded by voluntary donations.

What is this software you're running?
We use MediaWiki, the software developed for Wikipedia, with some totally tiny changes for Wikivoyage. You can get it from mediawiki.org.

How do I spell "Wikivoyage"?
Capital W, eye, kay, eye, vee, oh, why, ay, gee, ee. The "v" in the middle is not capitalized – try to avoid the temptation.

How do I pronounce "Wikivoyage"?
People vary on the "Wiki" part. It's either "WEE-kee", "WIH-kee" or "WIK-kee". Feel free to apply your best foreign accent to the "voyage" part.

Where's the contact information?
There isn't any. If you have a question about an article in particular, post it on the talk page for that article. If you have a question about Wikivoyage in general, try posting in the travellers' pub. If you're a new user and need some help, we've got the arrivals lounge, and if you've got a question about travel, please ask in the tourist office.

Contributors have their individual talk pages so you can use them to speak to other Wikivoyagers directly. Your talk page is where other users will contact you!

For legal matters you can contact the Wikimedia Foundation, if other means fail.

Is it true that Wikivoyage's content came from Wikitravel?
At one point it was true, more or less: when the English language Wikivoyage was founded in 2012, we brought over the travel guides from Wikitravel. (This is both legal and moral thanks to the free licence both sites share!) In fact, Wikivoyage was founded by a very large contingent of editors and administrators from Wikitravel—the very people who originally wrote much of the content we imported. Since then, the content of the two sites has diverged greatly.

If you're interested in the gory details of why we forked the project, we have a page that provides a recap. But we are our own project now, and we're moving forward with great new content. As time goes on, our content will continue to resemble Wikitravel's less and less—hopefully, by being more up-to-date, better organized, and more integrated with the other wikis of the Wikimedia Foundation.

This article is all wrong! You have to fix it!
This is a wiki – you can fix it yourself! Click the edit this page link, and change the parts that bug you. That's the whole idea (and the edit summary is a good place to explain what was wrong).

I am trying to find Topic X, and there's no article about it!
There are parts of the globe that no one has even thought about writing about yet. If you think you have a some information to contribute, feel free to create the page.

I am trying to find Topic X, the page just has headings and an intro
Some topics only have outlines covering them, and there are huge parts of the globe we've only begun to work on. Feel free to plunge forward and add more information.

I am trying to find Topic X, and all that's there is "asdfkjadflkjfd EAT MY BUTT"!
This is typical vandalism. Feel free to remove the vandal's garbage.

Make sure to check the article's history (there will be a "history" link at the top of the page) and look at the second or third revision listed (saved by another user) to see if that earlier version made more sense. You can edit, add to, and save that version to preserve the original content.

I have an idea for an article, but I don't know exactly how to get started.
Check out how to start a new page.

I have some information I want to share, but I don't know what to do with it.
The article skeleton documentation explains the section headings, and how the articles are laid out. We also have a page that tells you where you can stick various types of venues and points of interest.

The article on my destination is great, but I still have some questions.
See if your destination has a "docent". That's what we call Wikivoyagers who have volunteered to answer questions about their favorite spots. Ask them your questions, but don't abuse their generosity! You can read more about docents.

I want to cross-post content from another site under a CC-By-SA license (like Wikipedia or Wikitravel). Can I do this?
Yes, that is one of the main features of the CC-by-SA license! Make sure that the particular license is compatible, though—we cannot accept any content that has a non-commercial (NC) or no-derivative-works (ND) clause. Like Wikipedia, we require that you include a reference to the original source in the edit summary to preserve attribution.

 * eg:

We discourage wholesale copying from other Wikimedia projects, however, as we aim to provide original writing and to generally provide value-added, rather than "value-duplicated," content.

See Project:Wikivoyage and Wikitravel for information relevant to Wikitravel.

There aren't any references cited in articles! How do I know the info is accurate?
Requiring references for all edits doesn't work for a travel guide because much of the content is based on original research - the experiences of travelers and residents of places around the world. Many listings within articles include a link to the official web site for the business or attraction, and these links can be used similarly to how references are used on other sites. For other content, having lots of editors constantly reviewing and updating articles helps to keep articles accurate. If you find an inaccuracy simply remove it, and if you find something that seems dubious use the article's talk page to ask others to weigh in so that the questionable item can be either verified or removed.

This all looks like gobbledygook! How do I edit these pages?
Pages on Wikivoyage are formatted using wiki markup. It looks funny at first, but after a while it seems like second nature. You should read about how to edit a page. For individual "listings" you can use the listing editor, giving you a form to fill in or correct.

How do I upload an image to use in an article?
You should follow the instructions on how to upload files.

How do I put an image I uploaded into an article?
You should follow the instructions on how to add an image.

Hey! I wrote this long nice article on Topic X, and it got changed! What gives?
Any Wikivoyager can edit any page. When you submit an article, it's subject to ruthless editing for style, subject matter, spelling, factual information, and just generally fitting into the Wikivoyage scheme of things. If you don't like that, you shouldn't work on Wikivoyage. But if the change was vandalism, just revert.

Hey! I changed my nice long article on Topic X back to the way it was before, and it got changed again! What gives?
You need to go to the talk page for the topic you're writing about and work out your differences with the other article editors. Please avoid getting into an edit war.

How do I delete a whole page?
First, consider if the page really needs to be deleted. Perhaps it can be redirected to somewhere useful to the reader?

If the page does need to be deleted, then the procedure is somewhat more complicated: Go to Project:Votes for deletion and add a link to the page together with a reason for deletion. After fourteen days of discussion the page may be deleted, depending on how consensus develops. Vandalism and the like can be deleted out of procedure, whether or not they get listed on that page.

Articles about places are typically best redirected to the nearest existing destination article.

How do I sign a posting?
When posting a message on a talk page it is customary to sign the posting with your user name and the posting date so that everyone knows who you are (for example: "User 15:35, 6 May 2005 (UTC)"). To get that text to appear automatically, simply type four tildes (" ~ "), and they will be replaced with your user name and the current date when the edit is submitted.

Sorry, I don't speak English very well. Can I put articles in my own language in Wikivoyage?
Yes, if there is a separate Wikivoyage version for your language. If Wikivoyage in your language does not exist yet, you can start your own language version! To find out more, see our language version policy.

But my English sounds terrible. I'm embarrassed.
Don't worry too much about the level of your English, as long as it can be understood. Your spelling errors will be corrected by other people. We really want you to share your knowledge!

If you have an important point that you cannot explain in English, you could use the talk page. Write the point in your best English and clarify in your own language. Wikivoyage is a very international community, so there is likely to be somebody who understands your language.

Should I use US English spelling, or Commonwealth English spelling?
If the destination has a preferred variant of English, use that—use Commonwealth spelling for destinations in the United Kingdom, for example. For topics and destinations that don't have an established English language variant, we prefer US English spelling. In either case, though, don't worry too much about it; if you don't know the details of the different English spelling rules, just use what you know and someone will fix it later. See Spelling for details.

title: Wikivoyage:FAQ


text:
Wikivoyage:Fellow traveller Expedition

The Fellow Traveller Expedition is a Wikivoyage Expedition to explore how Wikivoyage can cooperate with other relevant, open-content, user-generated projects to which we have some relation.

Rationale
Travellers, whether they're taking the same route or merely crossing paths, will often help each other out. Wikivoyage is itself taking a virtual journey towards our goals, and along the way we will meet other projects trying to get to their respective goals.

By working with other projects in constructive ways, Wikivoyage can build up good will in the Internet community, which could mean more Wikivoyagers and thus more and better Wikivoyage content. By leaning on other projects, we can offload side tasks that we'd otherwise have to take on ourselves. In addition we can learn from others' experience, which, hey, is what Wikivoyage is all about.

Goals

 * To identify and list other projects related to Wikivoyage.
 * To determine for each project what we can offer and what we can use.
 * To approach projects and communicate with them.
 * To execute cooperation plans.

What's a related project?
There are uncounted things that could be called "projects" in the world: Web sites, organizations, individual efforts, etc. To be related to Wikivoyage, projects should either have something to do with our goals, or with the way we are trying to achieve those goals. Projects may be related to Wikivoyage if they're involved in or have something to do with one of these topics:

 * Travel, and particularly travel guides.
 * Geography.
 * Creating reference works.
 * Wikis.
 * Open Content.

There are probably other ways that projects can cross Wikivoyage's path; these are just some of the more obvious ones.

List of related projects
Projects that are related to Wikivoyage should be added to the list of related projects. Each related project should have an URL listed, as well as a brief explanation of the project, its licensing, and how it's related to Wikivoyage.

Cooperation
If there's interest in cooperating with a project, we can make a cooperation page in the Wikivoyage: namespace to talk about what we can offer and what we can use from the project. Cooperation pages should be named something like "Cooperating with Name of project", such as Project:Cooperating with Wikipedia, and should also be listed on the List of related projects page.

Approaching other projects
Of course, any Wikivoyager can approach any other project at any time to talk to them about cooperating with Wikivoyage in any way. That said, it would probably be helpful to look for, or start, a cooperation page to coordinate with other Wikivoyagers before approaching other projects.

It's probably not a good idea to represent yourself as something you're not ("As the elected president of Wikivoyage, ...") or to make promises you can't keep ("We'll change our software to meet your needs!" "We'll host your Web site!" "We'll give you a special license to Wikivoyage content!"). It will be embarassing to you when the truth comes out, and it might make future relationships somewhat strained.

When you approach the other project, be sure to give them the URL to Wikivoyage, and preferably the URLs to the Project:About page and the cooperation page for their project. Give them lots of options for responding -- although working on the cooperation page would probably be the best way to get them involved.

de:Project:Expedition 'Reisegefährte' fr:Project:Expédition Autres voyages

title: Wikivoyage:Fellow traveller Expedition


text:
Wikivoyage:Field research checklist

If you find yourself on the road, please think about how you can use your experience to help future visitors. Consider the following checklist. Feel free to pick and choose from the items below for things you can do to help.

The lists below assume you are traveling to a destination covered by a single article. If your trip covers multiple articles (as most do), repeat for all such articles.

Before you go

 * 1) Look at the existing page for your destination.  If it doesn't exist, go ahead and create it.
 * 2) Is there anything obviously wrong (vandalism, external links, spelling) that you can fix right now?
 * 3) Are there pictures of the destination?  If not, pack your digital camera so you can upload images to Commons when you get back.
 * 4) Print out a copy of the article and pack it.
 * 5) Read the articles from Wikipedia and other sources linked to on the left sidebar.  Think about what things they mention that are useful to the traveler that are missing from Wikivoyage.
 * 6) Is there a docent for the article?  If so, consider contacting them and asking what you can do to help.
 * 7) Consider posting a note on the talk page for the article letting people know that you'll be in the destination and asking what people are interested in seeing added.

While you're there

 * 1) First of all, enjoy your trip.  Don't get too distracted by research.
 * 2) Take pictures.  After you take a picture of your family in front of the local piazza, have them move out of the way so you can get a picture suitable for Wikivoyage.
 * 3) Grab a business card from any local restaurants you'd like to add.

When you get back

 * 1) Does the existing description in "Get In" fit with your experience of arriving?  If there is no description of your mode of travel, start one.  What was unusual about the experience that other people should know?
 * 2) How did you get around town?  Look at the "Get Around" section and see how helpful it would be to a stranger to the location who was using the same mode of travel.
 * 3) Did you stay in a hotel or other paid accommodation?  If so, would you recommend it to others?  If so, please add it to "Sleep".  If not, please delete it from "Sleep" if it's there, but explain why in the Talk page.
 * 4) Is there a docent for the article? If not, and you feel you have gained sufficient knowledge of the destination, consider becoming a docent.

title: Wikivoyage:Field research checklist


text: Wikivoyage:Finnish Wikivoyage Expedition


text:
Wikivoyage:Florida Expedition

The Florida Expedition is a Wikivoyage Expedition to promote and coordinate collaboration to improve Wikivoyage's articles pertaining to the US state of Florida. If you'd like to join the effort, please add your signature to the bottom of the page!

Rationale
Viewed by itself, improving Wikivoyage coverage of an US state is a daunting task. This difficulty is exemplified by the fact that Wikivoyage has only one state article of guide level status (Maryland)! This Expedition exists to to clarify exactly what needs to be done in pursuit of our goals for Florida and related articles, identify avenues for potential collaboration, and generate enthusiasm towards achieving our goal.

Goals
The main goal of the Florida Expedition is to achieve Guide status for the Florida state article. In pursuit of this goal, we must:

 * 1) Improve the quality of the Florida article itself, by adding images, graphics, and prose
 * 2) Improve all linked destinations to at least usable status

Florida article

 * 1) Find/add great iconic images of Florida [Current Florida images]

Linked destinations
Featured collaborations:
 * Florida_Panhandle - Sub regions under the Panhandle need to be examined and reorganized.
 * North Florida - Bring page up to Usable.

Other Guide and Star Articles
Explore the links here for ideas on what can be added to Florida:
 * Category:Guide_articles
 * Category:Star_articles

Article status chart
The following chart shows the current status of all linked destinations which must be at least usable status in order for the Florida article to achieve guide status.

Expedition members

 * User:AHeneen Talk
 * User:(WT-en) OldPine Talk
 * User:(WT-en) Huckabmm Talk
 * User:(WT-en) Jtesla16 Talk
 * User:(WT-en) JesusbymySide Talk

title: Wikivoyage:Florida Expedition


text:
Wikivoyage:Foreign words

Use italics to delineate foreign words that have not been adopted in English. Don't use any formatting or punctuation to delimit words that have been adopted in English.

Examples:

 * Do italicize
 * arrondissement
 * tuk tuk
 * khong
 * But do not italicize:
 * kung fu
 * haggis
 * hotel
 * Latin abbreviations such as "etc.", "e.g.", or "i.e."

Translations
To note the foreign-language translation of a word, list it in parentheses right after the English name, with the name of the language, followed by a colon, then the foreign language name in italics. If the language does not use the Latin script, give the local script (no italics) followed by the correct transliteration (in italics). Some examples:

 * The subway (French: Métro) is very convenient.
 * A tasty Japanese treat is grilled eel (うなぎ unagi).

Alternately, you can use the foreign language word in italics, and provide the English translation in parentheses afterwards, as in:

 * The Rathaus (city hall) is in the center of town.
 * In Thailand, Western-style black tea is known as chaa ron (ชาร้อน, "tea hot").

If there's just no translation for a foreign word, or the word has been explained already, just use it without a translation.

Proper names
For Wikivoyage, we prefer to use the most common English-language name for people, places, and things. However, it's often useful to point out the local-language name for a place or thing in an article, since travelers will often encounter those names. As with other foreign words, list the foreign-language name for a place or thing in parentheses after the English name:

 * Mexico City (Spanish: Ciudad de México)
 * Basque (Basque: Euskara)
 * Istanbul (Turkish: İstanbul)
 * New Brunswick (French: Nouveau-Brunswick)

If the foreign language uses a foreign script, include an italicized transliteration within the parentheses:

 * Penza Oblast (Russian: Пензенская область Penzenskaya oblast')

If there's more than one language you want to give the name in, put them all in the same set of parentheses, separated by a comma.

 * Geneva (French: Genève, German: Genf)

Avoid listing the names of places in every single language under the sun. It's usually only helpful to English-speaking travelers to know the local language name. Yes, it's possible that some travelers may need to know how to say and write "Oslo" in Tigrinya or Quechua, but the chances are diminishingly small, and it would clutter up the destination pages to add those names in.

Once the language has been specified, you do not need to repeat it later in the article.

Spelling
For foreign words that have entered the English language, use the English spelling as appropriate for the destination. For all other words, use the locally preferred spelling. For instance the "ß" symbol which does not exist in Switzerland and Liechtenstein should not be used in Swiss destination articles (except when discussing its absence), but should be used for German and Austrian articles under the currently applicable spelling rules.

title: Wikivoyage:Foreign words