How akram6t/cdac_material works
1. What this repo is
- This is a static study-material repository for CDAC-related exam prep content.
- The architecture is content-first: each topic/mock test is a standalone page rather than part of a dynamic application.
2. Top-level organization
- The repository is split by subject/domain folders:
- cpp/
- java/
- dsa/
- dbt/
- dotnet/
- advjava/
- osc-sdm/
- Each folder acts as a logical module containing related learning material and mock exams.
3. Primary content units
- Most deliverables are HTML pages such as mock1.html, cpp_oops.html, java_jvm.html, etc.
- Some areas also include Markdown/MDX topic docs like advjava/topics.md, java/java_all_topics.md, and dotnet/basics.mdx.
- This suggests a mix of authoring formats but the published output is primarily static pages.
4. How users navigate the content
- The root README.md acts as a catalog/index page.
- It lists every subject and links to the corresponding hosted page under https://cdac-material.vercel.app/....
- So navigation is directory-driven and manual, not generated by a backend or database.
5. Route and page structure
- Each file maps directly to a public path, for example:
- /cpp/cpp_basic_mock.html
- /osc-sdm/mock1.html
- /java/java_collections.html
- The repo therefore behaves like a static website with file-based routing.
6. Content boundaries
- Subject areas are intentionally isolated:
- C++ mock pages stay inside cpp/
- Java material stays inside java/
- OSC-SDM mocks stay inside osc-sdm/
- There is no sign of shared application state or cross-subject processing; each page is effectively self-contained.
7. Likely delivery model
- The README links point to a vercel.app domain, so the repo is almost certainly deployed as static hosting.
- The architecture is therefore: repository content → static build/publish → Vercel-hosted pages.
8. No backend or service layer visible
- There is no evidence of APIs, databases, authentication, or server-side logic.
- The “data flow” is simple: a user opens a static URL, and the hosting platform serves the corresponding HTML/MDX-rendered page.
9. Special standalone assets
- sunbeam_pune_and_karad_cmce_ranks.html is a root-level page, separate from the subject folders.
- project_document.html also appears to be a standalone page, likely supporting documentation or project-level reference material.
10. Practical architecture diagram view
- The cleanest diagram would show:
- Repository source content at the center
- Multiple subject folders as independent content modules
- A README index/catalog pointing to them
- A static hosting layer (Vercel) publishing each file as a public page
- End users consuming the pages through direct links
Main entry points: README.md README · cpp_oops.html C++ pages · java_all_topics.md Java docs · mock1.html OSC mocks
Components 18
Source content
Static study material and indexes
- README · Root catalog that links all subjects and public pages
README.md - C++ · Standalone C++ study pages and mocks
- Java · Java topic pages and reference material
- DSA · Data structures and algorithms mock content
- DBT · DBT mock exam pages
- .NET · .NET basics and topic notes
- Adv Java · Advanced Java topic notes
- OSC-SDM · Operating systems and system design mock series
- Standalone docs · Repo-level pages outside subject folders
project_document.html - C++ pages · Core C++ mock and theory pages
cpp/cpp_oops.html - Java docs · Java topic and reference pages
java/java_all_topics.md - OSC mocks · Sequence of OSC-SDM mock exam pages
osc-sdm/mock1.html - .NET docs · .NET topic notes in mixed markdown formats
dotnet/basics.mdx - AdvJava notes · Advanced Java topic documentation
advjava/topics.md - DBT mocks · DBT mock exam pages
dbt/dbt_mock1.html - DSA mock · DSA mock page
dsa/dsa_mock.html
Delivery
Published static hosting and readers
- Vercel hosting · Static deployment that serves each file as a public page
- Readers · Users opening the catalog and subject pages
Connections 25
- Readers → README: open catalog · Readers start from the root index
- README → C++: links · Catalog points to the C++ section
- README → Java: links · Catalog points to the Java section
- README → DSA: links · Catalog points to the DSA section
- README → DBT: links · Catalog points to the DBT section
- README → .NET: links · Catalog points to the .NET section
- README → Adv Java: links · Catalog points to the Advanced Java section
- README → OSC-SDM: links · Catalog points to the OSC-SDM section
- README → Standalone docs: links · Catalog also references repo-level pages
- C++ → C++ pages: contains · C++ content is organized as multiple standalone pages
- Java → Java docs: contains · Java content mixes topic docs and pages
- OSC-SDM → OSC mocks: contains · OSC-SDM is primarily a mock-test series
- .NET → .NET docs: contains · .NET area includes markdown and MDX notes
- Adv Java → AdvJava notes: contains · Advanced Java area centers on topic notes
- DBT → DBT mocks: contains · DBT area contains mock exam pages
- DSA → DSA mock: contains · DSA area contains a mock page
- README → Vercel hosting: published via · Catalog entries map to hosted static pages
- C++ pages → Vercel hosting: served by · Static host serves each content file directly
- Java docs → Vercel hosting: served by · Static host serves each content file directly
- OSC mocks → Vercel hosting: served by · Static host serves each content file directly
- .NET docs → Vercel hosting: served by · Static host serves each content file directly
- AdvJava notes → Vercel hosting: served by · Static host serves each content file directly
- DBT mocks → Vercel hosting: served by · Static host serves each content file directly
- DSA mock → Vercel hosting: served by · Static host serves each content file directly
- Vercel hosting → Readers: delivers · Readers consume the published static pages