How yunusemreerkesikbas/admincraft works
Project type and purpose
• This is a full-stack CMS/admin dashboard project named AdminCraft.
• The backend is a Spring Boot (Java/Maven) application exposing MVC controllers and REST endpoints.
• The frontend is an Angular application configured for both client-side rendering (CSR) and server-side rendering (SSR via Angular Universal + Express).
File structure
Top-level:
• backend/ – Spring Boot service
– src/main/java/com/admincraft/cms – application entrypoint (AdminCraftApplication.java), config (SecurityConfig), generic core (BaseEntity/Repository/Service), exceptions, modules (home)
– src/main/resources – application.yml, Thymeleaf templates (index.html)
– pom.xml, Maven wrapper
• frontend/ – Angular Universal app
– src/app – components, routing (app.routes.ts/server), config (app.config.ts), SSR entrypoints (main.server.ts, server.ts)
– angular.json, package.json
• README.md, roadmap.md
README for additional insights
• Minimal README (“# AdminCraft”) – no built-in architecture notes, so we infer from code.
• Break the system into the frontend SSR server, the Angular app (SSR + CSR), the backend service (layered), and the database.
• Interactions, including security filtering and template serving.
• Technologies (e.g., “Spring Security,” “Thymeleaf,” “Angular Router”).