Please enable JavaScript.
Coggle requires JavaScript to display documents.
Architecture, TRENCHDEVS/APPS CORE (Open-Source), CORE TASKS, Philosophy…
Architecture
-
User Flow
-
- Domain & or subdomain resolved at an application level
- FE/routes will render the site accordingly depending on domain
Q&A
Why Laravel for the web app?
Capitalize on current knowledge + already built platform (trenchdevs/apps)
Why React for Admin/Auth routes?
There will come a time that (actually on trenchdevs today as well) dynamic user interaction would be one of the priority/requirement. having it on React will give us this flexibility on creating UIs and expand on mobile if needed (Ionic?)
Why plain old blade for public facing simple pages?
Speed, SSR support, Livewire for simple interactions & vue2 components sprinkling interactions whenever needed
-
CORE TASKS
- Refactor & Update trenchdevs/trenchdevs repo
- Add React support for Admin/Auth routes (via Cookies)
- Add Postgres Support & Migrations Support From Scratch
- Fork and make a closed-source repo for .com products (Proj. w/ JS).
-