How rajivanandkhanal/student-resource-hub works
Project type + purpose (from file tree + README)
This is a Qt 6 C++ desktop application (“StudentResourcehub”) that appears to provide a student resource hub UI with multiple screens (landing page, register, profile, update info, about/contact pages).
It uses a local SQLite database file: StudentResourceHubDB/StudentResourceHubDB.db. There is no server/backend in the repo; everything is local to the desktop runtime.
Key indicators in the tree:
• Qt project file: StudentResourcehub/StudentResourcehub.pro
• Qt Designer UI files: *.ui (e.g., mainwindow.ui, register.ui, etc.)
• C++ Qt classes: *.cpp / *.h matching those UI screens
• Qt resource system: ProjectResources.qrc + Img/
• Build outputs: StudentResourcehub/build/... (should not be treated as architecture; they’re artifacts)
How to think about the architecture for diagramming this repo
• Actor (User)
• Desktop Application (Qt runtime + compiled exe)
• Presentation layer (Qt Widgets screens)
• Data layer (SQLite file access)
Desktop Application Container
StudentResourcehub.exe (Qt Widgets app)
• Entry point: main.cpp
• Main shell window: mainwindow.h/.cpp/.ui
Resource bundle (static assets)
• ProjectResources.qrc
Persistence / Database
• StudentResourceHubDB.db (SQLite)
Build/Tooling (keep separate or omit from main architecture)
• StudentResourcehub/build/..., Makefiles, moc_*.cpp, qrc_*.cpp, generated ui_*.h
• omit them, or
Architectural patterns/design principles to highlight (based on structure)
What the tree suggests:
• Qt Widgets + Designer-based UI: .ui forms compiled to ui_*.h
• Signal/slot event-driven interactions (typical Qt): user actions trigger slots in each screen class
• Single-process, local-first architecture: no network services in repo; persistence is local SQLite
• “Event-driven UI (Qt signals/slots)”
• “Embedded persistence (SQLite DB file)”
• “Resource-compiled assets (.qrc)”
• App Entry: main.cpp → “Application Startup”
• Shell / Navigation: mainwindow.* → “MainWindow (navigation host)”
• Screens:
• landingpage.*
• register.*
• profile.*
• updateinfo.*
• aboutus.*
• contactus.*
• firstpage.ui (screen-only)
• Resources: ProjectResources.qrc, Img/
• Database: StudentResourceHubDB/StudentResourceHubDB.db
• Ignore for runtime architecture: build/**, generated moc_*, ui_*, qrc_*