PlanB-Network
Add a date to the articles
I propose to add a "date" on each article (the date of "last update", or both "first publication date + last update"). It will help a lot in the future, when people will need to find up-to-date info.
I was referring to this article, for example: https://planb.network/en/tutorials/node/ronin-dojo-v2
Thx a lot for this very important you do for the community!
@carmine-pb it's a tiny detail but it seems important for tutorials, cause it has been asked several times. Could you add those dates onto the page please? @LoicPandul @Asi0Flammeus do we have this "publication date" and "last modification date" in the data or does it need to be added.
Not yet, but we could add a publication date in the tutorial.yml. We already have dates for proofreadings, but that doesn’t really fit here. Personally, I don’t think the "last modification date" is relevant, because we often make small changes without fully updating all the informations. imho we only need a "publication date", and when we release a major V2 of the tutorial to update it, we update that date.
It feels like the underlying user need is to have an indicator of trustworthiness and whether it still applies to the software they are about to use/that they have.
We could go in two directions that I can think of:
-
The simplest solution would be a date, but even that leaves the question open of whether they can trust the software: how would you know if "4 March 2024" is outdated? So it's a bit of an indirect wat of conveying trust.
-
Have a little indicator/badge that says: "✔️ Verified for RoninDojo v2.x", to give the user confidence that it will work for them. But it's potentially more maintenance work.
@LoicPandul @mumacadam Any preference?
I think proposal 2 is not realistic from a data perspective. We already have 300 tutorials, and the developers of all these tools are working continuously. It's impossible to track and verify evry updates of each tool continuously, especially since each tutorial involves the use of numerous features. I think option 1 is a good compromise, even if it's not perfect as you explained.
To know if the tutorial is up to date or not, a comments or reporting feature by the readers would be more effective imo
Just to clarify, I meant we would note down the version the tutorial relates to, so only at the time of writing (v2.0).
But I do agree a simple date is much simpler from our perspective. It would get updated automatically any time the content changes. It doesn't fully address the question of user confidence in the match between software being used and the tutorial material, but it's good enough for now, a quick solution. 👍
Let's go with that ✅