By default, all blog entries automatically generate a series of tags and tags decide where a blog entry lives on CodeProject. So first you will want to go and edit your article by hitting the Update icon:
Then, you will want to edit the tags within your article. You may also use the Auto fill Tags.
Currently we have series of taxonomy topics: Artificial Intelligence, Internet of Things, DevOps, Containers, High Performance Computing, etc, many of which have a corresponding taxonomy parent tag, like artificial-intelligence, IoT, DevOps, containers, etc. Then, within these we have taxonomy children. So, for example, artificial-intelligence has the following taxonomy children: big-data, data-science, deep-learning, machine-learning, etc.
When an article is created and give tags, where it sits in the taxonomy will depend on the tags chosen. There are several considerations that go into this decision and it is decided based on a hierarchy. What matters first and foremost is the taxonomy tag, the second thing that matters is the sort order, and then lastly then the length of the trail of the tags.
If you put in a tag that is a taxonomy tag, or associates with a taxonomy parent (like artificial-intelligence, IoT, DevOps, containers, etc.) this will be favoured greatly, and the article will likely be sorted into the corresponding Topic. For example, Articles / Artificial Intelligence
This is the order of how our taxonomy tags are listed. So, for example, you can go on the articles dropdown at the top of the page, hover over articles, then Browse Topics, this is the order in which taxonomy tags are valued. So if you have a taxonomy tag of artificial-intelligence, and another taxonomy tag, IoT, because Artificial Intelligence is higher in the sort order than Internet of Things, the article will be sorted into Articles / Artificial Intelligence
Length of Trail
One thing we want to do is consider is the length of a tag trail. The longer the tag trail the better. So, for example, if you put a C#4 tag, and this is a child of C#, which is a member of the Programing Languages topic, this is a longer trail than say, an algorithm tag, which simply has JUST the General Programming layer above it. So a C#4 tag would be of a higher value.
Bear in mind that this is an evolving this system. There are other factors that go into article placement considerations like Topic parents, where if a tag can’t be traced back through a taxonomy parent, it will walk through a topic parent.
Let’s look at an example. Here is:
Building a Database Application in Blazor - Part 1 - Project Structure and Framework.
It has the following tags:
C#, ASP.NET, HTML, Markdown, .NET-Core, Blazor
C# is a language tag, and is in the Programming Languages topic, while ASP.NET, HTML, and Blazor are Web Development tags. Because Web Development is higher in the Topic Hierarchy than Programming Languages, it gets preference and the article is placed into Articles / Web Development / Blazor. If you look at the list of tags within the Web Development Topic, you see:
Note that Blazor is at the top of this list. This is why the article is placed in Blazor, rather than Articles / Web Development / ASP.NET. .NET-Core and Markdown are not child tags that are associated with any particular topic, so in terms of placing the article, they are discounted.
For a full list of Topics and corresponding child tags, please look at our Site Map. If you have any questions, problems, or Topic suggestions, please feel free to reach out to us on the Bugs and Suggestions forum, or send us an email at email@example.com.