Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

71%
+3 −0
Meta Separate the tags away from the Sandbox or delete the [finalized] tag

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...

0 answers  ·  posted 3y ago by General Sebast1an‭  ·  edited 3y ago by General Sebast1an‭

#2: Post edited by user avatar General Sebast1an‭ · 2021-09-02T04:54:21Z (about 3 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 user avatar General Sebast1an‭ · 2021-09-02T04:51:32Z (about 3 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.