3 ms·
> inventor of the wiki It's interesting you gave that example. Before my first use of a wiki I was on a team that used Lotus Notes and did project organization
by socalgal2 1y ago
> inventor of the wiki
It's interesting you gave that example. Before my first use of a wiki I was on a team that used Lotus Notes and did project organization in a team folder. I loved that Notes would highlight which documents had been updated since the last time I read them.
In the next project, that team used a wiki. It's simpler. But, the fact it didn't tell me which documents had been updated effectively made it useless. People typed new project designs into the wiki but no one saw them since they couldn't, at a glance, know which of the hundreds of pages had been updated since they last read them.
It was too simple
- avhon1 1y agoFWIW, showing recent changes is a very common wiki feature. Here's the page for my local makerspace's wiki, which runs on mediawiki: https://bloominglabs.org/Special:RecentChanges?hidebots=1&limit=50&days=90&enhanced=1&urlversion=2 https://bloominglabs.org/Special:RecentChanges?hidebots=1&li...
- something98 1y agoA terse diff like that, on a separate page, is probably not what they were referring to.
- me-vs-cat 1y agoThe first wiki by Ward Cunningham included a RecentChanges page from the beginning or very nearly so. > It was too simple That happens when you ignore requirements, either because they were outright discarded or because they were never recognized. "The simplest thing possible" is understood to include: "to meet all requirements."