Project

General

Profile

Actions

Feature #2130

closed

CAC Featured Content "Random Content Type"

Added by Dominic Giglio over 11 years ago. Updated about 7 years ago.

Status:
Rejected
Priority name:
Normal
Assignee:
Dominic Giglio
Category name:
Home Page
Target version:
-
Start date:
2012-09-14
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

I think it would be really cool to add the ability to feature a random content type from all of the currently available content types. I envision it working similarly to the way the Display Images checkbox works. If an admin checks "Random Content" all unnecessary inputs would be hidden. Then the plugin would load a (different) random content type on the front of the site each time the page displaying the widget loads.

Actions #1

Updated by Matt Gold over 11 years ago

Interesting. I'm not sure that a completely random setting would be good in a use case like the Commons, in part because this plugin is premised on the site admins carefully choosing what they want to be featured. So a completely random selection might not be desirable. But if one could set up, say, sample featured content in a variety of content types, and then have the plugin showcase a new one randomly on page load, that would be cool and would lead to a more dynamic homepage. Is that what you meant?

Actions #2

Updated by Dominic Giglio over 11 years ago

I was thinking more generally for the "lazy admin" who would like to feature content but not have to choose what they'd like to feature. I do like your idea though.

I will think about how to implement a more "targeted randomization" based on predetermined content types. Maybe even allow the admin to select a blog, post, group and member and then save the widget in the admin. Then offer a randomization option that would constantly switch between the content types chosen and saved for that specific widget. It might be hard to explain to users in the small space allocated to widgets in the admin exactly how that works though. Might also be hard to design code around "maybe randomized" content types. I don't want to bloat the code with a bunch of additions for something that may only be used occasionally.

But that's why I opened this ticket, wanted to know what my fellow co-workers thought about the idea. That's also why I set it to Future Release, definitely not something that will be in the next couple of releases.

Actions #3

Updated by Boone Gorges almost 10 years ago

  • Category name changed from WordPress (misc) to Home Page
Actions #4

Updated by Boone Gorges almost 10 years ago

  • Tracker changed from Bug to Feature
Actions #5

Updated by Boone Gorges about 7 years ago

  • Status changed from Assigned to Rejected
  • Target version deleted (Future release)

Looks like this isn't going to be useful on the Commons, so I'm going to close it out.

Actions

Also available in: Atom PDF