Ron, thank you for your argumented answer.
My understanding of the Tip/Tricks category is it is a good place to explain a few-code-lines technique.
A
recent article is a good example: two 7-lines examples, a good text that explains the technique, and no Zip archive.
I agree that the word 'article' suggests it will explain a technique.
But what if you want to publish a solution that is not a simple trick nor a technique explanation ?
Let's imagine somebody wants to publish a rather big solution to a common problem, but this solution does not involve any particular technique in its code ?
I do not imagine the author publishing it as a trick.
As an article, it would be more focused on usage of its program than on any technique.
Until now, I thought CodeProject was a good place to publish some useful piece of code with some documentation (as said in the official site's documentation, by the way), something more documented or explained than a pure source code store site as GitHub, but I now understand there are some not-said requirements for the articles.
I don't know if there should be a third way in CodeProject, something as 'solutions', but now it seems clear to me the existing 'article' and 'tip' categories do not fit all usages.