docs: clarify public portfolio entry points#157
Merged
Conversation
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.
What
Why
The portfolio bundle is now ready enough to be discoverable from the repo root, but the public path still had friction: the README did not point to the sanitized demo package, and several docs implied the gitignored PPTX was a committed artifact.
How
docs/demo/sanitized-demo-plan.md,docs/portfolio/README.md, anddocs/demo/portfolio-handoff-bundle.mdfrom the root README.sofficefallback command.Testing
pnpm exec prettier --check README.md docs/portfolio/README.md docs/deck/README.md docs/deck/REHEARSAL.md docs/demo/portfolio-handoff-bundle.md docs/case-study.mdnode scripts/ci/check-workstation-preflight.mjsnode scripts/ci/check-workflow-command-drift.mjsnode scripts/ci/check-version-parity.mjspnpm health:repoRisks
Low. Documentation-only change. The only notable behavior is expectation-setting: public docs now point to the committed PDF preview rather than the local gitignored PPTX.
Performance impact
None expected. Documentation-only change; no runtime assets, UI, API, database, or bundle logic changed.
Lockfile rationale
No lockfiles changed.
Screenshots
Not applicable. Documentation-only change; no UI surface changed.