Making WordPress.org: Ticket #2797: Plugins: Suggest related plugins when the current plugin hasn't been updated in two yearshttp://meta.trac.wordpress.org/ticket/2797
<p>
There is currently a banner on any plugin that hasn't been updated in two years. We should be able to add related plugins to this section to guide the user in a better direction.
</p>
<p>
<a style="padding:0; border:none" href="https://cldup.com/rxgfEgMSiu-1200x1200.png"><img src="https://cldup.com/rxgfEgMSiu-1200x1200.png" alt="https://cldup.com/rxgfEgMSiu-1200x1200.png" crossorigin="anonymous" title="https://cldup.com/rxgfEgMSiu-1200x1200.png" /></a>
</p>
<p>
This is for: <a class="ext-link" href="https://wordpress.org/plugins/email/"><span class="icon">​</span>https://wordpress.org/plugins/email/</a> (chosen randomly)
</p>
<p>
This screenshot also shows a "Search for other plugins." link which just links to the search page at <a class="ext-link" href="https://wordpress.org/plugins/search/email/"><span class="icon">​</span>https://wordpress.org/plugins/search/email/</a> (just using the plugin's slug as a search string). Not great, but it is easy. Eventually we could have a page at /plugins/SLUG/related that we link to instead.
</p>
<p>
This search link could use some CSS/Design help/ideas/language.
</p>
<p>
The algorithm for related plugins isn't figured out yet (the above screenshot was hard coded with plugin IDs selected based on search), but this should be a pretty easy query to build.
</p>
<p>
The downside to this approach is that it pushes the main plugin down the page a lot, but by reusing the existing search cards it is pretty easy to implement.
</p>
en-usMaking WordPress.orghttp://meta.trac.wordpress.org/chrome/site/your_project_logo.pnghttp://meta.trac.wordpress.org/ticket/2797
Trac 1.2.2slackbotWed, 03 May 2017 22:16:30 GMThttp://meta.trac.wordpress.org/ticket/2797#comment:1
http://meta.trac.wordpress.org/ticket/2797#comment:1
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #meta by gibrown. <a class="ext-link" href="https://wordpress.slack.com/archives/meta/p1493849788191485"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketslackbotWed, 25 Oct 2017 22:29:57 GMThttp://meta.trac.wordpress.org/ticket/2797#comment:2
http://meta.trac.wordpress.org/ticket/2797#comment:2
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #meta by gibrown. <a class="ext-link" href="https://wordpress.slack.com/archives/meta/p1508970596000018"><span class="icon">​</span>View the logs</a>.</em>
</p>
TickettellyworthWed, 01 Nov 2017 21:48:49 GMTstatus changed; resolution set; milestone deletedhttp://meta.trac.wordpress.org/ticket/2797#comment:3
http://meta.trac.wordpress.org/ticket/2797#comment:3
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>maybelater</em>
</li>
<li><strong>milestone</strong>
<em>Plugin Directory v3 - Future</em> deleted
</li>
</ul>
TicketgibrownThu, 02 Nov 2017 13:40:38 GMTstatus changed; resolution deletedhttp://meta.trac.wordpress.org/ticket/2797#comment:4
http://meta.trac.wordpress.org/ticket/2797#comment:4
<ul>
<li><strong>status</strong>
changed from <em>closed</em> to <em>reopened</em>
</li>
<li><strong>resolution</strong>
<em>maybelater</em> deleted
</li>
</ul>
<p>
@tellyworth I think we should leave this open. The screenshot is from a patch I have where I hardcoded the results. Now that JP Search code is live it should be pretty easy to add an algorithm to power the UI and get this live (once I can get back to working on .org). I'm hoping to get this live by the end of the year.
</p>
<p>
Some discussion on the UX or whether there are problems with this approach would be great though.
</p>
Ticket