As more examples got updates in v36 and v37, this is becoming even more painfully obvious.
Shame that your gatekeepers wont even see this, let-alone acknowledge it.
Some notes:
our own projects show “almost transferrable” metrics already such as project version and Last Opened. Literally without any extra work, showing those on the feature examples would at least give us a rough idea if we should manually rebase.
Ideally has one called “Revision Number” or something, like existing “Docs: LINK” one.
Ideally this revision number would also be tracked at the start of the doc.
Plz consider hiring a technical writer at your company who would give pointers on successful knowledgebases.
Doco :: New and Updated used to occasionally mention major things other than the changelog (verse v1 changeover, etc)… i can see that it’s size is probably too big already to also include docs updates now… so maybe instead an indicator in the left side nav-list if something updated.
A good Doc Mgmt Sys would already track whichever article has been read, and then just bold or yellow-star next to titles of any that have updated since last read…
even without this, you could just bold/star anything that updated since last login, which is a metric your definitely do have.
or just bold anything changed since last point-release, or last major version?
so many options here for flagging changes in the doco/tuts pages, and im sure a good tech writer will have so many other ideas with what worked at their other employers like Microsoft etc.
I REALLY strongly feel that a bare-minimum should just be showing RC number in the Feature Examples project browser and probably just link/transfer that to the associated Doco page.