Tell us a story we can’t report ourselves.
This is our jam: app development and management at scale, and all the software and services that support this task. We want to know how everything works, from a sysadmin or dev angle.
People like TNS because it analyzes and explains technology, with a voice that is positive, forward-thinking and cuts through the nonsense.
And we don’t talk down to the reader; we know the reader is intelligent.
Mostly, we want stories that offer our readers a little something for their time. Busy people, they are. They’re CTOs, project managers, developers, administrators and other technically-inclined IT pros who do not appreciate having their time frittered away on artfully-disguised marketing copy.
Contributed stories are, at heart, an exercise in mutual exploitation. So if you truly do desire an audience before our technically-inclined (and hella influential) readers, you will have to bring it.
In other words, don’t write like you are writing a presentation for a company meeting; Write like you’re urgently describing something important, or at least entertainingly bizarre, to your technically-inclined peeps, all sitting around the fire (or bar) late at night, trading tales of the craft.
If you are a standards group or an open source project, we want to hear what you’re doing. If you’re company with a unique technical perspective on the market, explain it to us in an elucidated, compelling way. If you’ve sussed out a better technique for getting your job done, we want to hear about it.
A contributed piece doesn’t have to be 3,000 words of heavy teaching. It can be 500 words outlining a technical epiphany, a handy technique, or a small lesson learned of some sort. Code snippets are fine, as are visualizations, and stats and metrics are always appreciated.
An example! nearForm’s Mattero Collina submitted “How To Do Microservices with Node.js.” Collina brought up the idea that microservices architecture does away with the need of object-oriented modeling. You may agree with the idea. Or not. But our readers found it interesting enough to ponder. And, oh yeah, they learned a bit more about nearForm in the reading.
So other than all these conditions, we’re pretty flexible about the type of content, length, style, etc. for contributed content. Our editors are civilized people who can be reasoned with, for the most part.
We do accept tutorials with embedded code. Due to the limits of the WordPress platform, however, we have a set of rules for what we can and cannot support with embedded programming code:
- Code can not be colored, nor have any additional formatting.
- Only ASCII characters — not smart quotes.
- No HTML or any other code with an open or closed brackets.
- Code block space (i.e. tabs) is done on a best-effort basis: We can make no guarantees that code will remain in the structure provided This is especially true with tabbed code (We’re looking at you, Python).
- NO markdown.
- We encourage the use of third-party plug-ins where applicable, such as Asciinema, or dynamic gifs.
Please note that all contributed content we run must be original. We do not run posts that have already appeared somewhere else on the Internet. We also require a two-week window when we have exclusive rights to run that content. We ask this to ensure the material gets the highest visibility with our readers and with the search engines. After this time period, contributors are free to run the material elsewhere, such as on their own sites or on Medium.
Please also note that we can only accept contributions from a company or individual once every three months. We encourage those who wish to submit more frequently to chat with our sales department to find the sponsorship that is right for them.
So if you have questions, or want to submit something, hit us up here.