Write for Digital Energy Journal

We very much welcome articles and press releases from the industry - please send press releases and article ideas to Karl Jeffery, editor on jeffery@thedigitalship.com.

You can see our plans for 2007 in our media pack, Click here to download it.

The kind of articles we are looking for is different to other publications in our market - we do not see ourselves as a purely technical journal, and particularly welcome articles about how technology is being used in the oil and gas industry, and who is using it.

We think that visual appeal / readability of the magazine is very important, and so would prefer articles which are clearly written without jargon and without too many acronyms, and written at a level that an oil and gas executive without any specific IT knowledge would be able to follow easily whilst on an aeroplane.

Photographs are very welcome because they improve the visual appeal.

Other editorial requirements / suggestions:

The articles must also be specifically about upstream oil and gas information and communications technology.

We prefer not to publish powerpoint slide - type diagrams, because they make our pages look like a technical report and turn off the readers, and also often get messed up when we change the size of them, and their contents can often be adequately explained with a few words.

We certainly want plenty of photographs, to put on our front cover and all of our pages, to attract reader's attention.

We will delete any unsubstantiated claims, buzzwords, 'trademark' symbols and make other changes as we see fit to ensure readibility. We will delete any efforts to put in specific words in the article as many times as possible because this is something you want to emphasise for marketing purposes (eg 'real time').

A good length for a meaty article is around 1200 words - long enough to get into a meaty subject, but not so long that no-one reads the whole thing. It can be shorter or longer than this though, depending on how interesting it is.

Articles should be about a recent development, not written in a non-time sensitive, 'what was done' classic technically report style.