Skip to content

Refactor MySTRA as a publication-only adapter - #17

Draft
lhparker1 wants to merge 1 commit into
mainfrom
agent/myst-consolidation
Draft

Refactor MySTRA as a publication-only adapter#17
lhparker1 wants to merge 1 commit into
mainfrom
agent/myst-consolidation

Conversation

@lhparker1

@lhparker1 lhparker1 commented Aug 5, 2026

Copy link
Copy Markdown
Member

Summary

  • define MySTRA as a portable ASTRA-to-MyST publication adapter rather than a project viewer
  • give hidden resolved-store carriers page-unique identifiers while preserving the stable astra-store class contract
  • tighten documentation and tests around the viewer/publication boundary

Verification

  • npm test — 102 tests passed
  • npm run build

Product boundary

  • MySTRA (this PR): converts ASTRA records into portable MyST publication content and page-local resolved stores.
  • astra-theme #7: renders that publication content as the paper/book experience.
  • astra-viewer: owns host-neutral project inspection, inventory, record-detail, and result-viewer components.
  • jupyterlab-astra: hosts the shared viewer packages inside JupyterLab without importing the publication theme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant