# writing style USE-IT’s style is like speaking to a foreign friend. USE-IT explains things the way they are – it’s that simple. No difficult words, no promotional blah blah, no exaggerations, no poetry. A golden rule: if the text does not sound natural when you read it aloud, it’s not a good USE-IT text. ## Concrete Our texts give information that young travellers need. The reader should know what it’s about. That sounds logical, but haven’t you sometimes read brochures that tell you how wonderful everything is without really giving information? If you write “cool bar with great music” or “open-minded place for all kinds of cultural events”, that might be true, but nobody knows what you mean. What is cool? What kind of music? Can you give an example of past events? What’s the typical crowd? It’s never easy to define a place, but nobody will go there anyway if you stick to the clichés.

Chemnitz

Esch-sur-Alzette

Nantes

## Visual USE-IT texts include details that can actually be ‘seen’ when somebody reads the text, or ‘heard’, ‘smelled’, ‘tasted’ or ‘felt’.

Ghent

Nijmegen

Graz

## Informative We do not make critical evaluations. It’s not about saying which place is good and which one sucks. Basically, if it sucks: don’t include it. Just give a clear description so that people who would like it will know. After all, who are you to decide? A metalhead expects something else from the city than a couple of lovers, who also expect something else than a group of five backpacking friends. Don’t give one- to five-star ratings, just inform clearly.

Esch-sur-Alzette

Tromso

Graz

## Practical Don’t forget to include practical tips and be detailed about them. Taking a train isn’t hard as a local, but as a traveller, it can be challenging. Give as much practical info as you can.

Chemnitz

Prague

Nijmegen

## Smart USE-IT conveys local history and the stories behind places. Invite a historian, a sociologist and an architect to join your team! Our maps are more than simple fun, it’s about the character of your city, which is always grounded in history. Do your research well! Also, ask around. If you’re not gay, ask a gay friend. If you’re not into techno, ask a clubber. Etc.

Ghent

Warsaw

Prague

## Young USE-IT writes in a young style for a young audience. Don’t write in hiphop slang, but don’t be too formal either.

Esch-sur-Alzette

Nantes

Warsaw

## Funny and True Keep in mind that the best joke is the one that is actually true. Stating a fun fact is better than inventing a silly joke. Also, don’t exaggerate. Is it really “gigantic”, “unbelievable” or “spectacular”? Really? These are words to use rarely. Before you know it, your text will sound like a tourist brochure. Just write as if you were speaking to a friend and your texts will feel more real. And please take it easy on the exclamation marks. (!!!!!!!!). They usually make jokes less funny and make facts less surprising. Or worse: they make you sound like the marketing department. Oh and: no smilies or emojis please. You don’t need them.

Brussels

Tromso

Tillburg

## Up-to-date USE-IT maps are updated every 18 months and include the talk-of-the-town. Which area is hipsterizing? Which bar burned down and started a crowdfunding campaign to rebuild? Many spots could never be described the same way on last year’s map or next year’s map.

Arhnem

Warsaw

Nantes

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://use-it.gitbook.io/use-it-wiki/editorial-style-guide/writing-style.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.