The deployable code lives in a conventional monorepo layout:
apps/backend— the Go APIapps/webapp— the PWA frontend (in progress; replacesapps/mobileapp-legacy, the retired Ionic 3/Cordova app kept around for reference during migration)apps/gis— geodata scripts/tooling
The business/marketing/architecture documentation below still uses a TOGAF-flavored structure (business/, technology/, application/logical/) — this part of the tree also doubles as the source for the project's Jekyll site (see _config.yml), so it's kept separate from the apps/ code layout rather than merged into it.
These applications are deployed within the solution, are specificially written for it and far from off-the-shelf.
./apps/mobileapp-legacy (being replaced by ./apps/webapp)
I am a business administration guy by trade and can't help but spot "biz" where I see it. Th latest when hardware comes into play there is purchasing, maybe even a boll of materials 'BOM' and it doesn't help to put the customer user is in focus the terminology just fits.
This folder is typically used by scripts in ./apps to hold data in a predictable place. I tend to do a lot of curl'ing with checks for If-Modified-Since to be nice to the (mirror) servers.
About off-the-shelf technology used by the project.