It's Time We Talked About Tags

Originally published at: It’s Time We Talked About Tags | Blog

Consider the typical sections of a daily newspaper: Arts, Sports, Business, Travel, Local, and World. Any given article belongs to just one of those sections, and the content in each section is quite different, such that some people, for example, may only ever read the Sports or Business sections. These are what we call categories.…

32 个赞

Great work! I love tags, and I’d just like to repeat some of my suggestions:

  • Ability to require a tag per section (as stated in the blog this is coming!)
  • Ability to add info per tag, such as a short description and a link (this would show on mouse over, as well as on the tag view page)

These would be nice to have:

  • A redesigned tags homepage (currently very unappealing, would like to see it more useful/informative like the categories homepage)
  • Ability to give tags different colours (not as important but could be nice for some communities)

With this in place I can see tags becoming a huge part of how people use Discourse :smiley:

13 个赞

I want to add this feature request to the tag wishlist.

1 个赞

Great to see that tags now gain more attention. Please also consider adding support for tag aliases.

5 个赞

3 posts were split to a new topic: Some questions about tags

+1 this - the company I work for is a stockbroker and we collect requests from users for stocks that they want us to offer. There’s groups of stocks that we can’t add at the moment, for a particular reason. Tagging would enable us to highlight the fact that a stock is part of that group & explain in a short message / link to a topic explaining why we can’t add the stocks yet.

3 个赞

Do I understand this to mean that the functionality of tagging as described in the @HAWK post is not available to users accessing via mobile. In particular, how would this resolve in the scenario where we were requiring all posters to assign a tag to the post for the purposes of “categorisation”?

1 个赞

Tagging is fully supported on mobile today. It wasn’t at the time of Steve’s post.

11 个赞

@awesomerobot reminded me of this absolute classic Clay Shirky post on the topic of tagging versus categories

https://web.archive.org/web/20180224153834/http://www.shirky.com/writings/ontology_overrated.html

If you haven’t read this, and have any interest in the topic whatsoever … please read it now. :bowing_man:

15 个赞

@codinghorror 您是否对特定于基于位置的内容的类别、标签或组有建议?

对于我的用例,我有一个业余无线电爱好者社区 (https://community.americanradioclub.com)。出于多种原因,位置非常重要,但主要有几个原因:1) 他们可以与附近的用户进行业余无线电联系,2) 安排本地聚会,3) 讨论本地中继器、应急通信演习等。

我想自动订阅用户更新他们所在州/地区的信息,使用 API 将他们所在州/地区的信息放入他们的 WordPress 仪表板,并允许他们发布他们所在地区活动的帖子和讨论主题。

是否有推荐的方法以这种方式使用位置?

目前我正在考虑设置类别:区域无线电,子类别:州,然后使用标签来标记活动、聚会、操作等。

4 个赞

通过地理位置连接用户很棘手,我知道 @pfaffman 过去曾与他的一些客户合作过。用户个人资料中当然有对地理位置字段的既有原生支持,但地理位置字段是完全自由格式的文本。

Discourse 更侧重于通过共同的_兴趣_和_话题_连接用户,而不是地理位置,但地理位置对某些社区来说可能非常重要。

5 个赞

当然,用户也同样关心兴趣和话题。许多更传统的社区平台都提供内置功能,例如“附近的人”和“活动”等,但我将使用 Discourse 并进行一些插件和自定义。

我非常喜欢 Pavilion 的位置插件(我认为现在由 Discourse 维护?),我将安装它并看看它的效果!我真的认为 Discourse 实际上可能是基于位置的帖子最佳平台,甚至可以以一些有趣的方式与业余无线电集成。如果我弄清楚了一些很酷的东西,我一定会分享。

我的社区还有很多关于业余无线电天线、电源、设置、操作方法等方面的讨论,这些是 Discourse 的更常规用例,与位置无关。因此,我计划将基于位置的对话保留在一个类别中,并使用 位置插件 在那里标记位置。

7 个赞

抱歉,您无法在当前的托管计划上安装该插件。:frowning:

3 个赞

@HAWK 哎呀!这是因为它不是官方支持的插件吗?

3 个赞

它得到官方支持,但您仅限于套餐中提供的插件。如果您想与支持团队讨论此事,请发送电子邮件至 team@discourse.org

6 个赞