Astro Knots
A pseudomonorepo for the age of AI-assisted development. Speed up delivery by co-locating projects with shared patterns, dependencies, and documentation under one roof.
Why a Pseudomonorepo?
Not a true monorepo. Not a loose collection of repos. A pseudomonorepo gives you the visibility and pattern-sharing benefits of co-location without coupling deployment or forcing shared dependencies where they don't belong.
Accelerate with Shared Patterns
Co-locate projects with similar features, dependencies, and needs. Abstract what works into reusable patterns -- extended markdown render pipelines, CSS token conventions, OpenGraph and SEO optimization techniques -- without forcing premature abstraction.
Context Vigilance
Maintain structured, AI-friendly documentation that travels with the workspace. Specs, blueprints, prompts, and reminders give both human collaborators and AI code assistants the context they need to make informed decisions across every project.
Build in Public, Ship in Private
Share learnings, patterns, and context openly while keeping client-specific projects private. Each site is its own git repository, independently deployable -- the pseudomonorepo is a development convenience, never a deployment requirement.
Packages from Authentic Need
Don't guess what should be shared. Develop true packages only when real developer needs prove the value. Our first: @lossless-group/lfm -- a shared markdown processing pipeline born from building the same render logic across six sites.
Sites in the Workspace
In progress
Nested astro-site
Selective Package Sharing.
Lossless Flavored Markdown: A Shared Processing Pipeline
When code genuinely needs to be shared -- not just copied -- we publish it. @lossless-group/lfm bundles unified, remark-parse, remark-gfm, remark-directive, and custom plugins into a single import. Sites install it as a real dependency from GitHub Packages or JSR.
Patterns Over Dependencies.
Copy, Adapt, Own: A Practical Component Strategy
Not everything should be a shared package. UI components, layouts, and styles are better copied and adapted per site. @knots/* pattern packages serve as a cookbook -- reference implementations you browse, copy into your site, and make your own. No runtime coupling, no abstraction overhead.
Independent Deployment.
Each Site Ships on Its Own Terms
Every project deploys directly from its own repository via Vercel -- no knowledge of the pseudomonorepo required. Published packages are installed from registries, not workspace links. The workspace is a development accelerator, never a deployment dependency.
Context-Driven Development.
Specs, Blueprints, and Prompts Guide Every Decision
The context-v/ directory holds living documentation -- formal specs, architecture blueprints, implementation prompts, and reminders -- that travels with the workspace. AI assistants and human collaborators alike can reference these documents to understand the why behind every pattern.