🗂️ Devantler’s Monorepo

Every project I actively work on, gathered in one place.

The public Devantler Tech website is owned by business-site, checked out at applications/business-site. Its source, checks and independent GitHub Pages publication live there; this monorepo aggregates a reviewed source pin without triggering publication. Repository-wide architecture decisions stay in docs/adr/.

Each project stays its own repository and is linked here as a submodule: a pointer to a reviewed commit in that repository. A normal clone contains the aggregator’s guides and those pointers, not every project’s files. Populate only the projects you need; each keeps its own access, contribution rules, issues and releases.

Getting started

You need Git to read the aggregator. The public checkout does not require SSH credentials or access to every project:

git clone https://github.com/devantler-tech/monorepo.git
cd monorepo
git submodule status

An initial - beside a project means its checkout is not populated; it is not a clone failure. See the portfolio map for project ownership, or start with docs/ for aggregator architecture records.

To read a project’s pinned source inside the aggregator, you also need Bash and access to that repository. For example, the public website submodule uses HTTPS:

bash .claude/scripts/submodule-init.sh applications/business-site

Most other entries in .gitmodules use SSH and therefore need GitHub SSH authentication; some repositories require additional access. HTTPS works for public repositories and can also authenticate private access. Initializing every submodule is optional, not a public onboarding requirement. Prefer a project’s own public repository and contribution guide when you want to change that product rather than inspect the aggregator’s pin.

Working safely with pinned projects

Use submodule-init.sh, not bare git submodule update --init or a recursive clone. The helper populates an empty repository at its recorded pin. For an existing checkout, it repairs Git worktree configuration and checks isolation without moving the checkout to a different pin. The plain Git initialization path can leave parallel sessions resolving to the same physical folder. Read worktree isolation before project edits.

A detached checkout at the recorded commit is expected. It is a source snapshot, not your work branch: create an owned, isolated work branch from the product’s fresh default branch before editing it. The contributor guide separates aggregator and product contributions.

Each project is pinned to a specific commit, and your checkout stays on that pin. Automated pull requests here move the pins forward, but **your existing checkout does not follow — and re-running