https://meta.discourse.org/t/links-category-for-discourse/43532 Links category is going to be a core feature. Links category offers the ability to post a link instead of text as well as displaying the link in the topic list. I’ll work together with the team for all its features. All features shall be working as original after the transition. It adds an option in the category settings to be enabled. It stores links in the topic’s custom fields. A customized composer which shows only a small input field instead of original one is used to post link topics. The digest email template is also overrided for displaying url. The implementation of plugins overrides many spots of core model which looks quite awkward to merge directly. I believe another archetype is much promising to try in the new implementation as described here. But that should result in a lot of changes in composer model and post creator. I’d like to know whether it’s the right path to go. @team

@team I think Erick is blocked on this without any feedback since he needs to know whether archetypes is the way to go or not before doing any significant work.

I personally would rather prioritize this than Feature Voting, as it is more broadly useful to any Discourse site. But we’ll need to pick one – we don’t have anyone else to allocate at the moment.

If archetype is an expensive way to go, I can still merge the plugin in the core with the same implementation. It could be a bit messy in code. But I can improve later.

Adding an archetype construct is going to be a massive amount of work, I am not sure I am keen to take on that work right now. Instead lets just extend plugin api to support what we need here if bits are missing cc @eviltrout

I am curious what kinds of changes you’d need to the plugin api to support this? You said the code goes deep into the model which sounds a bit scary.

This should actually be merged into core, I don’t think this should be a plugin at all. Sharing a link and inviting discussion on that link is an essential feature for all Discourse instances. We’ll need to allocate someone for this work in the next few weeks.

Should this be by category as it is today, or by topic as Reddit and HN?

Probably by topic. I don’t think a whole category is needed. Some topics will be link based, others won’t.

Also (sorry for being so specific) are we keeping the like OP on topic list? And only for link-type topics?

Sorry for my communication. I have arrived Sweden and there were things unexpected in the way :frowning: I will make some progress this week. [image] eviltrout: I am curious what kinds of changes you’d need to the plugin api to support this? You said the code goes deep into the model which sounds a bit scary. The code simply uses topic custom field so there are monkey patches in the ComposerController. And I also patched Topic and Composer model. To be merged to core with less work, sounds another model like Warning can do the trick. As @sam asked, I will look for a way to extend Ember models to carry the field.

Merge discourse-links-category into Discourse

Development

neil (Neil Lalonde) November 30, 2016, 9:55pm 15

FYI I’m reviewing the PR now and hope to merge it soon. Soon!™

Topic		Replies	Views
Start a topic by pasting a link (like Reddit) Announcements new-feature , featured-link	73	13064	February 17, 2017
Submit Link (Similar to Reddit or Hacker News) Feature	20	7044	January 8, 2016
Only allow link sharing? Product Support	5	1008	June 25, 2019
Link that pre-populates the composer? Feature	2	2119	May 14, 2015
Edit URL into a topic title after creation? Feature	17	3802	May 10, 2020

Merge discourse-links-category into Discourse

Related topics