Post History
This is a feature-request post consisting of 2 actions for a reason... There's this thing that's been bugging me for a while in Code Golf CD. If you go to the tag page of the Challenges catego...
#2: Post edited
by
General Sebast1an
·
2021-09-02T04:54:21Z (over 2 years ago)
- > This is a <a class="badge is-tag is-filled">feature-request</a> post consisting of 2 actions for a reason...
- There's this thing that's been bugging me for a while in Code Golf CD. If you go to the [tag page of the *Challenges* category](https://codegolf.codidact.com/categories/49/tags), you'll be greeted with, of course, tags. But there's one tag that I didn't want to see a part of in *Challenges*: <a class="badge is-tag" href="https://codegolf.codidact.com/categories/49/tags/4300">finalized</a>, a tag that only shows in the *Sandbox* category. This doesn't fit, honestly.
It's weird seeing a tag from a sub-category (categories that rely on a more *main* one) appear from the other, and I want to fix that somehow. There are 2 options:- 1. Get rid of the <a class="badge is-tag">finalized</a> tag once and for all. Doesn't seem to be completely necessary, as one could simply say it is [finalized] or [released] by adding it to the title. (Actually, we might need to have a policy on tag burnination soon.)
- 2. Separate the tags from the 2 categories. If no one wants to get rid of the tag, this is an option. Basically, it removes the post count from the *Sandbox* away from the *Challenges* category, and vice versa. This clears <a class="badge is-tag">finalized</a> away from the tag list in *Challenges* and also fixes the post count from all tags.
- So which is better, the former or the latter? That's where you guys decide. If the majority doesn't agree on any of the ideas, well said then, we won't deal with the tag in there.
- > This is a <a class="badge is-tag is-filled">feature-request</a> post consisting of 2 actions for a reason...
- There's this thing that's been bugging me for a while in Code Golf CD. If you go to the [tag page of the *Challenges* category](https://codegolf.codidact.com/categories/49/tags), you'll be greeted with, of course, tags. But there's one tag that I didn't want to see a part of in *Challenges*: <a class="badge is-tag" href="https://codegolf.codidact.com/categories/49/tags/4300">finalized</a>, a tag that only shows in the *Sandbox* category. This doesn't fit, honestly.
- It's weird seeing a tag from a sub-category (categories that rely on a more *main* one) appear from the main, and I want to fix that somehow. There are 2 options:
- 1. Get rid of the <a class="badge is-tag">finalized</a> tag once and for all. Doesn't seem to be completely necessary, as one could simply say it is [finalized] or [released] by adding it to the title. (Actually, we might need to have a policy on tag burnination soon.)
- 2. Separate the tags from the 2 categories. If no one wants to get rid of the tag, this is an option. Basically, it removes the post count from the *Sandbox* away from the *Challenges* category, and vice versa. This clears <a class="badge is-tag">finalized</a> away from the tag list in *Challenges* and also fixes the post count from all tags.
- So which is better, the former or the latter? That's where you guys decide. If the majority doesn't agree on any of the ideas, well said then, we won't deal with the tag in there.
#1: Initial revision
by
General Sebast1an
·
2021-09-02T04:51:32Z (over 2 years ago)
Separate the tags away from the Sandbox or delete the [finalized] tag
> This is a <a class="badge is-tag is-filled">feature-request</a> post consisting of 2 actions for a reason... There's this thing that's been bugging me for a while in Code Golf CD. If you go to the [tag page of the *Challenges* category](https://codegolf.codidact.com/categories/49/tags), you'll be greeted with, of course, tags. But there's one tag that I didn't want to see a part of in *Challenges*: <a class="badge is-tag" href="https://codegolf.codidact.com/categories/49/tags/4300">finalized</a>, a tag that only shows in the *Sandbox* category. This doesn't fit, honestly. It's weird seeing a tag from a sub-category (categories that rely on a more *main* one) appear from the other, and I want to fix that somehow. There are 2 options: 1. Get rid of the <a class="badge is-tag">finalized</a> tag once and for all. Doesn't seem to be completely necessary, as one could simply say it is [finalized] or [released] by adding it to the title. (Actually, we might need to have a policy on tag burnination soon.) 2. Separate the tags from the 2 categories. If no one wants to get rid of the tag, this is an option. Basically, it removes the post count from the *Sandbox* away from the *Challenges* category, and vice versa. This clears <a class="badge is-tag">finalized</a> away from the tag list in *Challenges* and also fixes the post count from all tags. So which is better, the former or the latter? That's where you guys decide. If the majority doesn't agree on any of the ideas, well said then, we won't deal with the tag in there.