Seven levels of academic hierarchy, without seven screens

The challenge

Board, medium, standard, subject, chapter, unit and topic are structurally the same CRUD surface at seven different depths. Building a screen per level makes the codebase grow with the level count rather than with the concept - and guarantees seven places to fix every bug. The second problem was data: a question bank populated by hand never reaches useful size.

Our approach

One hierarchy manager, parameterised over the level, instead of seven near-identical pages. Spreadsheet bulk import was treated as a primary path rather than an admin convenience. The codebase is organised by feature module rather than by file type, so a feature is one directory, and the interface runs against a mock data layer so it can be built and demonstrated independently of the API.

What we built

• Seven-level academic hierarchy through one reusable manager
• Question bank typed and tagged by topic, difficulty and marks
• CSV/spreadsheet bulk import
• Question-paper generator and online exam scheduling
• Role-aware student and teacher management with an approval flow
• Performance and engagement reporting

The results

In development. The interface is complete across its feature modules and runs against a mock data layer; the API covers the question bank and hierarchy. Screenshots show demo data.