Over a million developers have joined DZone.

Guidelines for DZone Articles

DZone's Guide to

Guidelines for DZone Articles

· Java Zone
Free Resource

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

The following are guidelines for if you're considering posting articles on DZone, put together in consultation with various people including Rick and Matt. It is a "living" document.

Can you give me some guidelines for the subject matter that should be covered here?

  • No marketing material. In other words, if a non-technical marketing person would be interested in reading what you're writing, you shouldn't be writing it for DZone.
  • The article shouldn't be a mere pointer to another article. It should have unique content of its own.
  • Technical articles are preferred. If you can get some code snippets into your story, somehow, that's better than no code snippet at all.

What about some general style guidelines?

  • Titles should be capitalized, like this: My Very Interesting Story
  • It is important that the first few sentences of anything you write is very descriptive of the content of the rest of whatever it is. This is because the first few sentences are used as the "teaser", that is, the sentences on the zone index that provide a high level description of the rest of the content.
  • Try and keep the formatting simple. For example, no numbered lists within other numbered lists.
  • At least one pic. But not too many pics either, unless having them is very functional to the content. After you have two or three pics, ask yourself if more are really needed. They might be, but if they're pretty obvious and don't really add something to the story, consider excluding them.
  • If you're interviewing someone, you need to include a pic of the interviewee.
  • Pics shouldn't be massive (aim for 600 pixels). If a picture is the first thing in your content, it needs to be 525 pixels or less and left aligned.

Frequently asked questions:

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.


Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}