Best Practice around number of Record Tags on News Posts

Certified Lead Developer

I was unable to find a recommendation of a suggested max number of Record Tags for a news post.

I have a primary concern of performance, as evaluating the visibility for the records must be done for each tag.  Depending on how many posts are loaded when hitting News, the system could experience heavy load.  I know it's an extreme example

I feel from a UX perspective 3 is about the most record tags you want, beyond that and the post gets cluttered.

Does anyone have any metrics or suggestions around the performance concern?  For UX, have you found 3 to be about right, more, less?

Also, if there is a clear recommendation in the documentation, can you please point me to it?

  Discussion posts and replies are publicly visible

Parents
  • Certified Lead Developer
    I have not seen any documentation on this, but I also find the max of 2 or 3 to be right from a usability perspective.
    Meaning a news post raises awareness to more passive participants. If they are slightly removed and you give them too many tags, how will they know which one to dive into or do you really expect them to drill, back, drill, back, drill. So, if you get too many, maybe that is even a better indication for a new record that combines that info, or...

    Hope that helps and provides one perspective!
Reply
  • Certified Lead Developer
    I have not seen any documentation on this, but I also find the max of 2 or 3 to be right from a usability perspective.
    Meaning a news post raises awareness to more passive participants. If they are slightly removed and you give them too many tags, how will they know which one to dive into or do you really expect them to drill, back, drill, back, drill. So, if you get too many, maybe that is even a better indication for a new record that combines that info, or...

    Hope that helps and provides one perspective!
Children
No Data