As a basic overview CodeProject articles have a certain layout to follow, so that users can learn the most from them. Each article attempts to answer the following questions: What problem does this solution solve? How does this help someone else? How does the code actually work? What is going on inside the code snippets? Here is a submission from a first time author who did a terrific job, just to give you a basic overview of what a beginner article might look like: Avoiding InvokeRequired[^]
And here is a submission from one of our top authors.
HTML5 WebWorkers Experiment
Keep in mind that CodeProject readers are primarily 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.
In the above article, Sacha's 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.
Every time the community considers whether or not to approve an article, this is the style of article they have in mind. They love it, they want it, and they praise the authors enormously when they get it (and we want authors to feel like their hard work is appreciated).
For more tips on writing articles, please see this article: A Guide To Writing Articles For Code Project[^]