We believe that ideas are important to share, which is why we promote guest contributions to The Urbanist. Many of our most interesting articles come from readers like you, and people deserve to read what you have to offer. If you’re interested in sending us an article to publish, we encourage you to contact our editors at editorial[at]theurbanist[dot]org to get their feedback before jumping into deep. If we think the topic and article is a fit, we will work with you to get it published with a byline under your name.
We have some general guidelines for writing articles. Following these will help ensure that we will accept your article for publishing. In some cases, we may publish an article that doesn’t meet all of the following criteria.
- Keep it short. Most articles should be in the range of 400 to 1,200 words. You should strive to make a single point, which will help keep length down. The longer an article is, the less likely that people will read it. Of course, there are plenty of circumstances where a long article makes sense like when presenting data or an in-depth story–and we will accept these.
- Know how to write in plain English. Stick to short and simple sentences and phrases. Long and technical ones can easily confuse readers. Avoid using jargon and abbreviations, but if you must, always explain these through context or giving the reader something to start from. Many people probably know what SDOT (Seattle Department of Transportation) is, but don’t assume they do; write it out and then abbreviate. Choose an active writing style, it will keep your reader glued to the next sentence. While we don’t have any particular manual of style, nor require one, Wikipedia has an excellent guide if you’re looking for one to use.
- Don’t stifle dialogue. Our Comment Policy outlines the best ways to share ideas that are positive and inclusive to community discussion.
- Always be truthful. We fact check guest articles to ensure that the information being shared derive from reputable sources. We will not publish something that we believe is false. Occasionally, incorrect information does make it to print unintentionally, and when this occurs, we correct the record.
- Be realistic with a proposal. If you have a proposal in mind to change specific public policies, plans, or services, you ought to make sure that it isn’t completely pie-in-the-sky. If you want the proposal to be taken seriously, you’ll need to do your homework to show that proposal is innovative, reasonable, and/or implementable.
- Stick to one topic and one point. Doing this makes it easy to argue your point and gives clarity to readers. If you have a number of related points on a topic, it may be better to consider a series of articles as opposed to trying to fit it all into one.
- Make it new. Original ideas are always the best; they are interesting and give readers something new to think about. Of course, building off of the ideas of others, or re-presenting a current issue or news story is great, too, so long as it is original.
- Consider counter-arguments. No matter how interesting or compelling the argument you intend to make is, you should consider addressing counter-arguments. If you there are glaring arguments that could be made against your case, you are better off addressing them up front than leaving them to the reader to gnaw on and pick at.
- Provide a featured image and short bio. Every article requires a featured or title image. As an author, readers want to know who you are. A short bio of two or three sentence should do.
- Other images. If you have photos in mind, please send them as attachments or provide a link to the photo. We generally only accept photos that are of author origin, in the public domain, or that have a Creative Commons license. Named photos are greatly appreciated over “image2.png”. A caption is recommended.
While we have a general set of formatting techniques, we’re very flexible with how you choose to format your article. We’re happy to take articles through a number of mediums like e-mail text, shared Google Docs, or a Word document. While plain text with html is a nice-to-have, it isn’t required nor expected.