Repository navigation
Add Interior archive category and highlight latest showcases - #92
Merged
Merged
Conversation
Collaborator
Author
|
CI verified for commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
updatedAtdates, newest first, across standalone experiences, PixiJS, and procedural Three.js studies. Dates come from the showcases' repository history, not the deployment date.#/x/<id>deep links. Direct exhibit links omit the discovery strip.Verification
img2interiorreturns the living-room showcase. The highlighted living-room link opens/living-room/.#/x/crown-chestselects Crowned Loot Chest, omits the latest strip, and creates its viewer canvas.Local build environment note
The local native Node 24 build reached the source-archive plugin after successful prebuild/TypeScript/Vite compilation, then hit a recursive AST traversal stack limit. Completed source generation and all postbuild checks with:
No build configuration, dependency versions, lockfiles, generated bundles, or model assets are changed in this PR. The standard
npm run buildinvocation did not exit successfully in that local Node 24 environment; the follow-on commands above did.