Standard of English

We expect the standard of English in submitted work to be very high; certainly that of a native English speaker. Please do not waste your time and ours if you cannot submit work to that standard.

Exclusivity

Articles must be exclusive to The Stack, and stay exclusive – except by prior arrangement.

This does not apply to print. We can re-use existing print material that has not been online before, and have no problem with Stack-featured work being re-used for print.

Appropriate tone and style

The tone of articles should be aimed at a tech-savvy audience, not a general consumer audience unfamiliar with basic technology themes. A ‘Wikipedia’ feature that prognosticates vaguely about a subject, is unlikely to generate as much interest as a feature which gets down to tech specifics and really digs into a target topic.

Please also avoid business-style conventions such as bullet points. If you need to list a number of things, give each one a simple heading instead.

Suitability for The Stack

Articles need to cover topics that are clearly within the Stack’s remit.

About that link you would like included…

We expect that you have at least one link that you want to include; it should be a straight link without URL hooks (i.e. http://mysite.com NOT http://mysite.com?ref=campaign etc.). Hooked URLs risk our SEO, and we can’t run them.

Your target link, if any, must relate to your topic. We cannot accept an interesting article on home networks that needs to contain an irrelevant link to a frame manufacturer, etc.

Author biography

These articles are prefaced by a paragraph’s worth of author bio, where the company link will be included (it is not ‘nofollowed’); for the author image we will need a headshot, and ideally the writer should supply a bio.

Article length

We wouldn’t expect a worthwhile feature to come in at less than 700 words – this length would require dense and concise writing to really deliver any value. Somewhere around 850-1000 words is ideal.

Reasonable neutrality

(If you have a very good reason to write entirely about your company’s own work – i.e. you’re a developer writing about your own project – the following does not apply, naturally.)

The central topic of the article is bound to touch on the expertise of the writer’s company, but should be of general interest to readers – this doesn’t preclude examples from the company’s own sites and work, but the piece can’t become manifestly self-promotional.

Editing your submission

We reserve the right to change the titles and add section headings and images as necessary to make the piece as marketable and presentable as possible. You are welcome to supply images that you would like us to consider including, or to use as the main article image. Please submit pictures for inclusion as separate email attachments in your submission.

Author attribution

If the piece is to be written by a PR, they will have to find someone creditable in the company to take the by-line; we can’t put up pieces that are attributed to PR or marketing folks. The person taking the byline should read and approve the material in advance as representing his or her views.

Authority

If the feature refers to news events, a hyperlink proving it should be provided for such references for authority (not Wikipedia links). Too many is better than too few, as they are easier for us to prune than to research ourselves.