|
I've written an FAQ on plagiarism to help authors understand what is plagiarism, as well as help members identify it. It is here: CodeProject Plagiarism FAQ[^]
If you find an article that is plagiarized you can either submit a report on the article itself, marking it as "Plagiarized," or you can report it in the Spam and Abuse Watch[^] forum with your evidence and a link to the members account, or you can email me directly sean@codeproject.com if you suspect plagiarism or have further plagiarism questions or concerns.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
This forum is for any and all questions for Code Project Article Writing:
- Have a question about writing an article?
- Having trouble posting?
- Blog aggregation not working?
- Not sure about your article topic?
- Is your article still pending?
- Is there a crazy formatting problem in your article?
- Not sure how to update your article?
- Having problems with the submission wizard?
- Need help making a change to an existing article?
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[^]
You can take a look at our article FAQ series here:
Code Project Article FAQ[^]
For tips on writing articles, please see this article:
A Guide To Writing Articles For Code Project[^]
You can also see our submission guidelines here:
http://www.codeproject.com/info/submit.aspx[^]
If it has to do with posting articles on Code Project, ask away. CodeProject staff and members are here to help.
Thanks,
Sean Ewington
The Code Project
modified 8-Apr-21 17:10pm.
|
|
|
|
|
Dear Colleagues,
Still waiting for approval...
|
|
|
|
|
I can see the other members are really trying to help you and I can see that you're attempting to make changes, but ultimately your changes are small and not enough.
If you please, let's try a different exercise here. For this article only, let's change the goal. The goal is not to get the article published. The goal, for now, is to get better at writing an article for CodeProject. Think of it that way.
Throw your existing article completely out. Start over from scratch. The first step that might be helpful is to make a rule for yourself. Write more words than code. Put it into a word counter if you have to. Write out what the code does, rather than show it.
Also, truly look at the following article by one of our top authors. Don't skim over it, don't skim over this message. Read every word. Think about it. Think about this author's approach in how it differs from your own. 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.
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.
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).
If you can fundamentally change your thinking here, and you can fundamentally change your approach, we're happy to continue working with you. There's no short cut to getting an article published. Put in the time, make the effort. Take a week or longer.
If you come back with minimal changes, that's the end of the road. I don't think you're right for CodeProject. We won't consider any more of your future articles. And that's OK. Some people and institutions don't fit together. But we could. You just have to decide to put in the work.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
Just finished tip/trick, please check it
|
|
|
|
|
I appreciate you being willing to start over. But this is essentially tool sharing, which contradicts everything I tried to carefully outline in my previous message. I'm afraid we will be rejecting this tip, and will no longer accept your article submissions on CodeProject.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Do you mean that there is no possibility to solve this question?
|
|
|
|
|
I mean we will no longer accept your article, tip, Blog, or Project submissions on CodeProject.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
Please help, I need more advise
|
|
|
|
|
|
I have revised and submitted, please review it
|
|
|
|
|
Sorry, but that is still not acceptable. There is no description of what actual problem this will help to solve. Two blocks of code with no details of what the code does, where it should be placed, or why. Please go to the links I gave you and read them carefully, in order to understand what an article or tip should contain. If you want further ideas then read some of the articles post by @RichardDeeming, @OriginalGriff. And here is another example of what a well written example looks like FMBomb - A Beginner's Approach to Hardware Programming[^]. And you do not need to be an electronics expert to understand the structure of the article. So stop rushing to post every few lines of code that you write, and think carefully about what you want to say.
|
|
|
|
|
Thank you, just edited, please review the tip/trick
|
|
|
|
|
Please stop posting, and read my suggestions above.
|
|
|
|
|
This is my entirely reviewed post, thanks
|
|
|
|
|
Thank you, just done, please check!
|
|
|
|
|
You have not done anything, you are just reposting the same thing over and over. As I keep suggestiong, stop posting something that we keep telling you is not accptable for publication. Go to the links I gave you and look at examples of properly well written aricles and tips.
|
|
|
|
|
I hope this is my last post, waiting for your comments.
I have added the problem description, outcome and vice versa.
|
|
|
|
|
Just re-worked, there's no more to add for this tip/trick - it's quite clear in the sense of term framework.
|
|
|
|
|
|
Thanks for information, It's a full article for review - IdahoJS
|
|
|
|
|
To add to what @Richard-MacCutchan has said, I sent you a long message two days ago which explained why we keep rejecting it, and suggesting what you need to do to get it through.
As it stand, nothing has changed that invalidates any of what I said - your framework is still unusable without significant effort being put in by every reader to try and work out what you can do with it, and what benefits they might get - and that's before they eve=n try to work out how to use it to get those benefits.
As such (and given the huge number of "frameworks" that are out there already) what you have submitted here is useless - nobody will use your framework because nobody will invest the time in checking if it will help them significantly. It's like you built a new car and hid it in a garage with a sign on the door saying "Good new vehicle inside" but bricked up the doors and windows and didn't leave any contact info! You won't sell any cars that way because nobody is going to see it.
We moderators aren't here to make your life difficult, or to be nasty - quite the reverse, we protect the site from not-ready articles, and authors from the derision and downvotes that poorer articles can receive. And to be a moderator, you have to write articles, so we know what it feels like when you slave away on something and Joe Moron from Stupidity High School, Kansas finds out it's not what he needs to hand in as his homework ... 
If we let this though as it stands, it would - at best - be ignored, and more likely downvoted into oblivion.
I'm sure you have put a lot of effort into getting the framework code right but without actual info we as readers have no idea if it's something we could use in our projects.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Thanks 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
