You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the ability to "favorite" modules might fit this criteria and be useful. Just a way for folks to show that they like a specific module and a way to generate a list of "most popular" modules that is different from pure usage statistics. This would not allow for any negative feedback and would be quite simple. Not to mention, it's easy to implement with the flag module and nothing else.
TODO:
MVP
install flag module
set up "Favorite" flag configuration (nodes of type module, theme, layout) and permissions
display a flag toggle link on each project page (in the sidebar?)
add a count for how many people favorited an individual project, and display this on the project page
Better product
Create a view of most popular projects, with 4 displays:
* (Default) popular everything
* popular modules : filter for type = project_module
* popular themes : + filter for type = project_theme
* popular layouts : + filter for type = project_layout
* popular everything + contextual filter for uid
Create a page at /add-ons/most-popular that contains the module, theme, and layout blocks
display view of favorite each person's modules for on their profile
Nice to have
add popularity as a sort criteria on the project listing pages
add popularity into the project feed (and then also the core installer module)
The text was updated successfully, but these errors were encountered:
The term 'popular(ity)' is however quite ambiguous, in my opinion. Probably many will think at first sight, that being popular refers to the number of installations. Not sure about an alternative. I guess, 'favorability' is not ideal.
I think the ability to "favorite" modules might fit this criteria and be useful. Just a way for folks to show that they like a specific module and a way to generate a list of "most popular" modules that is different from pure usage statistics. This would not allow for any negative feedback and would be quite simple. Not to mention, it's easy to implement with the flag module and nothing else.
TODO:
MVP
Better product
* (Default) popular everything
* popular modules : filter for type = project_module
* popular themes : + filter for type = project_theme
* popular layouts : + filter for type = project_layout
* popular everything + contextual filter for uid
/add-ons/most-popular
that contains the module, theme, and layout blocksNice to have
The text was updated successfully, but these errors were encountered: