Editorial Guidelines

Please observe the following editorial guidelines when submitting blogs to DEVOPSdigest:

Getting Started

DEVOPSdigest recommends that you send an abstract or outline of your potential blog submission to Pete Goldin, Editor and Publisher of DEVOPSdigest, before you start writing the blog, to ensure it is something we would publish.

The following guidelines apply to non-vendors — such as analysts, consultants, integrators and users — who would like to post a blog on DEVOPSdigest. Non-vendor blogs are posted in the BIZDEVOPS Blog.

Vendor blogs are posted in the Vendor Forum. If you work for or represent a product vendor, and you want to submit a blog to DEVOPSdigest, click here for the Vendor Forum guidelines.

If you are a PR or Communications Manager or Agency, click here for some tips on how to interact with DEVOPSdigest.

If you are submitting a quote for a DEVOPSdigest list, such as our annual DevOps Predictions list, click here for guidelines on APMdigest.

Original Content

All blogs submitted to DEVOPSdigest must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not pitch DEVOPSdigest to re-post your blog.

Word Count

Standard word count for a blog is 500-1000 words. This is not a strict rule. Word counts can be longer if the topic warrants more content. If your blog is longer than 1000 words, however, you may want to consider breaking it into multiple parts. Editorial decisions relating to word count are made on a case-by-case basis.

Deadline

DEVOPSdigest does not follow an editorial calendar, and usually does not assign a deadline. We post content as we receive it.

Publication Timeframe

DEVOPSdigest posts 1-3 items of primary content — blog or feature — per week. Consequently, there is often a queue of content waiting to be posted.

DEVOPSdigest content is featured in APMdigest e-mails, which go out twice per month, and the current mailing includes content posted since the last mailing.

Topics

DEVOPSdigest accepts blogs on topics relating to DevOps including:

■ DevOps

■ Development Processes

■ Development Technology

■ Development Automation

■ Agile Development

■ Continuous Development

■ API (Application Program Interface)

■ Development Monitoring and Analytics

■ Application Performance and Quality Testing

If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.

Content Guidelines

Blogs should be objective, vendor-neutral, thought leadership pieces. Topics should be general industry interest to educate and enlighten our readers. Please do not promote your company, products, partners or any vendor — or criticize the competition — in the blog copy or in related graphics submitted with the blog.

Author and Company Profile

If this is your first blog for DEVOPSdigest, send a one paragraph bio of the author and one paragraph profile of the company, along with the blog.

Related Links

On The BIZDEVOPS Blog, non-vendor bloggers are welcome to include links at the end of the blog to link to their home page, or other relevant information such as research or events.

Do not place any hyperlinks in the body copy of the blog linking to your company's web pages or any other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making.

Approval

All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Related links included with the blog are also subject to DEVOPSdigest approval.

Reposting Blogs

If you contribute to DEVOPSdigest, you are free to re-post your own blog on your own website, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site.

However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.

The Latest

June 28, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 5, the final installment, covers how Agile improves product quality and the customer experience ...

June 26, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 4 covers how Agile impacts team productivity ...

June 23, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 3 covers how Agile enables you to grow and adapt to change ...

June 21, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 2 is all about speed ...

June 19, 2017

Earlier this year, DEVOPSdigest featured a list of expert opinions on the essential steps to become agile. Now that we have an idea on how to achieve agility, however, we have to consider why. What's the payoff? With this question in mind, DEVOPSdigest asked the experts — including analysts, consultants and vendors — for their opinions on what are the most important advantages of being Agile ...

June 15, 2017

In the development community, creating additional efficiency through improved collaboration has been prevalent for some time. But despite the head start on the rest of the corporate world when it comes to collaboration, many organizations function today as they did 15-20 years ago. Since time is money in the tech world, outdated collaboration is a huge missed opportunity ...

June 14, 2017

Given the efforts we put in these days to deconstructing monolithic applications, and using distributed microservices to make us more agile, the potential for app performance to take a nosedive because of unseen (and unanticipated) network congestion and outages is only getting greater. There is help at hand, though, in the form of new ways to program network awareness directly into your code ...

June 12, 2017

What if you discover a fatal error or an exploit in your app? What if your app is down during a crucial time? As a developer, how you react to a crisis can mean the difference between minor blip and an embarrassing or costly company blunder. Here's a crisis management plan to get things right when they go wrong ...

June 08, 2017

Recently, the results from SmartBear Software's annual survey, the State of Code Review 2017: Trends & Insights into Dev Collaboration were released. One point I found interesting is that it suggests only 66 percent of organizations can get releases out on time. Why are the other 34 percent struggling to get releases out the door? ...

June 06, 2017

Today's app development landscape is competitive and expensive. Thousands of apps are released each month, and user acquisition and retention are costing app developers millions. User abandonment is one of the main battles of every app developer — as every lost user means another wasted investment ...

Share this