ישנו רכיב עיצובי שדרכו אוכל ליצור דף בית כזה ב-Discourse Filtered Topics List, אבל אני מרגיש שהחיסרון הוא שהוא עובד רק עם מסגרת זמן מסוימת, אז אצטרך לשנות את מסגרת הזמן מדי יום.
אני מתכוון, לעת עתה, זה עובד על בסיס שאני יכול להוסיף תאריכים, כמו:
activity-before:YYYY-MM-DD נושאים עם עדכון אחרון לפני התאריך שצוין
activity-after:YYYY-MM-DD נושאים עם עדכון אחרון אחרי התאריך שצוין
created-before: YYYY-MM-DD נושאים שנוצרו לפני התאריך שצוין
created-after:YYYY-MM-DD נושאים שנוצרו אחרי התאריך שצוין
אבל אז אני תמיד אצטרך לשנות תאריכים. האם יש אלטרנטיבה שאני יכול לעשות בפורום?
Does your case require these to be literally most replies/likes? If you use the /top topic list you can get automatic time periods… top factors in views, likes and post count (and you can adjust these weights a little bit with site settings)
Right this is a complication with sourcing multiple topic lists, a component would need to cross reference each list and remove duplicates. Not very complicated, but I don’t think this has been implemented in any available components.
Yeah it wouldn’t be too complicated to add a “hide duplicates” feature to Filtered Topic Lists, if @gormus is interested. The findFilteredTopics action could be modified to store every topic ID in a list, and then duplicates could be filtered out.
The downside is that if you want a list of 10 topics, you might only get 5 after duplicates are removed… but that could be partially avoided by maybe fetching a few extra beyond what was specified in the setting.
I’ve added filtered lists to homepages on several projects before and I’d caution that to populate multiple “most recent” lists with overlapping filters, you really need a very active community to begin with. Now when your community is that active, you’ll also have a much richer set of content to work with for building a dynamic homepage. In that case, a block of different lists might rather come off as static and not so visually appealing.
Though for a slightly different angle, you could also explore just putting one or two lists with a manual time filter. That could even feel more dynamic for the users. As in this view:
