text:
MediaWiki:Spam-whitelist

# # # # \w+\.sh\.cn 00100roma\.it aladdincasino\.com albury-wodonga\.com almaty-bus\.narod\.ru almaty-tramway\.narod\.ru almaty-trolleybus\.narod\.ru biscuit-palace\.com casinovenezia\.it chinabeijinghotel\.com\.cn china\.com cuc\.edu\.cn cyu\.edu\.cn donga\.com expo2010china\.com forms\.gle freewebs\.com fremontcasino\.com gb\.com geocities\.com goldcoastcasino\.com hotels\.com joes\.com linktr\.ee luggagestoregallery\.org mainstreetcasino\.com milfordplaza\.com milford\.com muze\.gen.\tr nouveaucasino\.net nynyhotelcasino\.com pharmacymuseum\.org pralniawodnik\.republika\.pl premiumflats\.com reefcasino\.com\.au sockshopandshoeco\.com stbishoy\.8k\.com thebootmakersshop\.com\.au thebridges-shopping\.com u-tokyo\.ac\.jp vancouverlookout\.com wikivoyage\.org ya\.ru youtu\.be # #
 * 1) This is a list of domain names which are whitelisted on en.wikivoyage only.  Please check
 * 2) the guidelines on the talk page when adding entries.
 * 1) Syntax is as follows:
 * 2)   * Everything from a "#" character to the end of the line is a comment
 * 3)   * Every non-blank line is a regex fragment which will only match hosts
 * 4)     inside URLs
 * 5)   * You do not need to put \ before a /.
 * 1) This is the local whitelist for URLs that are being incorrectly blocked by the Project:Spam filter.
 * 2) To add URLs or URL fragments to this list, add them in in alphabetical order between the pre tags, and
 * 3) indent one (1) space. You MUST also leave a note on the talk page
 * 4) indicating why the URL is valid.

title: MediaWiki:Spam-whitelist


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) logo contest

After two years of operation, Wikitravel needs a new graphical logo.

The old one has served us well, BUT: it's not in the correct file format, it'll look awful on merchandising / publicity, and it's mis-spelled!

How to enter
Logo entries should be submitted by 1 August 2005. Graphics should be submitted as compressed bitmap files (preferably PNG files) as well as vector graphics files (such as SVG, PostScript, Illustrator, or Gimp) or other source files that can be further modified, scaled, etc. The final PNG entry should have a transparent background.

To submit an entry to the contest, upload the file(s) to Wikitravel, and add the image to the Logo contest entries page (see directions on that page for details). All entries must of course conform to the Wikitravel copyleft policy.

If you'd rather submit an idea for discussion use your User page or a page within your user namespace to sketch out the idea, and link to it from the logo contest ideas page.

Logo guidelines
Of course, it's up to you what you want to do with your logo. But it would be helpful if you could consider the following guidelines:

 * Wikitravel now has multiple multilingual versions - any text in the logo should be minimal and easy to replace with text in other languages
 * Travel-related logos are preferred
 * It would be nice to emphasize some of the themes of Wikitravel, namely the spirit of sharing knowledge, plunging forward into editing, etc.
 * The logo should be legible and identifiable in a number of sizes and environments, including the top-left corner of this page, the favicon, as (or combined with) a compass card for Wikitravel maps, on T-shirts, and in black and white for newsprint. Alternately you can develop and present a family of branding marks to serve these various needs.

Logo voting
After the contest deadline, registered users will have fourteen (14) days to vote for the logo entry of their choice (details of the voting process to follow).

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


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) logo contest entries

This page lists the current entries for the Project:Logo contest. To add an entry, do the following:

 * 1) Upload both the bitmap (PNG) version and a source file (Postscript, Gimp, Illustrator, or whatever)
 * 2) Add rights (copyright holder, etc.) information to the Image: page for each uploaded file.
 * 3) Add the bitmap version to this page, as well as a link to the source file. Underneath, sign the submission with your Wikitravel user name, and give a few words of explanatory text (if you want).

The Wiki markup for a submission should look like this:

 * [[Image:bitmap_version.png]] Image:source_version.whatever  Ryan • (talk) • -- Explanatory text

(You should be able to just copy and paste that, by the way, substituting in your file names.)

Submissions should go below the following line and above the old logo. Thanks for submitting!

Submissions go here!

Note: the use of a scatter brush to suggest masses of people moving around the world doesn't work very well here - sorry... Perhaps the little arrows and the scatter brush might better be deleted, leaving just an Earth with a circle-W looking somewhat like a pool ball?

--(WT-en) Stefn

--(WT-en) Comrade009 18:13, 31 Jul 2005 (EDT) I finally have an SVG version: see it here. Note that even if this logo is selected, I will be more than glad to revise it (especially alter the mini icons) until everyone is satisfied.

Update: I uploaded the svg, but it won't seem to link to it. I have the file, so maybe I could email it to someone who knows how to upload it? Thanks, --(WT-en) Comrade009 18:16, 31 Jul 2005 (EDT)

I only have paint.

-User:(WT-en) DogZilla59

(WT-en) Pjamescowie had suggested using a compass rose as the logo. I rather liked that idea, and wanted to make sure at least one of the entries used it. More details about the image are on the image page. --(WT-en) Neil 00:58, 10 Jul 2005 (EDT)

 * I don't think the logo should necessarily have the tone that one can span the entire globe, but that one can zoom in on one particular area and get to know its characteristics and nuances on a personal level. This is why instead of incorporating a globe or broad outlines of continents, I decided to incorporate a generic subway/metro map which is enlarged by a magnification glass. Essentially, this is what Wikitravel is, anyway- a device used to zoom in on the specifics of a place. The image itself was done in MSPaint in less than 10 minutes, in grayscale. If you want to edit the idea, change anything about it, or make it look respectable, feel free to... --(WT-en) Klestrob44 17:00, 1 Aug 2005 (EDT)

 * With this logo, it incorporates the concept of "delving in and being bold", or whatever that phrase is, with the stack of books, and an open one being edited. I tried to make the logo less corporate and more scholarly than some entries. Behind it are an airplane and a generic palace, modeled after Buckingham. It was made in glorious MS Paint. Feel free to revise. --(WT-en) Klestrob44 17:57, 1 Aug 2005 (EDT)

 * And here's the small version of the above logo. --(WT-en) Klestrob44 18:34, 1 Aug 2005 (EDT)

 * This logo plays off of (WT-en) Mark's idea with the paper airplane/rose. There is a subtle "W" in the left end. --(WT-en) Klestrob44 18:58, 1 Aug 2005 (EDT).

I can't upload Photoshop source file. (WT-en) Yahrou

(WT-en) Paul Richter 23:04, 20 Jul 2005 (EDT)

The emblem part of this logotype idea was inspired by --and can be used as a compass star but I think the shape has a number of other travel related overtones. For instance the version at the top of the page with the name "wikitravel" sandwiched between the two halves of the compass star for me recalls a racing skiff or some other kind of sailboat with a long keel.

Another image the emblem part of the logo recalls is that of two butterflies settling to rest in a nose-to-nose position. Or perhaps they are paper airplanes? If so somebody (of screen) must have put those airplanes into motion. I think this subtily implies the action of user's hands without attempting to render them.

You'll note that there is no 3D shading, or blending or anything like that in the emblem part of the logo. I feel that that sort of treatment became cliché sometime in the late 1990s and probably shouldn't be used for serious logotyping. Worse that sort of thing tends to lead to higher printing costs for things like business cards, letterhead and T-shirts. Speaking of printing costs I'd like to point out that the blues in this logotype are all tints and shades of the very same blue. Therefore it would be possible to print all Wikitravel using this logotype with a single ink (which is not to say that better results could be achieved by using black plus a couple of different inks for the blue.

By tweaking the value of the colour in the lines the emblem part reduces nicely even down to favicon size. It also makes a good compass star (with a "W" replacing the customary "N").

The font used for the Wikitravel name is Ray Larabie's "coolvetica" font, and the caption is in his "helmet" font. I'd like to point out that (WT-en) Comrade009's excellent logo entry above pointed out "coolvetica". I did some kerning though. Should we choose to use Comrade009's logo I'd like to see the type kerned as I've done here.

Additionally I'd like to point out that I don't see this logotype as final in any way, even if it were to win the contest. I think anybody should be able to offer up modifications or variations of these images at any time. I can see changing the brightness and saturation of the colours over time to reflect our collective mood, etc. The current colours are muted in an attempt to embody a concept of professionalism, but with time perhaps brighter blues will fit us better? Who's to say? We all are, together.

As one can't for the moment download an SVG image from Wikitravel you can also find the source here. Sorry about the filename, I should change it but I'm running late for lunch. -- (WT-en) Mark 06:50, 21 Jul 2005 (EDT)

Can you identify the continents? -- (WT-en) Paul Richter 00:53, 22 Jul 2005 (EDT)

OK, this is my first attempt at drawing a logo for anything ever, so don't be too mean!

I had a concept in my head of a notepad where someone had scribbled a picture of a plane that became a real plane. It was trying to convey the idea that anyone who goes on holiday can take notes, add them to wikitravel, and create amazing holidays for others.

I'm no artist, unfortunately, and this one has taken me several hours of fiddling in the GIMP.

Let me know what you think on the discussion page for this image.

 * -- (WT-en) Owl 09:43, 23 Jul 2005 (EDT)

Note to people who are voting: this image is more a proof-of-concept than anything else. I am open to improving this image in any ways people think are good. I'm also happy to release the XCF (GIMP) file for people to make the modifications themselves. See the discussion page for an example of nice text for this image rerendered by (WT-en) Mark.

 * -- (WT-en) Owl 05:04, 1 Aug 2005 (EDT)

Here's the text or logotype part (WT-en) Owl mentioned:

I do believe that the second lowercase "i" should be curved in the other direction. -- (WT-en) Mark 05:29, 1 Aug 2005 (EDT)

Here are a few logo contributions. There are two main versions, one greyscale, and a browser icon. The actual images (click below) are bigger than those pictured in the following gallery. The backgrounds are transparent. Vector images are also available and could indeed be resized maintaining resolution to somewhere around 2000x2000 pixels if necessary. Let me know what you think, as I am fully open to community suggestions. [mailto:jsymmetry@gmail.com]

(WT-en) Jsymmetry 03:54, 25 Jul 2005 (EDT)

(WT-en) jmdelarosa

---   Image:comp1.ai  (WT-en) Jsmorse47 -- It's late, but I had to submit something!

Current Logo (to be Retired)
The globe alone, with transparency (PNG) (WT-en) Gutza


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) logo contest ideas

Mini-symbols
My logo has a couple of minisymbols, that each have modes of transportation. You can see it at my (WT-en) user page. Feel free to give feedback on my talk page. I'm also looking for someone with Illustrator experience to help me make a vector version.

BTW Mark, I like what you have so far. :) --(WT-en) comrade009

Compass card idea
I've been working on (WT-en) an idea for using a stylized compass card together with the jigsaw puzzle idea from WikiPedia. Please have a look and provide feedback. Thanks! -- (WT-en) Mark 10:14, 23 Jun 2005 (EDT)

Concepts
Some more conceptual ideas, without implementation. If you have a good idea for a logo, add it here. (Feel free to sign your addition if you use a lot of "I" or "me" language.)

 * Many hands. I like the idea of lots of hands working together to make something. Many hands writing in the same book, maybe? Or writing out the word "Wikitravel"? --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)
 * A road paved from hands. Kind of macabre, I know, but one idea I had was the hiker from this image walking across a line of upraised hands. Or a hands-road going off to the horizon. --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)
 * Sharing thought balloons. Kind of complicated, but maybe something about knowledge coming out of people's heads, in the form of thought balloons, and being shared with others? Or coming together to make a book? --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)
 * A changing world. One of our strengths is that we can make guides that keep up almost instantly with changes "on the road". Could a logo convey this idea? --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)
 * Re-edited guidebook. (WT-en) Maj keeps intricate notes in the margins of her guidebooks. She also adds new entries and crosses out missing ones. Maybe some sort of idea of editing, re-editing, etc. would be good? It'd be hard to make it not language-specific. --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)
 * Where I came from, where you're going. Two (or more) travellers going in opposite directions, each describing where they came from to the other (who's headed that way). Yes, pretty much impossible to describe iconographically. --(WT-en) Evan 13:20, 29 Jun 2005 (EDT)


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) logo contest results

New logo (2005)
Wikitravel's new logo is Compass Star by User:(WT-en) Mark. Archives of the selection process:

 * Project:Logo contest announcement
 * Project:Logo contest entries
 * Project:Logo voting page
 * Project:Logo voting page/Round 1

Original logo (2003)
Thanks to Wikitravel user (WT-en) Gutza, we now have a shiny new logo to call our very own. The results of our logo contest were indisputable. No vote was necessary, as Gutza's entry was obviously the only possible choice.

The image looks like this:

If you choose the "Standard" skin in your preferences, you'll see it all the time in the upper lefthand corner of Wikitravel pages. It looks great!


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) logo voting page

This is the voting page for the second round of the Logo contest. The design with the most votes will be selected as Wikitravel's new logo. Note that the objective is to select the design or idea of Wikitravel's new logo, not the final implementation.

See also: Project:Logo voting page/Round 1

About Logos
It might be a good idea to read up a bit before voting. Wikipedia has some good information on Logo design and some common mistakes and links to some really good articles like this one.

Also it would be worthwhile to read this classic essay by Paul Rand. Here's a summary:

 * A logo is a flag, a signature, an escutcheon.
 * A logo doesn't sell (directly), it identifies.
 * A logo is rarely a description of a business.
 * A logo derives its meaning from the quality of the thing it symbolizes, not the other way around.
 * A logo is less important than the product it signifies; what it means is more important that what it looks like.

he goes on to say that a logo depends on the following qualities to function

 * 1) distinctiveness
 * 2) visibility
 * 3) useability
 * 4) memorability
 * 5) universality
 * 6) durability
 * 7) timelessness

About the entries

 * All entries have had their author's names removed, and have been placed in random order.
 * Authors are allowed to replace their entry during the course of the contest; however, all previous votes for that entry will be removed. (please do not alter anyone's work besides your own)
 * Authors may choose to withdraw their entries at any point in the contest.
 * Some authors have chosen to submit multiple treatments of the same logo (i.e., a main logo, a fav icon, etc.). In this case, the entry has been labeled, and the main logo displayed. You can click on the image to view the full treatment.

About voting
In the second round you can choose one logo. Votes from the first round do not count, you will have to cast your vote again. Votes can be changed during the voting period and authors can vote for their own logos. Votes will only be accepted from logged in users and admins have full discretion for determining vote validity.

There will be two rounds of voting. The first round has decided the top 3 semifinalists. The second round, currently in progress, will determine which of the entries will become our new logo. In the event of a tie in either round, voting continues until a tie-breaker vote is cast.

Provisional results
The results below are subject to confirmation on the Talk page.

 * Compass Star: 22 votes (winner)
 * Puzzle Logo: 18 votes
 * Diagonal W: 5 votes

Puzzle Logo
Talk

Comments
IMHO, the horizontal treatment is really great. I also like how the puzzle theme echoes wikipedia, which is a positive association. -- Stanwiki 6:23 PST 8/10

Something I've been toying with:

A quick color study (seriously, I made these all within 10 minutes):

Wow, the horizontal treatment looks fantastic also. As for the colors, they can be fine tuned. This communicates what wiki is about.

Very nice! The colors are a bit, um, Microsoft-y though — I'm reminded of the Windows logo... and I don't think this will scale down very well. (WT-en) Jpatokal 21:48, 26 Jun 2005 (EDT)

 * Oh man, I just decided to look. I haven't much paid attention to the windows logo/emblem whatever, but I decided to do a quick google search.  Unfortunately it seems that the results would suggest that this is way too close. -- (WT-en) Mark 05:31, 8 Aug 2005 (EDT)

 * I don't think Microsoft can really copyright the idea of juxtaposing primary colors in a square, or otherwise they'll have to sue my 4th grade art teacher too. The order of the colors is (slightly) different and 'puzzle' idea is also original.  But legal issues aside, this certainly does seem to invoke a "Microsoft Wikitravel" feel, which is not exactly what we want to convey...! (Where do you want to go today?) (WT-en) Jpatokal 05:47, 8 Aug 2005 (EDT)

 * Agreed, conveying a relationship with m$ is off my list. At any rate though it's true that they can't copyright the idea, but they certainly can and have trademarked the idea (for use with operating system software). -- (WT-en) Mark 05:51, 8 Aug 2005 (EDT)

This is such an obviously strong image by itself that it seems unecessary to say so, but I'll say it anyway. -- (WT-en) Mark 23:27, 3 Aug 2005 (EDT)

Very distinctive. A strong branding statement. I think a color study of this would be interesting; trying the logo with different color schemes? Thoughts?

One of the good things about it is that some specific details can be changed, but it still has the same feel. Some people have suggest changing some of the symbols to non-transport travel things, like a bed. Colors can easily be changed; it looks ok even with the colors removed. To scale it down, we could have just one puzzle piece with a W in it, for like a favicon. --66.188.138.70 01:24, 4 Aug 2005 (EDT)

I believe that Evan's a bit busy with other things right now, so I'm going to add his comment from the talk pages that he's concerned that using a puzzle theme in our branding could cause confusion about our relationship with WikiPedia, or rather the lack thereof. I'd like to know what some WikiPedians think about that.

That said, I'd also like to point out that the Compass Star below is in effect a treatment of exactly this logo the logo being just the text part, especially if the puzzle tabs were to be put back in between the compass tabs. The reason I say this is that we use the same font, so the actual logo part of the logo is exactly the same between the two. The colours would need to be adjusted in both and the kerning in this one, but otherwise you could use a puzzle-like compass star along with this as part of a branding scheme. -- (WT-en) Mark 04:03, 4 Aug 2005 (EDT)

I like this one a lot as well- just the colors are M$... (WT-en) Nicamds 15:15, 5 Aug 2005 (EDT)

I want to re-iterate that I think that puzzle pieces tread a little too closely to Wikipedia's logo. --(WT-en) Evan 16:02, 8 Aug 2005 (EDT)

Given time, for the next round of voting, I'm going to do multiple versions in different colors. I'm also going to list separately a bunch of possible mini logos that can be put into the logo. --User:(WT-en) Comrade009

Second round comment: this is such an excellent logo, but I just can't vote for it. I just don't like the idea of using Wikipedia's puzzle-pieces. --(WT-en) Evan 09:28, 9 Aug 2005 (EDT)

I especially like the version "gradients". It could perhaps be worked to add even more the idea of a globe. It would be worth trying as four objects: car (or plane), bed, food, person" (now too much focus on transport) −(WT-en) Woodstone 14:41, 9 Aug 2005 (EDT)

 * I feel this is the best logo by far. Is it really that similiar to Microsoft's logo? When you think about it, all logos are very similiar in design; what distinguishes them is the concept behind them. Microsoft's logo conveys the ability to open and close programs at will, hence, "Windows", while this logo conveys the different aspects of travel that, when put together, form a complete trip. Just because they share similar colour schemes and a vaguely similar shape doesn't mean that they are the same at all. Secondly, what's so bad about treading on Wikipedia's design? The idea behind a multilingual Wiki in the first place goes hand-in-hand with the idea of puzzle pieces. If you want to revoke the similarity between this site and Wikipedia, then you might as well change the name from WikiTravel, and the fact that it uses MediaWiki. Finally, the other logo, Mark's, is (and somebody else pointed this out, too) totally vague and far off from the principles of Wiki which the logo was supposed to convey in the first place. I mean, seriously, WikiTravel isn't a corporation, the logo doesn't need to be aesthetically pleasing from the sides of buses and buildings, or when shrunk down and branded on pens, I thought the logo was supposed to promote the idea of delving in and contributing. Yes, Mark's logo is versatile, but any logo could communicate aspects of travel if it were manipulated in a certain way, a sphere could, a box could, a triangle could, but the logo doesn't describe anything about the site.--(WT-en) Klestrob44 17:38, 9 Aug 2005 (EDT)

 * Read the Paul Rand essay. The idea is to have something that is distinct and easy to remember. -- (WT-en) Mark 01:34, 10 Aug 2005 (EDT)

 * Even better, read our goals and non-goals. You need to take some time to understand what we're trying to do here. If you think the logo for this contest is just supposed to show up in the upper-left corner of every Web page, you're mistaken. At the very least, it should fit into a favicon.ico file, but Wikitravel has been meant from day one to be published in multiple media and multiple ways. A versatile logo is absolutely necessary. --(WT-en) Evan 08:38, 11 Aug 2005 (EDT)

 * This logo is the best. It is the only one that catches my eye.  I have to disagree about being too close to Wikipedia's logo and for all you anti MS, give it a rest.  You can't help but be drawn to it especially against the other two candidates.  The other candidates in my opinion look stuffy and corporate.  The Gradients is nice and I also very much like the horizontal logo. --(WT-en) CH 16:14, 10 Aug 2005 (CST)

 * It's not an anti-Microsoft thing; it's just too close to their logo. --(WT-en) Evan 08:38, 11 Aug 2005 (EDT)

 * A quick question- why is it necessary to adhere to the gospel of Paul Rand? There are plenty of logos that defy his principles and are among the most recognizable. That is beside the point, however, because this logo is distinct, easy to remember, and extremely versatile, as demonstrated above. --(WT-en) Klestrob44 18:34, 10 Aug 2005 (EDT).

 * The puzzle logo is clearly the best! It connotes travel really well, it has a folksy appeal appropriate to a community site, it is memorable and engaging.  -- Socaltransplant

 * I dig this logo, but I have to agree on the WikiPedia thing. Its not a matter of treading on their logo or anything like that, its just what was pointed out earlier - we don't have a realationship with WikiPedia except for the fact that we use the same software.  I don't know that its neccessarily a bad thing to be thought of as being related to something as successful as the WikiPedia, but it can cause some confusion, as I'm sure nearly anyone that has spent any time watching changes come through can admit.  Like I said, I hope Evan gets a spare moment before the voting closes to comment on this point directly.  I will admit I'm having a difficult time deciding. :( (WT-en) Ilkirk 23:28, 10 Aug 2005 (EDT)

 * I can comment on the issue directly: I really, strongly dislike the implied relationship to Wikipedia. I don't think it's fair to either project to have that implied link. At the very least, it makes us look like wannabes who can't stand on their own reputation. That's not the message I want to send out to the world. I think the contributors to this project deserve better than that. --(WT-en) Evan 08:26, 11 Aug 2005 (EDT)

 * having people inadvertantly think that we have a relationship to wikipedia is not necessarily a bad thing. Many people who don't know what a wiki is will have used wikipedia. People new to this stuff will probably end up thinking this is like wikipedia anyway, logo or not. The differences are really superficial to most people not keen on details, mainly 1)we're not part of the wikimedia foundation (i don't see how this matters) and 2) we have a different license (we have a "Welcome, wikipedians" page explaining the difference. And to be honest, we really do have a noticeable informal relationship with wikipedia. Many people coming to this project came first from wikipedia (I, for example), and we link to wikipedia all the time. I don't see how this will confuse people, besides in a semantic sense. --(WT-en) Comrade009 00:13, 11 Aug 2005 (EDT)

 * Confusing people with similar names and logos is unfair to readers and contributors of both projects. If it happens accidentally, so be it. But I think we should avoid doing it on purpose. --(WT-en) Evan 08:26, 11 Aug 2005 (EDT)

I understand that this logo has a lot of support among voters, but I've got a few major issues with it: These points may seem like some fairly harsh criticisms, but I hope they're taken in the right way. This puzzle logo is good, but I just think WikiTravel has massive potential, and I'm keen to see it get a logo that will help realise it. There's nothing wrong with aiming for a logo that is just as strong as travel guide brands. (WT-en) Allyak 09:13, 11 Aug 2005 (EDT)
 * 1) The style and colour scheme are dated; it's very late 80's, early 90's.
 * 2) The logo is too busy and won't scale well.
 * 3) The logo is too obvious. The best logos are vague and have strong shapes, but not strong literal visual elements. This is important, because it allows marketers (and the public) to change the logo's meaning over time, so they won't date (i.e. timelessness). Think of the world's biggest brands. How many of them include literal representations of their products? Literal logos (i.e., those that show literal, pictorial representations of their product or key messages) lock you into a fixed brand image that can never be changed, and also have connotations of small businesses. While this usually isn't a bad thing (and I understand the comments above that WikiTravel doesn't need a 'corporate' logo), when it comes to travel guides, this impacts on credibility (see point 5 below).
 * 4) It has, as Socaltransplant notes "a folksy appeal". I agree entirely with that comment, but unlike Socaltransplant I don't see this as a plus, in fact I see this as a drawback. From a branding point of view, the stereotype of the "folksy" (and somewhat 'daggy') traveller is one that might be best avoided for a project as broad-minded, global and dynamic as WikiTravel.
 * 5) Partly because of its 'folksy' nature, and also because of the primary colours and cartoon-eque map symbols, this logo lacks authority. This should be a major goal for branding a travel guide, because the most important element of a travel guide's brand value is its accuracy, reliability and credibility. The main question travel guide consumers ask themselves when faced with multiple travel choices is: "Can I trust this information?" This is made even worse for WikiTravel, that may face the challenging public preconception that a community guide will never be as accurate as one published by professional travel writers.

 * 1) I am a regular Wikipedia contributor, and I love the association the puzzle logo provides.  I love the community pride in the postings on that that site, and this one as well.  The loose similarity of the logos seems appropriate, given the loose similarity of the sites.  While the two are somewhat different, both involve similar expectations of their contributors, and provide similar value to their users.

We must not associate ourselves with Wikipedia! The confusion is not harmless. We often get people who think "oh, this is just like Wikipedia, so I'll copy some intro paragraphs from Wikipedia's Walla Walla, Washington page to start out the Wikitravel Walla Walla article." That is a copyright violation, and must be noticed, verified, and deleted by an editor here. It is rude to copy Wikipedia's stuff in violation of Wikipedia's copyright; we want to do whatever is needed to prevent that. Having a look to the Wikitravel web site which discourages that association in people's minds is a Good Thing. Does a puzzle make you think about Travel? No, it makes you think of Wikipedia. And we should avoid that. We love Wikipedia, and we need to act on that by actively discouraging the unwitting yet improper taking of Wikipedia's hard work. -- (WT-en) Colin 19:22, 11 Aug 2005 (EDT)

 * A puzzle makes me think of putting something together, piece by piece. Drawing people into wikitravel is a good thing, and it far outweighs the risk that someone might inadvertantly copy something they should've. Plus, anyone who stays around wikitravel long enough to actually start a new article will learn how wikitravel is different from wikipedia. And honestly, if wikitravel was supposed to be just like wikipedia, then why would they even been separated? People will find out fast enough that they are different. That's why we have this page and this page. --(WT-en) Comrade009 19:32, 11 Aug 2005 (EDT)

 * This is a travel guide, not a puzzle. Also, I assure you I have deleted accidental Wikipedia-copyvios on MANY MANY occations.  Not all wikipedians notice or read the Welcome to Wikipedians; and we only copy it into their talk page if we have reason to think they might be one, which is rare.  Just the other day User:(WT-en) Luvdapug copied an image from Wikipedia and failed to note the source of the image.  I only noticed because it was suspiciously professional.  So I had the joy of doing the research and checking out the issue.  In this case, the Wikipedia image claims to be in the Public Domain, so it's okay.  But I had to go figure that out myself because the user made an innocent error and thought we were alike enough with Wikipedia for that to be ok.  It's a fine logo Comrade, it's just too easily confused. -- (WT-en) Colin 19:41, 11 Aug 2005 (EDT)

 * "This is a travel guide, not a puzzle"- Is not the pursuit of composing a finer travel guide the combining of different bits and pieces? Is the final product not a combination of different aspects from different people, pieced together to form something cohesive? Does not WikiTravel strive to form a symbiosis between different languages of the guide? Could those different languages be considered parts, when put together creates something much better? If you are so eager to separate this guide from WikiPedia, perhaps you will do something more than change the logo; it's definitely NOT the logo which makes this guide appear affiliated with WikiPedia.--(WT-en) Klestrob44 21:16, 11 Aug 2005 (EDT).
 * I wholeheartedly agree that it would be nice to change more of the look of the site away from Wikipedia style. The old logo, by being round like the Wikipedia logo, also had style-cue issues. -- (WT-en) Colin 22:47, 11 Aug 2005 (EDT)
 * I believe the main reason that people (myself included) associate 'Wikitravel' with 'Wikipedia' is the common use of the title 'Wiki'. If the two groups are totally different, then maybe the working title for 'Wikitravel' should be changed, at first via a link so that the site can still located, then finally dropped altogether. Do I hear the rumblings of the next competition - coining a new name for 'Wikitravel?'...anon

See. In particular: (WT-en) Jpatokal 23:46, 11 Aug 2005 (EDT)

 * No - Wikimedia does not have, nor wishes to have, any trademark on the term "wiki". Ward Cunningham is the first person who used the Hawaiian word wiki to described what we now know as wiki technology and philosophy (IIRC that was in the mid 1990s). He could have created and enforced a trademark on that use but made no move in that direction. So please do not feel that you are infringing on our 'trademark' by using the name 'Wikitravel'.

 * Thanks for the info. It was helpful. However, the current problem is that 'Wikitravel-ers' do not want their site to be confused with 'Wikipedia' (see above comments Evan & Colin: Aug 11), but that will always be the case as long as they share the same prefix in their title, 'Wiki.' In short, it is not the logos that will create the confusion (unless they are idetical or very similar), but the sites similar titles. Don't you agree? Anon

 * I would also change the name of the site, if we could. But I only know one word for user-edited-website: wiki.  I see no way out for that.  But the fewer things that remind people of Wikipedia the better. -- (WT-en) Colin 03:00, 12 Aug 2005 (EDT)

Votes

 * 1) (WT-en) Comrade009
 * 2) (WT-en) Woodstone
 * 3) (WT-en) P.R.
 * 4) (WT-en) Vaergoth
 * 5) (WT-en) zeno
 * 6) (WT-en) CH
 * 7) (WT-en) Stanwiki
 * 8) (WT-en) Socaltransplant
 * 9) (WT-en) Sojourner
 * 10) (WT-en) Mnolf
 * 11) (WT-en) Julien Navarro
 * 12) (WT-en) SophisticatedLady
 * 13) (WT-en) Ralfi
 * 14) Minh Nguyễn
 * 15) (WT-en) jhortman
 * 16) (WT-en) Fluglotse2000
 * 17) (WT-en) jsymmetry
 * 18) (WT-en) Wrh2

Diagonal W
Talk

Comments
I like the idea behind this one a lot, although the implementation needs some work (mostly just being turned into vector image) and the font is not very good. I can see the un-rotated version on the spine of a book, for instance. (WT-en) Jpatokal 23:54, 3 Aug 2005 (EDT)

Yes, it's really slick, and quite pretty. I agree that the text has to change. Of course it doesn't say anything about the wiki process, but that may really not be so much of an issue. -- (WT-en) Mark 04:36, 4 Aug 2005 (EDT)

Oh, and I agree with Jpatokal that it should probably be un-rotated. -- (WT-en) Mark 04:49, 4 Aug 2005 (EDT)

What? It looks much cooler rotated and the text is fine. The text doesn't need to be stylish to look good. (WT-en) Bob rulz 06:27, 5 Aug 2005 (EDT)

 * Regarding the "rotated" perspective view, it makes the rectangle a horizontal surface, i.e., a landscape, and the W is a road. The flat view doesn't have that. -- (WT-en) Paul Richter 02:07, 10 Aug 2005 (EDT)

Text font can be improved (WT-en) AnyFile 15:32, 7 Aug 2005 (EDT)

I like this concept the best, but how about using the font from Owl's logo? (WT-en) Greenman 16:50, 7 Aug 2005 (EDT)

 * If you mean the original mix of "handwriting" and "corroded typewriter" fonts, I don't care for either, especially in logos.(Corroded typewriter is far too overused for "edgy" Gen-X stuff.) And I'm apparently in the minority here, but I don't like the "coolvetica" font that for some reason is being used in both other logos as well as some other first-round ideas. Am I the only person who thinks the "fish-hook t" is atrocious? -- (WT-en) Paul Richter 01:57, 10 Aug 2005 (EDT)

 * I didn't like the handwriting-printed mix either, but I do like Coolvetica, esp. with the more 'adult' capital W as in Mark's latest logo. It's distinctive and a bit funky but still elegant.  The bolded italic Lucida-Condensed-y font in your logo, on the other hand, is too bland and corporate-eighties for me. (WT-en) Jpatokal 02:23, 10 Aug 2005 (EDT)

Clean, clear, attractive. My only negative is that it looks too commercial, I would assume it is for a travel agency, rather than a WikiProject. (WT-en) Eoghanacht 16:04, 8 Aug 2005 (EDT)

 * This is really great, but again, very Latin-1. --(WT-en) Evan 16:06, 8 Aug 2005 (EDT)

 * Interesting way to put it. The "Wikitravel" logotype of course could be localized to any script, and the font choice is flexible too; I just personally prefer modern sanserif fonts for logos. As for the "W", I think that no matter what the language or script, the association of "W" with Wiki is very strong and will still hold. (Wikipedia's favicon is just a serifed "W", in all languages.) And the "W" form is a path that gets bent this way then that way, but in the end follows a straight path -- that's the "Wiki" symbolism in this logo. -- (WT-en) Paul Richter 01:44, 10 Aug 2005 (EDT)

 * To me — and one of the reasons I like this — it's got a blue sky, a green forest, and either a white beach or a road in the middle. And I agree that localizing this is not a problem.  (WT-en) Jpatokal 02:23, 10 Aug 2005 (EDT)

 * Well said, Paul. I've been pretty averse to "W" logos for this reason, but as you point out it also has an ideographic sense. My objections retracted. I'd vote for this one if I wasn't already emotionally attached to the rose below. --(WT-en) Evan 10:24, 10 Aug 2005 (EDT)

Votes

 * 1) (WV-en) ddwiki
 * 2) (WT-en) Gorath99
 * 3) (WT-en) Eoghanacht
 * 4) (WT-en) Carrerdeverdi
 * 5) (WT-en) Pdwerryhouse

Compass Star
Talk

Comments
I haven't read all the pros/cons of this logo, but I'm going with my gut reaction: I hate it. It's boring, and I don't know what it's supposed to convey. -- (WT-en) Jeremy_S

Too generic. Could be a logo for anything, such as beauty supplies or facial tissue. It's not obvious at all that these are compass points.

 * Really? I would tend to think that beauty supplies probably don't have much to do with a compass star. Of course the thing to remember is that the thing the logo represents is more important than the logo, the logo is mearly a mnemonic: The easier it is to remember the better. -- (WT-en) Mark 04:58, 8 Aug 2005 (EDT)

 * You might want to check out this version: Image:Logo_compass_star_shades_of_greyblue.png . -- (WT-en) Mark 05:04, 8 Aug 2005 (EDT)

Pretty versatile logo, as Mark has already demonstrated. You can modify the composition in any way but it still has the same feel. Can be easily adapted for merchandise, the web, fav icons, etc. Good work. --(WT-en) Comrade009 15:52, 3 Aug 2005 (EDT)

Very, very smooth implementation! You've obviously put a lot of thought into it and I like the 2nd row (text on lower right), but for favicon/tiny logos the "w" should be in the same place, not above. The font is also very professional-looking. The only thing I don't like about this is that it's kinda generic, the connection to travel is not that obvious. (WT-en) Jpatokal 23:54, 3 Aug 2005 (EDT)

Thanks for the kind words Jpatokal! The answer to both of your concerns is that this image is meant to be a Compass Star, to be placed on a map. The version with the "w" above would be put on maps, with the "w" for "wiki" replacing the traditional "N" for "North". You are quite correct that there would need to be a small version with a "w" next to the star as well.

To me the fact that the emblem part is a compass star for a map pretty much says travel, as do the fact that you can imagine the two bits travelling through the air. Of course I can totally understand why you might not see it that way.

By the way, as noted above: if the puzzle logo were ultimately selected we could just add the puzzle concept back (and adjusting the colors) into this one and still use it as a compass star in part of a wider branding scheme, especially since the actual logo part (the text) is exactly the same. Get out a copy of a Lonely Planet to see how their logo (mostly type, with a circle) and their Compass Star work together. -- (WT-en) Mark 04:14, 4 Aug 2005 (EDT)

This Logo is a Logo - elegant, good colours, well scalable, big recall value - simply great work. --(WT-en) PhilipP 07:31, 6 Aug 2005 (EDT)

I think this is by far the best logo. It doesn't depend on typography; it has a minimal set of colors; it's pleasant to look at and as Mark showed with some other images we can change the compass parts into paper airplanes and back again. I'd love to see this become the next Wikitravel logo. --(WT-en) Evan 16:08, 8 Aug 2005 (EDT)

 * I forgot to mention: Mark, would it be at all possible to use a capital "W"? --(WT-en) Evan 09:29, 9 Aug 2005 (EDT)

 * You know, I think that is better. Thanks! -- (WT-en) Mark 09:46, 9 Aug 2005 (EDT)

This one does not evoke the idea of travel. The compass star is hardly recognisable as such. It contains way too much text and that will become unreadable at the size a logo should be allotteed on screen. −(WT-en) Woodstone 14:35, 9 Aug 2005 (EDT)

 * Really? OK, read the Paul Rand essay. -- (WT-en) Mark 01:37, 10 Aug 2005 (EDT)
 * I agree that the compass rose, and thus the travel connection, is not obvious. A compass rose itself is not a very common thing, and might even be casually confused with other similar emblems like a Christian cross or a fleur-de-lis which carry a lot of symbolic meaning.
 * However, as a logo, that doesn't bother me much because it stands on its own a a good, solid graphic form -- there's no need to rely too much on overt representational symbolism. And it works well with or without the text. -- (WT-en) Paul Richter 02:25, 10 Aug 2005 (EDT)
 * Yeah, the cross thing bothers me about this design, but it's pretty unavoidable, since the traditional compass star is derived from a star of Bethlehem design which is supposed to forshadow the cross in Christian iconography anyhow. That's the reason I separated the two halves.  Of course adding in NW and SE somehow would help too. -- (WT-en) Mark 04:58, 10 Aug 2005 (EDT)

Just a quick comment: the fact that the colors are shades of blue doesn't really do much to save on printing costs. The cheapest way of printing is spot color, where an image uses three or four total colors, and each ink is printed separately. Getting these shades of blue requires mixing blue ink with other inks, which is more expensive. --(WT-en) Comrade009 21:12, 9 Aug 2005 (EDT)

 * Halftones. This would be done with halftones.  It's true that more spot colors would make it prettier since one could dispense with the halftones, but here you have the option of using just one, or just one plus black. Trust me, I've done this stuff for years. -- (WT-en) Mark 01:37, 10 Aug 2005 (EDT)

The compass logo looks like it belongs to an insurance company. Boring! And let's be honest...if you asked a hundred people what the logo symbolizes, maybe two people would guess a compass...it's not at all intuitive. -- Socaltransplant

By far the best logo on offer. Why? Well, after reading my comments about the puzzle logo above, this entry satisfies many of my requirements: I agree with other comments above that this logo maybe a little boring, but it will serve WikiTravel well, build a strong brand and is open to dozens of variations. (WT-en) Allyak 09:42, 11 Aug 2005 (EDT)
 * 1) It's not too literal. A logo doesn't need to accurately symbolize the product / service it's trying to brand. The Nike Swoosh doesn't look like a shoe and it's arguably the strongest brand on the planet. Great logos don't convey meaning, they evoke feeling. The benefit of a non-literal logo lends credibility, cultural neutrality and timelessness.
 * 2) It's authoritative and suggests credibity. In my comments above I discuss how important this is for a travel guide, and the use of compass star--a symbol usually found on maps--is a clever way to capitalise on the credibiltiy and authority that most people associate with cartographic symbols.

Per my comment above, I think this logo is not nearly as useful as the puzzle one, which captures the Wiki spirit while showing that Wiktravel is different. (WT-en) SophisticatedLady

I think that of the three remaining logos this is definitely the one with the most potential. However, I don't think it's finished and, as far as I know, neither does Mark. Here are my ideas:

 * Mark was quite enthusiastic about the type (based on my handwriting) of my logo which was just pipped by the "W" logo to the second round, so I'd like to see a version containing that text at some point.
 * Green-and-blue (as per the original logo) has a certain power as it is the colour combination people usually associate with the Earth.
 * I'm not happy with the idea of a "W" replacing "N" on maps. "W" could stand for "west" and it is quite possible to see maps with west oriented at the top. Although it would be kind-of fun to have west marked rather than north on all the maps.
 * I really don't like "The Free Travel Guide" -- especially capitalized thus. It's almost identical to WP's slogan. Personally I'd drop that thing altogether and just stick with "Wikitravel".
 * It would be nice to combine this with the success of Comrade009's logo in some way too. I know the Coolvetica was originally inspired from there, but maybe we could use some of the symbols or something.

Good luck, Mark! -- (WT-en) Owl 14:42, 11 Aug 2005 (EDT)

I'm voting for this logo for a couple of reasons: (WT-en) Majnoona 21:51, 15 Aug 2005 (EDT)
 * I like the feeling of motion and "coming together" that I get from the two points-- even if the compass aspect doesn't come across to everyone, arrows/points have a basic feeling of movement and direction that relates well to travel and the development of the guide.
 * It's not too literal. Others have mentioned the fact that the Nike logo doesn't need to be a shoe and I think the same thing applies here.
 * It's versatile. It's the only one that I can imagine on a web site, sticker, book, etc...

Votes

 * 1) (WT-en) Jpatokal
 * 2) (WT-en) jsmorse47
 * 3) (WT-en) Ilkirk
 * 4) (WT-en) Mark
 * 5) (WT-en) Paul James Cowie 02:44, 9 Aug 2005 (EDT)
 * 6) (WT-en) Quirk
 * 7) (WT-en) Sunray Traveller
 * 8) (WT-en) Evan
 * 9) (WT-en) Neil
 * 10) (WT-en) Colin
 * 11) (WT-en) Nicamds
 * 12) (WT-en) 1ur1
 * 13) (WT-en) Berru
 * 14) (WT-en) Owl
 * 15) (WT-en) Allyak
 * 16) (WT-en) Professorbiscuit
 * 17) (WT-en) sportymonk
 * 18) (WT-en) Stavp
 * 19) (WT-en) Russell =/\= 22:17, 13 Aug 2005 (EDT)
 * 20) (WT-en) Pigeonshouse
 * 21) (WT-en) chwalters
 * 22) (WT-en) Majnoona 21:40, 15 Aug 2005 (EDT)


text:
Wikivoyage:Main Page guidelines

The Main Page is the entryway for most casual readers into Wikivoyage. It should show us in our best light, and we've put a lot of thought and work into designing it, to include a mix of gradually-changing information. Editing it directly is usually not necessary, as the Main Page can be updated by editing the corresponding templates.

 * Destination of the Month, Off the Beaten Path and Featured travel topics showcase our featured articles, which are changed every month. These articles are selected in advance at Project:Destination of the Month candidates. If you wish to edit the text or replace the image, please test it first in Main Page/Sandbox.

 * Discover spotlights interesting and often quirky factoids about the places described in Wikivoyage guides. These items are also selected in advance, and added to a queue of upcoming items at Project:Discover. This section is not updated on the Main Page itself, but in a template that is automatically included in the Main Page:
 * Template:Discover

 * Getting involved engages Wikivoyagers to start improving the project. It shows four static links at the left side of the bar, and the Collaboration of the month at the right side. The collaboration of the month is single destination article selected for a focused effort to improve it in some way. Articles are selected in advance at Project:Collaboration of the month. Changing the Collaboration of the month should not be done directly on the Main Page, but is done via this template:
 * Template:Current collaboration

The rest of the Main Page should not be changed without first discussing it with the community. Even if there is community consensus, because of the complexity of the page layout, care should be taken in doing so.

title: Wikivoyage:Main Page guidelines


text:
Wikivoyage:Manual of style

Our manual of style is a collection of rules of thumb and guidelines for giving Wikivoyage a consistent look and feel. Most of these rules have exceptions, but to put together a good reference work collaboratively, it's best to follow the rules unless they're quite inappropriate for a particular situation.

The manual is broken up into different pages so that this page is not overloaded with extraneous text. It makes it easier to find and update individual rules or concepts if they're on their own pages; and it's easier for people to link to particular rules from article talk pages.

If all this stuff makes your head swim, and you don't want to bother with it, by all means plunge forward and just start sharing your knowledge. Other Wikivoyagers will come through and bring your contributions more into line with the style guide.

If you have a question about the specifics of the manual, or want to see it changed/amended/clarified, use the talk page for the section in question. Requests for comment are issues currently being discussed.

Structural style
This section of the manual is for rules about the structure of Wikivoyage as a whole.

 * What is an article? – how and when to start new articles.
 * Other ways of seeing travel – approaching travel from different angles.
 * Geographical hierarchy – how we divide up the world.
 * Article naming conventions – how to name an article.
 * Disambiguation pages – when to make them and how to use them.
 * Bodies of water – how lakes, rivers, seas and oceans fit in.
 * Categories – using the MediaWiki categories feature.
 * Using MediaWiki templates – using the MediaWiki Template: transclusion feature.
 * MediaWiki template index – a list of available MediaWiki templates.

Formatting style
These rules are about the formatting of individual articles—how we take raw information and put it in a format that's easily usable by travellers.

Article layout
 * Article sections – what sort of information each section should contain.
 * Article skeletons – consistent articles. Standard sections and formatting.
 * Information for LGBT travellers – where to put LGBT info in a destination article.
 * Where you can put it – finding a place to share your knowledge.

Formatting content
 * Accessibility – how to make content accessible to people who have a disability.
 * Avoid HTML – avoiding HTML formatting.
 * Avoid long lists – lists of items should usually follow the 7±2 rule.
 * Geocoding – adding latitude and longitude to destination articles.
 * Information boxes – when, how and when not to use information boxes.
 * Section headers – formatting guidelines for the section headers.
 * Wiki markup – how to use the MediaWiki markup to present information.

Links
 * External links – how and when to link to other websites.
 * Internal links – linking to other articles in Wikivoyage.
 * Inter-language links – linking to other language versions.
 * Links to Wikipedia – how to make links to Wikipedia articles.
 * Main Page guidelines – how to add links to the Main Page.

Listings
 * Listings – for including business and attraction listings.
 * One-liner listings – for regions, districts, cities, Go next sections, and other sections as appropriate.

Writing style
This set of rules describes how to write words, sentences, and paragraphs.

 * Abbreviations – when and how to abbreviate.
 * Air travel information – writing about airports, airlines and other air-related information.
 * Avoid negative reviews – don't bother listing places not worth going to.
 * Capitalization – when to capitalize words.
 * Creating emphasis – use boldface for theme words and italics to stress certain words and phrases.
 * Currency – consistent rules for displaying currencies.
 * Don't tout – describe, don't push.
 * Foreign words – using non-English words and names in articles.
 * Measurements – formatting lengths, weights, temperatures, etc.
 * No advice from Captain Obvious – if it's obvious or universally true, there's no point in adding it.
 * Phone numbers – adding and formatting phone numbers.
 * Romanization – for languages that do not use the Latin alphabet.
 * Spelling – what spelling rules to use.
 * Time and date formats
 * Tone – the right tone for your prose.
 * Trademarks – using trademarks.
 * Use of pronouns – avoid using "I" and "we", but "you" is okay.
 * When to use dates
 * Words to avoid – some words and phrases to avoid in articles.

title: Wikivoyage:Manual of style


text:
Wikivoyage:Mapmaking Expedition

 * See also: How to draw static maps, How to use dynamic maps, Regions map Expedition, Geocoding, Dynamic maps Expedition and WV:Lines.

The Mapmaking Expedition is a Wikivoyage Expedition to organize and standardize the maps used in Wikivoyage.

Rationale
The old dull saw says that a picture is worth a thousand words, but when a traveller is trying to find their way around a new city, it's more like a million. A clear and simple map can save hours or even days of hassle.

As with other parts of Wikivoyage, we think that having a coherent map policy will make each map in Wikivoyage more useful. Once a traveller has understood the symbols and conventions of one Wikivoyage map, they can quickly understand a new one.

Goals
The Mapmaking Expedition has the following goals:

 * To define preferred map file formats
 * To outline a map-making collaboration procedure
 * To enumerate different types of maps
 * To suggest guidelines for including maps in articles
 * To create a common map image layout and symbol vocabulary
 * To provide map templates for quickly making new maps
 * To collect mapmaking resources, that is, software tools and information sources
 * To understand map copyright issues and navigate them successfully

File formats
There are two major categories of image file formats: bitmap formats and vector formats. A bitmap format treats an image as a width-by-height array of pixels, each of which has a color. A vector format keeps information about individual parts of the image -- lines, shapes, text, etc. Vector formats tend to be best for computer-generated images -- like Wikivoyage maps. They're also much easier to use for collaborative development -- it's much easier to move a line, a symbol, or some text around in a vector format than in a bitmap format.

There are any number of good vector graphics file formats, and some that are pretty standard for cartography. No vector graphics format, however, is widely supported for Web use. For this reason, we need to maintain two versions of map images: a source version in vector file format, and an output version in a Web-standard bitmap format.

There is one file format that's making serious inroads for Web usage: Scalable Vector Graphics (SVG). Because SVG provides an upward compatibility path to allow us to remove the source-output dichotomy, we prefer SVG as the source format for map files. In case SVG is not available, encapsulated PostScript (EPS) files are a secondary source format.

For on-screen and printed output of maps, the lossless compression of PNG files is preferable. PNG map files are sharp and don't have compression artifacts like JPEG files do.

TLDR: SVG for source, PNG for output. (Yes, it's a long-winded explanation just to come up with 6 words.)

File size
There is no hard-and-fast rule but as a general guideline, try not to make your map image smaller than 2,000 pixels wide.

The preferred size of a single page output file (.png) for printing at Wikivoyage Press is 3008 x 1709 pixels.

Mapmaking procedure
A Wikivoyage mapmaker can and should create maps with whatever drawing tools they have available. When uploading a map, however, two files should be uploaded: the source version in SVG format, and the output version in PNG format. If the mapmaker's drawing tool doesn't support SVG as an output format, they should upload whatever source vector file format they can -- preferably Encapsulated PostScript, or (if necessary) Adobe Illustrator. Other Wikivoyagers with better tools can download the source file, convert it to SVG, and upload that.

The Image page for the output file should have a link to the source file.

Wikivoyagers editing an existing map really, really should work with the source SVG file if possible. After editing the file, they should produce an output PNG file, and upload both files to Wikivoyage.

See also: Project:How to draw static maps (from scratch), Project:How to use dynamic maps (using OpenStreetMap data)

Types of maps
There are several different types of maps that are useful to travellers. Among these are:

 * City street maps. These are simplified maps of the main streets, landmarks, and other important parts of a city, as well as restaurants, bars, and other places listed in the Wikivoyage article for a city.
 * District street maps and District maps. For large cities, it might be useful to split up city street maps into district street maps, and then use a city area map to show how major parts of the city relate to each other.
 * Country or regional railway/road maps. These kind of maps give an overview of travel destinations, passenger railways, other public transport, and/or major roads and thoroughfares between cities or large travel sites.
 * Site maps. These are maps of individual tourist destinations, like archeological or historical places (temple complexes, castles) or large museums.
 * Dive sites are a new development for which there is no consensus policy yet (December 2009). See Diving the Cape Peninsula and False Bay/Pinnacle for an example of a dive site map which was accepted for a Star topic. Other alternatives may be as good or better for a given site.
 * Region maps. These are maps of a country that show the Wikivoyage-defined regions of the country. There could also be region maps showing regions within a region. And so on. There is a specific Wikivoyage expedition for making region maps.

Other kinds of maps may be useful for Wikivoyage and we will try to list them here as we think of them.

Map layout
TBD

Map symbols
One thing that will make our maps more uniform — and therefore easier to create, update, and use — is a library of common map symbols. We have a page with the common map symbols available.

The map symbols should all be SVG files. This makes it easier to incorporate them into maps.

Map templates

 * Templates are available for static district and region maps.
 * Subregion colours are found in the region map template linked above, as well as in the StdColor-template, which also lists their RGB Hex-value.
 * In articles, maps with subdivisions on them are displayed using a Regionlist.
 * Wikivoyage maps use two notable fonts, DejaVu Sans and DejaVu Sans Condensed. Both can be found and downloaded here.

Copyrights
When created, Wikivoyage maps will be released under a free licence, usually Creative Commons' CC-BY-SA. This means that any map put on to Wikivoyage can be used by anybody and changed by a later contributor as needed. With this default licence, all future derivative works will require the same license ("SA": share alike) and proper attribution ("BY"). Accordingly, most Wikivoyage maps will need to be sourced from either public domain sources or sources with a compatible copyright release.

Most map producers and suppliers will take strong exception to their work being copied. Although maps are usually copyrighted, the facts and ideas that maps represent are not subject to copyright laws. If you use an existing copyrighted map as a reference source to make your own maps, be sure that you only use it to extract location data. Your data should be compared to maps from other sources too, as some map makers draw their maps with imperfections, meaning that simply copying a map, even if just tracing it by hand, will also include those imperfections, allowing it to be shown it was sourced from them. Of course, attribute your sources.

At the scale most maps are drawn, even tiny lines represent broad brush strokes over the landscape. Commercial city street maps may overstate the size of roadways and most road maps will overstate a road size. If you are drawing a map it may be more appropriate to simplify and stylize the map rather than make it an exact reproduction of a landscape. This will also lessen the chance of being accused of a copyright violation. If more detail is needed, people can always purchase a detailed map.

See the Talk page for discussion on this issue.

Public domain map sources

 * planiglobe - online map creation. Map generator with world coverage. Customized maps in Postscript and Illustrator versions (vector format) can be downloaded (cc-by-2.5 license). Locations and tracks can be added to a map.

 * Perry-Castañeda Library Map Collection at University of Texas. Most maps in the collection are public domain; copyrighted ones are clearly marked as such.

 * The United States Census Bureau makes their TigerLine map data of the United States available to the public domain. Note that this is raw database information that needs to be manipulated a bit to be of use.

 * The CIA "World Factbook" is public domain, but has mostly bitmapped maps at the country or continent level. There are quite a few maps on Wikivoyage from the factbook; see Project:CIA World Factbook 2002 import.

 * http://www.mapavivo.com.br -- Maps and Routs - Interactive map of South America (Brazil, Argentina, Uruguay, Chile, Paraguay, Bolivia and Peru)

 * nps.gov - The U.S. National Park Service has maps of its properties in various formats, including vector-based PDFs.

 * http://www.dromoz.com/directory/maps/ - public domain static maps, down to street level.

 * BigMap 2 - An open-source tool for exporting high-resolution OpenStreetMap content.

Graphics tools
This section lists some tools for making and editing maps in Wikivoyage's preferred formats. There's a full list of graphics programs that support SVG on the SVG standard site.

 * Inkscape. The main open source vector graphics editor. Produces excellent output in SVG, PNG, Postscript or EPS. This tool is available for Linux (and other Unix variants), Mac OS X, and Windows.
 * Adobe Illustrator. A fairly expensive commercial application, widely used by graphic design professionals, imports and exports SVG. For Windows and Mac OS X only.
 * CorelDRAW. Probably the leading commercial competitor to Adobe Illustrator and also widely used by graphic design professionals. Version 10 or newer can import and export SVG format files. SVG files produced by Coreldraw lose their layers, but are otherwise good conversions with no colour change or other unexpected variations when editing in Inkscape.
 * h n . o r g triggers Wikivoyage's spam detector. I don't know why. So I will munge (#) it: http://phma.h#n.org/Software/azimap.html Azimap, by (WT-en) phma. Converts lat/long coordinate lists to SVG using the azimuthal equal area projection.
 * QGIS. Can export shapefiles, but often makes a real mess of them, especially when multiple layers are involved. For single layer .e00 to .shp it seems to work OK. GPL'd and available for Windows and MacOS and linux.
 * Simple online map editor - fast and simple output in .png format
 * Travegeo (former ShareMap) – online social mapping tool that allows importing data from OpenStreetMap and produces content on CC license. Examples of maps created with ShareMap, see How to draw static maps.
 * Wikivoyage Districtifier - a tool that grabs wikidata regions from the selected area and creates a bunch of Mapshapes out of them.

Map making projects/articles/discussions

 * Converting MapInfo .TAB File to SVG - tutorial article with other interesting links
 * OneMap - Interesting project aims, although its underdeveloped at this stage. see also paper presented at SVGOpen
 * Slashdot article about open maps
 * Un point c'est tout - A wiki-like attempt to build a world mapping database with user contributed points and paths. Most of the site is in French, although the maps themselves are internationalized (you can edit the internationalization).
 * Wikiatlas - project proposal on wikimedia meta-wiki
 * OpenStreetMap - a crowdsourced world mapping project that is open data, licensed under the Open Data Commons Open Database License (ODbL), but the underlying cartography is licensed under the Creative Commons Attribution-ShareAlike 2.0 license (CC-BY-SA). They require you to use the credit “© OpenStreetMap contributors”.
 * MapOSMatic - creates city maps (with index) from OpenStreetMap data.
 * GISWiki on SVG & GIS
 * Gis and Maps on Wikivoyage project
 * Dromoz mapping project - Interesting project aims

title: Wikivoyage:Mapmaking Expedition


text:
Wikivoyage:Maryland Expedition

The Maryland Expedition is a Wikivoyage Expedition to promote and coordinate collaboration to improve Wikivoyage's articles pertaining to the US state of Maryland. 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 a U.S. state is a daunting task. This difficulty is exemplified by the fact that Wikivoyage currently has only one single region article of guide level status! This Expedition exists to to clarify exactly what needs to be done in pursuit of our goals for Maryland and related articles, identify avenues for potential collaboration, and generate enthusiasm towards achieving our goal.

Goals
The main goal of the Maryland Expedition was to achieve Guide status for the Maryland state article. And indeed, after a whole lot of hard work, we reached our goal, making Maryland the first guide-level state in the U.S.!

So what's next? Having reached guide status, Maryland is technically ready for a Destination of the Month nomination, but it would be nice to polish up some of the most important linked destinations—most importantly to get Baltimore and Annapolis up to guide status—before featuring the state on Wikivoyage's main page. So here are a list of tasks:

 * 1) Improve Baltimore to star status
 * 2) Improve Annapolis to guide status, and give it a map
 * 3) Improve Ocean City to guide status.
 * 4) Improve all immediate subregions to guide status.
 * 5) Create maps for all immediate subregions
 * 6) Add more, high quality photos to immediate subregions
 * 7) Make sure all linked destinations from subregion pages have at least one photo

If you can think of some other tasks worth completing prior to a DotM nomination, please add them here!

Baltimore

 * 1) Make Baltimore a star article.

Annapolis

 * 1) Templatize all listings, and add missing basic details, such as addresses, phone numbers, hours, and pricing
 * 2) One drink listing is about 8 two few (minimum)—add some more good recommendations!
 * 3) Ditto buy listings
 * 4) The understand section is unforgivably weak for a city so rich in history and modern-day culture

Article status chart
The following chart shows the current status of all linked destinations. While we are currently merely looking to have a successful and impressive Destination of the Month feature, it's worth keeping in mind that all the destinations below must be at guide status for Maryland itself to become the first star state, and only the second star region on the site!

Expedition members

 * Peter Talk
 * (WT-en) Jonboy Talk
 * (WT-en) Mark Talk

title: Wikivoyage:Maryland Expedition


text:
Wikivoyage:Measurements

We often use measurements in Wikivoyage—for the distances between places, for the altitude of mountains, for the temperature of deserts, for the volume of a glass of beer. This style guideline gives some suggestions for how to specify and format measurements, their units and unit abbreviations.

Note: The abbreviations below are bolded for clarity of exposition, but abbreviations in Wikivoyage articles shouldn't be bolded just because they're abbreviations!

Use local units of measurement
When showing a measurement, use the local system of units for the destination you're describing. This is the system that travelers will see on road signs, local maps, menus, food packages, weather reports, etc.

For almost all of the world, this is the metric system. For the United States of America, it's the U.S. system of units—similar to, but certainly not the same as, the imperial system of the United Kingdom. In some cases, the systems are mixed—for example, in the United Kingdom, road distances are measured in miles and beer served by the pint, while meat and canned goods, for example, are measured in (kilo)grams, and milk is measured in either pints and litres. Wikivoyage needs both accuracy and consistency.

The chief difference between the U.S. system of units and the imperial system is in the sizes of the pint and the gallon. The U.S. measures are often 16% smaller than the Imperial measures. That means you get more drunk on a British pint, and you get fewer miles to the gallon on American roads!

For articles that don't deal with a particular destination (like travel topics), use metric along with U.S. or imperial measures when needed or originally specified (e.g., "No more than 3 oz of liquids or gels may be taken through airport security in the U.S.").

Provide conversions
It's easier for travelers to understand measurements if they're converted to their own system—so try to provide conversions for measurements into both the metric (SI) and U.S. styles.

If the preferred units are metric, try to provide U.S. Standard measurements in parentheses. If the preferred units are U.S. Standard, try to provide metric measurements in parentheses. If for some reason the local unit is neither metric nor US, try to provide first metric, then U.S. (separated by a comma) enclosed in the same parentheses afterwards.

Don't repeat conversions unnecessarily and if you provide a conversion, use only the same number of significant digits as the original measure (these measurements are going to be used by travelers, not scientists).

Possibly the easiest way to provide conversions is to do it automatically using a template, either the compact templates below for specific measurements, such as km or mi, or the more general convert template. E.g. or 2 mi produces 2 mi (and 3.2 km makes 3.2 km). To reduce significant digits you can use the sigfig parameter: 5 km gives 5 km.

Sometimes it may be better to use a different unit rather than relying on automatic conversion; for example, Pudong mentions "four buildings over 400 m, a quarter mile high" which may be clearer than "400 m (1320 ft)".

Some numbers do not have convertible units but may be made clearer by a comparison; for example the Fujian article gives the population as "37 million, which is small for a Chinese province (17th of 23) but about the same as Canada, Poland or California."

Avoid orphaned units
Except for measurements of temperature and voltage, we have a mild preference for separating the number from its associated unit by a single space, but:

 * Don't go wild copy editing different formatting
 * To avoid the unit of measurement that "belongs" to a measurement being "orphaned" from its associated unit when it wraps to a following line, separate the pair with a non breaking space character " " rather than a simple space, eg: " " will display 4500 km. You can also use the template nowrap to achieve the same, e.g.:  (include any appended punctuation, to prevent a line break in-between).

Periods and commas
Since this is the English-language version of Wikivoyage, a full stop or period should be used separating any decimal fraction of a number and not a comma, whatever the local practice is, i.e. 10.75, not 10,75.

For similar reasons, never use a full stop or period as the delimiter to separate groups of three numerals left of the decimal point. Use a comma for this purpose instead, i.e. 10,000, not 10.000.

Fractions
It's okay to use fractions for expressing numbers, e.g. for hours or for measurements in the Imperial/U.S. system, but fractions should not be used for measurements in the metric system. Because fractions can be more difficult to read, it is best to stick with the most common, i.e., ½, ¼, and ¾, and use decimals for other numbers, e.g.,
 * 1½ hours, 2¼ miles,
 * But: 1 hr 20 min, 3.5 km, 1 ft 8 in (instead of 1⅓ hr, 3½ km, 1⅔ feet or 1' 8")

Examples
The following are examples of good practice.

 * It's 2,800 mi (4,500 km) from Los Angeles to New York City.
 * It's 815 km (506 mi) from Paris to Marseille.
 * Pikes Peak is 14,110 ft (4,301 m) high.
 * Mount Fuji is 3,776 m (12,388 ft) high.
 * Temperatures in Death Valley routinely hit 110°F (43°C).
 * In winter, Iqaluit gets down to -50°C (-58°F).
 * 5 km (3 mi) to the north is a national park. 5 km to the south is a lake.

However, consider if you can make the prose just as clear to a traveller while avoiding unit conversions.

 * Winter temperatures at night in Canberra can drop below freezing, but snow is rare.
 * The walk to the lake will take around 30 minutes and involves climbing around 30 stairs.

Area
Always abbreviate units in listings. Do not put periods (full stops) after units. Never use an "s" after a unit abbreviation to make it plural. Don't capitalize the first letter of any of the base units below.

 * square meter = m²
 * square kilometer = km²
 * hectare = ha

 * square foot = ft²
 * square yard = yd²
 * square mile = mi²
 * acre = acre

Examples

 * or  – will show as :
 * – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  or   – will show as :
 * or  or   or   – will show as :

Duration
Always abbreviate units in listings – outside the "content" tab that is. Do not put periods (full stops) after units. Never use an "s" after a unit abbreviation to make it plural. Never capitalize the first letter.

 * year = yr (rarely used in abbreviated form)
 * week = wk (rarely used in abbreviated form)
 * hour = hr
 * minute = min
 * second = s or sec

Electrical

 * alternating current = AC
 * direct current = DC
 * ampere(s) or amp(s) = A
 * volt(s) = V
 * cycles per second = Hz

Length
Always abbreviate metric units in listings. Do not put periods (full stops) after units. Never use an "s" after a unit abbreviation to make it plural. Don't capitalize the first letter of any of the base units below.

 * kilometer = km
 * meter = m
 * centimeter = cm
 * millimeter = mm

 * mile = mi
 * yard = yd
 * foot = ft
 * inch = in

Do not use quotation marks (' or ") to signify feet or inches; that would confuse some readers.

Spell nautical miles in full, because some abbreviations, including "nm", conflict with abbreviations for other units (eg. nanometres in the metric system).

Examples

 * "the trail is long" and "it's an  trail"
 * "the trail is long" and "it's an  trail"
 * or  or   – will show as :
 * or  or   – will show as
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * – will show as :
 * – will show as :

Speed
Show as km/h or mph, not kmh-1, kmph or mi/h.

Examples

 * or  – will show as :
 * or  – will show as :
 * The latest Boeing 787 Dreamliner has a cruising speed of Mach 0.85 (913 km/h, 567 mph) at 10,700 m (35,000 ft)

Temperature
Always abbreviate units in listings.

 * Celsius = degrees Celsius or °C (Don't use the name "centigrade" which was officially deprecated in 1948.)

 * Fahrenheit = degrees Fahrenheit or °F

When referring to places inside the United States, show temperatures in Fahrenheit first followed by Celsius in parentheses. Anywhere else, use Celsius first with Fahrenheit in parentheses.

If the prolix prose form is not chosen, temperature ranges should be shown in this form: −3 °C to 26 °C (rather than "-3°C - 26°C" or "-3°- 26°C")

Once you choose a temperature format, use that format throughout the article. Do not switch back and forth.

Examples

 * or  – will show as:
 * or  – will show as:

Volume
Always abbreviate units in listings. Do not put periods (full stops) after units. Never use an "s" after a unit abbreviation to make it plural. Don't capitalize the first letter of any of the base unit abbreviations below (except for the liter = L).

Dry volume

 * cubic meter = m³
 * cubic centimeter = cm³, or equivalently mL

If you cannot get the ³ on your keyboard, then use 3 which produces a 3.
 * cubic foot = ft³ or cu ft
 * cubic yard = yd³ or cu yd

Fluid volume

 * liter = L
 * milliliter = mL
 * hectoliter = hL

(In order to avoid confusion with the numeral 1 and letter l, L is always capitalized when used as an abbreviation for liter.)

 * pint = pt
 * quart = qt
 * gallon = gal

Weight/mass
Always abbreviate units in listings. Do not put periods (full stops) after units. Never use an "s" after a unit abbreviation to make it plural. Don't capitalize the first letter of any of the base units below.

 * metric ton (US) or tonne (UK) (1000 kg) = t (not Mg)
 * kilogram = kg
 * gram = g
 * milligram = mg

 * hundredweight [100 lb (U.S.) / 112 lb (U.K.)] = cwt
 * short ton (U.S., 2000 lb) / long ton (U.K., 2240 lb) = ton
 * pound = lb
 * ounce = oz

Examples

 * or  – will show as :
 * or  – will show as :
 * or  – will show as :
 * or  – will show as :

title: Wikivoyage:Measurements


text:
Wikivoyage:Microformats

Microformats are a loose group of standards for adding simple markup to human-readable data items such as events, contact details or locations. The information in web pages that follow the standards can be extracted by software and indexed, searched for, saved, cross-referenced or combined. More technically, they are items of semantic markup, using just standard (X)HTML with a set of common class-names. They are open and available, freely, for anyone to use.

Since microformats depend on particular (X)HTML elements and attributes, it's not - yet - possible to implement them in basic Wiki syntax. However, some of our MediaWiki extensions do or will support microformats for output.

hCard
hCard is used to mark up contact details for people, organizations or venues (i.e hotels, shops, pubs, museums, etc.). and can be extracted as a vCard. The new Project:Listings implement hCard. For examples, see Birmingham (England), Cincinnati or Singapore/Sentosa.

rel-license
The rel-licence microformat is already used on every page on Wikivoyage.

Future

 * Project:Listings will support rel-tag for tagging listings
 * Project:Geocoding will support geo for lat-long data for destinations.
 * Project:Listings will support geo for lat-long data for individual attractions

If you have suggestions for other ways to implement microformats on Wikivoyage, please discuss on the Talk page.

title: Wikivoyage:Microformats


text:
Wikivoyage:Archive of Wikitravel (not Wikivoyage) milestones

Wikitravel is a growing concern -- as a project and as a travel guide. This page is for recording some milestones in Wikitravel's history (or future), and for setting up some milestones along the way of where we want to go. It's for gauging our progress, looking forward and looking back.

Figures below refer only to the English version of Wikitravel.

Web site

 * Domain name registered : February 19, 2003
 * MediaWiki software installed and operational : July 24, 2003
 * First major crash: Database crashed February 20, 2004

Articles

 * First article : Main Page, July 24, 2003
 * 100th article : ? (sometime in early August, 2003)
 * 1,000th article : North Dakota, January 16, 2004
 * 2,500th article: Chichester, September 23, 2004
 * 5,000th article: Suzdal, August 3, 2005
 * 10,000th article : Loveland (Ohio), July 12, 2006
 * 50,000th article (across all language versions) : Khancoban, August 20, 2009
 * 50,000th article (English) : ?
 * 100,000th article : ?
 * Last CIA World Factbook 2002 disclaimer removed from a country article: June 5, 2006
 * Every UNESCO World Heritage Site covered: ?

Users

 * First user : July 24, 2003
 * 100th user : November 7, 2003
 * 500th user : April 15th, 2004
 * 1000th user : November 4th, 2004
 * 5000th user : March 20th, 2006
 * 10,000th user : November 2006

Usefulness

 * First report of someone using Wikitravel article(s) for travel : Talk:Taiwan/Archive 2003-2010, September 23rd, 2004
 * First report of someone using Wikitravel article(s) exclusively for travel : "I think printing out excerpts from wikitravel and bring them along from the trip should suffice.", March 28, 2006
 * First paper publication of a Wikitravel article : ?
 * First inclusion of Wikitravel content in a paper travel guide : JetAway magazine, Issue 5 (May/June 2006), "JetStar Asia Destinations" pp. 60-68
 * First travel guide with only Wikitravelcontent : Wikitravel Singapore by Wikitravel Press, soft launch November 2007, public launch February 2008
 * First violation of the Wikitravel copyleft : Detected March 29th, 2004, see Project:Non-compliant redistribution
 * First #1 Google hit : Apo Kayan, See, Detected April 21st, 2004

Popularity

 * First blog entry about Wikitravel : Logical Disconnect, August 15, 2003
 * First Slashdot article mentioning Wikitravel : Wikipedia Criticised by Its Co-founder, January 5, 2005 (indirect reference)
 * First mainstream press article about Wikitravel : The Hindu ("India's National Paper"), September 15, 2003
 * First external Web site about Wikitravel (e.g., "ihatewikitravel.org") : ?


text:
Wikivoyage:List of content re-users

This is a list of some sites that re-use our travel content, with comments on their implementation.

Mobile readers

 * OxygenGuide is just Wikivoyage offline, as interlinked HTML files for use without Internet. On Android, clicking on a listing opens your GPS/navigation app (such as OsmAnd) to take you there.

Mashups

 * Mapcarta is a mashup of Google Maps, Panoramio, Google Places, GeoNames and Wikivoyage.

Link providers

 * Wikipedia refers its readers to Wikivoyage for travel information. Both of us are hosted by the Wikimedia Foundation.
 * Tripline allows users to create, share and find maps with travel routes.

title: Wikivoyage:List of content re-users


text: Wikivoyage:Multilingual statistics

title: Wikivoyage:Multilingual statistics


text:
Wikivoyage:Namespace index

This page intends to act as an index to meta pages in Wikivoyage. The Wikivoyage: namespace contains mostly meta pages, while the Main namespace contain mostly non-meta travel guide pages.

Administration

 * Project:Bug reports and feature requests
 * Project:Links to disambiguating pages
 * Project:List of common misspellings
 * MediaWiki:Spam-blacklist
 * MediaWiki:Spam-whitelist
 * Project:Map sources

Collaboration

 * Project:Collaboration of the month
 * Project:Community portal
 * Project:Destination of the month candidates
 * Project:Discover
 * Project:Previous collaborations
 * Project:Protected pages
 * Project:Requests for comment
 * Project:Requests for images
 * Project:Requests for phrasebooks
 * Project:Requests for maps
 * Project:Script nominations
 * Project:Star nominations
 * Project:Travellers' pub
 * Project:Travellers' pub archives
 * Project:User ban nominations
 * Project:User rights nominations
 * Project:Vandalism in progress
 * Project:Votes for deletion
 * Project:Votes for undeletion

Expeditions

 * Project:Expeditions
 * Project:Language Expeditions

Language Expeditions

 * Project:Chinese Wikivoyage Expedition
 * Project:Danish Wikivoyage Expedition
 * Project:Dutch Wikivoyage Expedition
 * Project:Esperanto Wikivoyage Expedition
 * Project:Finnish Wikivoyage Expedition
 * Project:French Wikivoyage Expedition
 * Project:German Wikivoyage Expedition
 * Project:Hebrew Wikivoyage Expedition
 * Project:Hungarian Wikivoyage Expedition
 * Project:Italian Wikivoyage Expedition
 * Project:Japanese Wikivoyage Expedition
 * Project:Korean Wikivoyage Expedition
 * Project:Lithuanian Wikivoyage Expedition
 * Project:Norwegian Wikivoyage Expedition
 * Project:Polish Wikivoyage Expedition
 * Project:Portuguese Wikivoyage Expedition
 * Project:Romanian Wikivoyage Expedition
 * Project:Russian Wikivoyage Expedition
 * Project:Spanish Wikivoyage Expedition
 * Project:Swedish Wikivoyage Expedition

Geographic Expeditions

 * Project:Florida Expedition
 * Project:Maryland Expedition
 * Project:Poland Expedition

Other Expeditions

 * Project:Access Expedition
 * Project:Business listings reliability Expedition
 * Project:Country surgeon Expedition
 * Project:Dynamic maps Expedition
 * Project:Education Expedition
 * Project:Fellow traveller Expedition
 * Project:Mapmaking Expedition
 * Project:Offline reader Expedition
 * Project:Regions map Expedition
 * Project:Search Expedition
 * Project:Tourism Bureau Expedition
 * Project:World Heritage Expedition
 * Project:Writers' Expedition

General info

 * Project:About
 * Project:FAQ
 * Project:Help
 * Project:Wiki

For new users

 * Project:Graffiti wall
 * Project:Jargon
 * Project:Quick contribution guide
 * Project:Tips for new contributors
 * Project:Ways to help Wikivoyage
 * Project:Ways to promote Wikivoyage
 * Project:Welcome message
 * Project:Welcome, business owners
 * Project:Welcome, newcomers
 * Project:Welcome, tourism professionals
 * Project:Welcome, Wikipedians
 * Project:Why register

How to

 * Project:How to
 * Project:How to add an image
 * Project:How to create a user account
 * Project:How to delete a page
 * Project:How to describe yourself
 * Project:How to draw static maps
 * Project:How to use dynamic maps
 * Project:How to edit a page
 * Project:How to merge two pages
 * Project:How to redirect a page
 * Project:How to rename a page
 * Project:How to revert a page
 * Project:How to start a new page
 * Project:Wiki markup

Software help

 * Project:Recent changes help (redundant? remove?)
 * Project:Recent changes patrol
 * Project:Software features
 * Project:User email help
 * Project:User page help
 * Project:Using talk pages

Links

 * Project:Inter-language links
 * Project:Internal links
 * Project:Links from Wikipedia
 * Project:Links to Wikipedia
 * Project:Sister project links

Article skeleton templates

 * Project:Article skeleton templates
 * Project:Big city article template
 * Project:Continent article template
 * Project:Country article template
 * Project:District article template
 * Project:Diveregion article template (should be created?)
 * Project:Divesite article template (should be created?)
 * Project:Huge city article template
 * Project:Itinerary article template
 * Project:Park article template
 * Project:Phrasebook article template
 * Project:Region article template
 * Project:Small city article template
 * Project:Travel topic article template

Quick article templates

 * Project:Quick big city article template
 * Project:Quick continent article template
 * Project:Quick country article template
 * Project:Quick district article template
 * Project:Quick huge city article template
 * Project:Quick itinerary article template
 * Project:Quick park article template
 * Project:Quick phrasebook article template
 * Project:Quick region article template
 * Project:Quick small city article template
 * Project:Quick travel topic article template

Sections

 * Project:Article skeleton templates/Sections
 * Project:Section headers

Listings

 * Project:Listings

Article status

 * Project:Article status
 * Project:City article status
 * Project:Country article status
 * Project:Dive guide article status criteria
 * Project:Itinerary status
 * Project:Park article status
 * Project:Phrasebook status
 * Project:Region article status
 * Project:Travel topic status

Status ratings

 * Project:Guide articles
 * Project:Outline articles
 * Project:Star articles
 * Project:Star potential
 * Project:Stub articles
 * Project:Usable articles

Roles within the community

 * Project:Administrators
 * Project:Bureaucrats
 * Project:Autoconfirmed users
 * Project:Docents
 * Project:Hierarchy
 * Project:What is a docent?

Route icons

 * Project:Route icons
 * Project:Routebox navigation
 * Project:United States route icons

Recognizing contributors and articles

 * Project:Barncompasses
 * Project:Celebrate a contribution
 * Project:Destination of the month

Miscellaneous

 * Project:Administrator's handbook
 * Project:Babel
 * Project:Categories
 * Project:Comments in image files
 * Project:Field research checklist
 * Project:Geocoding
 * Project:Geographical data and metadata
 * Project:Image resources
 * Project:Information boxes
 * Project:Maintenance panel
 * Project:Microformats
 * Project:Non-administrator tasks
 * Project:Related articles
 * Project:RSS feed
 * Project:Shortcuts
 * Project:Spam filter
 * Project:Start a new guide
 * Project:Template index
 * Project:What is a dive guide?
 * Project:WikiNode (lost its purpose?)

Policies and guidelines

 * Policies

Guiding principles

 * Project:The traveller comes first
 * Project:Goals and non-goals
 * Project:Consensus
 * Project:Plunge forward

Core content policies

 * Project:Be fair
 * Project:Don't tout
 * Project:Tone

Unwanted edits

 * Project:How to handle unwanted edits
 * Project:Edit war

Linking

 * Project:External links

Specific community policies

 * Project:CheckUser
 * Project:Cross-identification of accounts
 * Project:Deletion policy
 * Project:Image policy
 * Project:Keep Wikivoyage fun
 * Project:No real world threats
 * Project:Protected page policy
 * Project:Sock puppets

Cooperating with other websites

 * Project:Cooperating with OpenGuides
 * Project:Cooperating with Wikia Travel
 * Project:Cooperating with Wikipedia

Infrastructure and software

 * Project:Avoid HTML
 * Project:Script policy
 * Project:Technical infrastructure policy (historical, obsolete)
 * Project:Using Mediawiki templates

Terms of use

 * Project:Cookies
 * Project:Disclaimer
 * Project:Living persons

Licencing and redistribution

 * Project:Copyleft
 * Project:Copyright-related issues
 * Project:Database dump
 * Project:Dual licensing
 * Project:Full text of the Attribution-ShareAlike 3.0 license
 * Project:Full text of the GNU Free Documentation License, Version 1.2
 * Project:How to re-use Wikivoyage guides
 * Project:License upgrade
 * Project:Non-compliant redistribution
 * Project:Non-free content (under discussion)
 * Project:Why Wikivoyage isn't GFDL

Hierarchy of travel guides

 * Project:Breadcrumb navigation
 * Project:Geographical hierarchy
 * Project:Other ways of seeing travel

Creating travel guides

 * Project:What is an article?
 * Project:Bodies of water
 * Project:Destinations (should be created?)
 * Project:Disambiguation pages
 * Project:Itineraries
 * Project:Phrasebooks (should be created?)
 * Project:Travel topics (should be created?)
 * Project:Naming conventions

Travel guide content policies

 * Project:Avoid negative reviews
 * Project:Sex tourism policy
 * Project:Illegal activities policy
 * Project:Information for LGBT travel
 * Project:When to use dates

Pages that are not travel guides

 * Project:Main Page guidelines

Manual of style

 * Project:Manual of style

Structure of travel guide articles

 * Project:Avoid long lists
 * Project:Climate (should be created from Climate Expedition guidelines?)
 * Project:Maps (should be created from Mapmaking Expedition and How to draw a map guidelines?)
 * Project:One-liner listings
 * Project:Where you can stick it

Writing style

 * Project:Abbreviations
 * Project:Creating emphasis
 * Project:No advice from Captain Obvious
 * Project:Use of pronouns
 * Project:Words to avoid

Language

 * Project:Foreign words
 * Project:Pseudo-phoneticization guide
 * Project:Romanization
 * Project:Spelling
 * Project:Trademarks

Numbers and dates

 * Project:Currency
 * Project:Measurements
 * Project:Phone numbers
 * Project:Time and date formats

Other

 * Project:Language version policy
 * Accessibility

Showcase articles

 * Discover
 * Previously Off the beaten path
 * Previous Destinations of the month
 * Previous Featured travel topics
 * Star articles

Site

 * Project:Bad jokes and other deleted nonsense
 * Project:Badges
 * Project:Cleanup
 * Project:Get-together
 * Project:IRC channel
 * Project:Joke articles
 * Project:Language versions of Wikivoyage
 * Project:List of content re-users
 * Project:List of related projects
 * Project:List of Wikivoyagers by location
 * Project:Migration to Wikimedia
 * Project:Not an article
 * Project:Press coverage
 * Project:Requests for username change (defunct)
 * Project:Syntax checks
 * Project:Top destinations lists
 * Project:User account migration (defunct)
 * Project:WikiSherpa (defunct)
 * Project:Wikitravel Press (defunct)
 * Project:World cities

Statistics and milestones

 * Project:Awards
 * Project:Celebrate a contribution
 * Project:Milestones
 * Project:Multilingual statistics
 * Project:Technical details

Help

 * Project:How to add travel news
 * Project:Tags
 * Project:RDF
 * Project:Turtle RDF

Expeditions

 * Project:Climate Expedition
 * Project:Cultural Expedition
 * Project:News Expedition
 * Project:Phrasebook Expedition
 * Routes Expedition
 * Project:RDF Expedition
 * Project:RDF Expedition Collection of wanted features
 * Project:RDF Expedition Defining templates
 * Project:RDF Expedition Example for index
 * Project:RDF Expedition Example 2 for index
 * Project:RDF Expedition Representation of Information

Site

 * Project:10K Party
 * Project:Archive of Wikitravel (not Wikivoyage) awards
 * Project:Archive of Wikitravel (not Wikivoyage) milestones
 * Project:Archive of Wikitravel (not Wikivoyage) press coverage
 * Project:Archive of Wikitravel (not Wikivoyage) logo contest
 * Project:Archive of Wikitravel (not Wikivoyage) logo contest entries
 * Project:Archive of Wikitravel (not Wikivoyage) logo contest results
 * Project:Archive of Wikitravel (not Wikivoyage) logo voting page
 * Project:CIA World Factbook 2002 import
 * Project:Scheduled downtime
 * Project:Table of contents location
 * Project:TourBusStop

Logbook

 * Project:Logbook
 * Project:Logbook archives

Go-between reports

 * Project:Go-between reports
 * Project:Go-between reports/German/German Wikivoyage Report for 2 July 2006
 * Project:Go-between reports/German/German Wikivoyage Report for 23 February 2006
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 7 December 2005
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 17 January 2006
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 3 March 2006
 * Project:Go-between reports/Japanese/Japanese Wikivoyage Report for 18 June 2006
 * Project:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 2 April 2006
 * Project:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 2 March 2006
 * Project:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 2 May 2006
 * Project:Go-between reports/Portuguese/Portuguese Wikivoyage Report for 5 June 2006
 * Project:Go-between reports/Swedish/Swedish Wikivoyage Report for 18 December 2005
 * Project:Go-between reports/Swedish/Swedish Wikivoyage Report for 22 January 2006
 * Project:Go-between reports/Swedish/Swedish Wikivoyage Report for 23 February 2006
 * Project:Go-between reports/Swedish/Swedish Wikivoyage Report for 19 April 2006

title: Wikivoyage:Namespace index


text: Wikivoyage:Namespaces

title: Wikivoyage:Namespaces