Sort by updated time feature for examples page #31339
Conversation
|
Sorting by "date added" may make more sense than sorting by "date modified". Or, just add the release ( e.g., "r177" ) as a tag to |
I got the created timestamp in timestamps.json but I thought updates might also be important for examples |
|
I'd also prefer date added over date modified. Often, examples are trivially updated to use more up to date syntax, even if the core code of the example itself has not been updated. For instance, PRs like #28241 make minor modifications to a large number of older examples. If we were to go by date updated, then many examples that have been in the codebase for nearly a decade will seem to be only a year old at most. Alternatively, there could be a sort by option allowing the user to sort alphabetically, by date added, or by date updated. Nonetheless, the date displayed in italics alongside the title should probably be date added. |
|
@Mugen87 I don't think this PR relates to documentation? |
|
You're right, I've misinterpreted the PR. Deleted my comment to avoid confusion. |
|
@cmhhelgeson got it, then I'll provide options and make the "added date" default, does that make sense? |
1- Added alphabetical and date created sorting, defaulting to date created 2- Now aligned with overall lowercase style 3- Removed "/" before "17 days ago" text which was out of context
📦 Bundle sizeFull ESM build, minified and gzipped.
🌳 Bundle size after tree-shakingMinimal build including a renderer, camera, empty scene, and dependencies.
|
|
@cmhhelgeson the commit a399191 should do |
|
Sorry for spamming, guys. Further simplification was possible, so I couldn't resist. |
|
The webgl, webgpu, svg examples are in separately-sorted lists. That may be confusing. Also, I'd suggest setting the label to sort by "newest", instead of "date created". Check how GitHub sorts Issues. |
|
WebGL and WebGPU separation seemed intentional, serving as main categories. In the currently live version, they are kept in search results. If I go the "newest" path, I have to go for the "oldest", etc, too. I was aiming to reduce the number of words/icons from the feature. |
|
The example's modification date is more interesting to me. Many projects are modified from one release to the next bring important updates like this for the next release for example . I've read this several times on X, where people ask what changed in the same example from one release to the next. If we could measure a big change, this would be the ideal scenario. I also think that should be shown as release, since the project is published this way on github for master by sprints and not granularly by day. It would be possible to use the timestamp itself for this since each release represents a month. I think the term "newest" would fit that. Maybe @mrdoob could have some idea about this? |
|
The initial thought was based on experience. As a newbie my first behavior was to check the examples, over a short period I came back at least 100 times to the examples page as I had a better idea of what I was looking for in various cases. The current model simply hides the gems and precious updates. I believe this is pretty common for all newbie Three.js devs, some Google Analytics attribution data would confirm if we have it. A few more ideas on showing how vibrant our community is (if it makes sense):
|
Attempted to add a simple generate-timestamps node script and a timestamp-based sort by update date feature to the examples page. I believe new features and updates are getting lost on newcomers who are not regularly following the project. I am not a developer, so please feel free to ignore if this is irrelevant. Cheers.
