Hi @Maik Skoddow ,

i am sorry, i just read November update ... a bit confusing that communities shows this to me as the first comment below your article, which made me assume it is the latest available and just some months old.

In the long term this made me think about my own writing style, i would also perhaps left out the year. I find a lot of community entries which first sound interesting but then you realize they are years old and in some cases not applicable anymore at all. I did not check weather there is some guidance how to write good articles, blogs and comments including some clarification right inside the text to set the context of version and applicability for future consumers of the element.

An example might be the Vendor Management Overview Article, which is a few years old and does not reflect the differences between the different techniques e.g. legacy and UI builder based workspaces and their installation amongst others.

I do not have a general solution yet other then the writing guidance mentioned above and maybe some extension of the communities functionality that reminds authors over the year of their older articles, comments or other entities if they opt in for it.

I created an idea, comments and upvotes are welcome!

Remind authors to validate their content

 

Kind regards .. .

PS: will try to train myself to check the date of the article instantly.