Thanks very much for your message. Typically in our articles we're looking for meaty, exhaustively explained solutions to their development problems, or articles that can teach them something to make their developing faster, more efficient, or expand their repertoire. Here’s an article from one of our top authors: HTML5 WebWorkers Experiment[^] His primary goal is to demonstrate “Using HTML5 WebWorkers and a custom jQuery plug-in to create a Flickr image wall.” He treats the reader like a beginner. He defines jQuery, explains what WebWorkers are, then gets into why he wanted to create a jQuery plugin. Each progressive section of the article expands on his topic, thoroughly explains the code, explains the limitations he chose in his scope, discusses how each element to his plug-in works, provides numerous code examples, and most importantly, gives a source code download at the top for the reader should they need it. Your article was more of an opinion piece, which isn't quite in line with the aforementioned article and our guidelines. for your next article, I recommend choosing a topic where you encounter a problem you couldn't find a solution to anywhere else. A situation where you really had to apply effort beyond your current knowledge base; where you learned something new. Maybe you had to search around the web for a few sources that gave you hints, but not a full solution. Then write an article about what you learned, and the process in which you engaged in learning it, describing each step.
Thanks, Sean Ewington CodeProject
