How pulkit1822/geeksforgeeks works
Project Type & Purpose
• This is an open-source, content-centric repository (“Geeksforgeeks-Practise”) containing solution code and problem statements organized by topic and difficulty.
• Purpose: serve as a reference for C++/Java solutions to Geeksforgeeks problems, with each problem in its own folder alongside a README describing the question.
File Structure Analysis
• Top-Level Components:
• .github (GitHub configuration / funding)
• README.md (project overview)
• LICENSE
• assets (media, e.g., gitflow.mp4)
• Category folders: Basic, Difficulty, Easy, Medium, Hard, School
• Inside each Category folder:
• One subfolder per problem, named by problem title.
• Each problem folder contains:
– README.md (question text)
– One or more solution files (.cpp, .java, .py, etc.)
• Consistent naming patterns facilitate navigation and modular addition of new problems.
Insights from README
• The repository is regularly updated (“Daily Updates”).
• Solutions are organized by date/problem name.
• Contributions via GitHub issues and pull requests are welcomed.
a. Main Components
• GitHub Repository (hosted on GitHub)
• Local Development Environment (developer’s IDE / clone)
• File System Modules:
– Category Modules (Basic, Easy, Medium, Hard, School)
– Problem Modules (subfolders per problem)
– Shared Assets (common images, videos)
• Documentation (README.md at root + per-problem READMEs)
• Contributors (external developers submitting PRs)
b. Relationships & Data Flow
• User / Contributor ↔ GitHub: forks, clones, PRs, issues
• Local Dev ↔ File System: read/write problem modules, update READMEs
• GitHub Actions (if any CI/CD): runs on PRs (not present here but can be added)
c. Architectural Patterns & Principles
• Modular organization: each problem is an independent module.
• Convention over configuration: directory naming dictates inclusion.
• Separation of concerns: code vs. documentation vs. assets.
• Version control centric: Git history drives updates.
d. Key Technologies
• Git / GitHub for VCS and hosting
• Markdown for documentation
• C++, Java (primary languages for solutions)
• (Optional) Continuous Integration if added via GitHub Actions
Capturing Essential Elements
• Two main “systems”:
1) GitHub Hosting (remote)
2) Local FS + IDE (developer’s machine)
• How documentation and code coexist in each module.
• How new problems (modules) plug into the structure without disrupting existing ones.