Proposed · Astro Knots WG
Part of: Hack & Ship
Why this exists
We started with a simple question: can a small team ship five client sites without each one becoming a snowflake? Six months in we've learned that the answer is "yes, but not the way the JS ecosystem tells you to."
A true monorepo with shared packages at runtime created more problems than it solved — every brand wanted its own treatment, and the abstraction tax was higher than the reuse benefit. Pure copy-paste was equally painful — bug fixes never propagated.
Astro Knots is the synthesis: pattern library by default, published packages where the abstraction is genuine. The first real package is @lossless-group/lfm (markdown pipeline). Everything else is @knots/* patterns you copy and adapt.
What we're building
A workspace where every site is a git submodule, deployable from its own repo.
@knots/*reference packages that sites copy from, not import.@lossless-group/*published packages where genuine sharing is justified (LFM is the first; more to come).A documented "pseudo-monorepo philosophy" so contributors don't accidentally re-introduce the abstractions we've explicitly rejected.
Working group expectations
Real client work is the input — patterns get extracted after they prove themselves in a paid engagement.
Be willing to delete a shared abstraction when it's not earning its keep. Reversal is part of the practice.