How fogsbridge/yogurt works
YogurT is represented here as two Vue frontend shells (web and admin) plus a Spring Boot server. The evidenced frontend workflow is application bootstrap, plugin/router registration, then rendering the shell’s RouterView; both routers currently declare empty route lists. The server excerpt only shows Spring Boot startup, with no demonstrated connection to either frontend or a database. The README names the product but documents no further capabilities, and the available excerpts do not establish domain behavior or API workflows.
Main entry points: src/main.js Admin bootstrap · src/main.js Web bootstrap · App.vue Web shell · index.js Web router
Components 9
Web frontend
- Web bootstrap
yogurt-web/src/main.js - Web shell
yogurt-web/src/App.vue - Web router
yogurt-web/src/router/index.js
Admin frontend
- Admin bootstrap
yogurt-admin/src/main.js - Admin shell
yogurt-admin/src/App.vue - Admin router
yogurt-admin/src/router/index.js - Admin styles
yogurt-admin/src/assets/main.css
Server
- Server startup
yogurt-server/src/main/java/com/fogsbridge/yogurt/server/YogurtServerApplication.java
Other components
- User
Connections 7
- Web bootstrap → Web shell: mounts
yogurt-web/src/main.js - Web bootstrap → Web router: registers
yogurt-web/src/main.js - Admin bootstrap → Admin shell: mounts
yogurt-admin/src/main.js - Admin bootstrap → Admin router: registers
yogurt-admin/src/main.js - Admin bootstrap → Admin styles: imports
yogurt-admin/src/main.js - User → Web bootstrap: uses
- User → Admin bootstrap: uses