Shared Component Library

BookNest's catalog page draws each book as a card, and an admin site for the shop's staff will draw the same cards. Copies of the CSS would drift apart, and an npm 2,036 package means a registry and a release for every one-line change. A third option is a small repository, booknest-ui, that both sites include at a version. Sam creates it beside BookNest, with a bare copy on the server:

git init -q ../booknest-ui && cd ../booknest-ui
# Add book-card.css and README.md
git add . && git commit -qm "Add the book card styles"
git tag -a v1.0.0 -m "booknest-ui 1.0.0"
git init -q --bare ../server/booknest-ui.git
git remote add origin ../server/booknest-ui.git
git push -q --follow-tags -u origin main
cd ../booknest

The library keeps its own history and release tags. BookNest needs to say "use booknest-ui at v1.0.0" in a way every clone reproduces, and to move to v1.1.0 on purpose, first with a submodule, then with a subtree.