Where to Maintain This Repo

Summary

This repo has been maintained at TACC/Core-Styles and TACC/tup-ui:/libs/core-styles. Neither syncing the two nor using one or the other has been ideal.

Options

A. Maintain Only TACC/Core-Styles

✅ Obvious and intuitive usage or a library that has multiple clients.

• Library can be familiarly installed from NPM at reliable releases.
• Library can be easily installed at stages of development e.g. branch, commit, latest, pre-release, tag.

⚠️ Extra steps required to test TACC/Core-Styles on TACC/tup-ui.

• But this challenge exists for TACC/Core-Styles and TACC/Core-CMS and TACC/Core-Styles and TACC/Core-Portal
• See TACC/Core-CMS: Locally Develop CMS and Styles.

B. Maintain Only TACC/tup-ui:/libs/core-styles

⚠️ Extra steps required to test TACC/Core-Styles on TACC/tup-ui.

• But this challenge exists for TACC/Core-Styles and TACC/Core-CMS and TACC/Core-Styles and TACC/Core-Portal
• See TACC/Core-CMS: Locally Develop CMS and Styles.

⚠️ No simple and reliable way to install from a repo at a sub-directory.

1. obtuse command (arcane repair)
2. git submodules (team dislike)
3. third-party service (unreliable maintenance)

C. Maintain Both TACC/Core-Styles And TACC/tup-ui:/libs/core-styles

❌ Syncing architecture changes is common and difficult.

• Architecture changes are common because Core-Styles is still a Work in Progress (v0.11.0).

❌ Syncing pattern updates in both directions is tedious and cumbersome.

• TACC/tup-ui and TACC/Core-Styles may add or edit the same pattern.
• Tracking which patterns to sync in which direction is not worth the overhead.

❌ Maintaining two instances of one library should not be necessary.

• It seems like a failure of architecture, not a solution.