How niharika2810/android-interview-questions works
Project type and purpose
• This repository is not a running application but an open‐source documentation/content project: a collection of Android/Java/DS/Kotlin/Android interview questions stored as Markdown files.
• Its purpose is to serve as a knowledge base and to let others read, learn, and contribute new questions or corrections via GitHub’s standard workflow.
File structure
• Top‐level components:
• .github/ contains issue‐/PR‐templates to standardize reporting and contributions.
• README.md is the main entry point for readers and shows content.
• CONTRIBUTING.md & CODE_OF_CONDUCT.md govern how to propose changes.
• LICENSE defines legal usage.
• images/ stores assets referenced by Markdown.
• No “src” or “backend” folder—this is purely a content‐management repo.
README for additional insights
• The README clearly lists categorized questions, links out to external resources, and calls for contributions.
• There is no build or deploy section, so CI/CD involvement is limited to PR checks (spelling, link-validation, templates) if configured.
Main components & interactions (to appear
a. Actors
1. Reader – browses the repository, reads questions.
2. Contributor – forks/clones, adds/edits questions, opens PR.
3. Maintainer (Reviewer) – reviews PRs, merges accepted changes.
4. CI Service (optional) – lints Markdown, checks link validity, enforces templates.
b. System Components
1. GitHub Repository (central content store)
2. .github/ (issue & PR templates)
3. Docs (README.md, category‐wise Q lists)
4. Images folder
5. CONTRIBUTING.md / CODE_OF_CONDUCT.md / LICENSE
c. External Services / Tools
1. Git/GitHub UI or CLI – for clone, commit, push, PR, merge
2. (Optional) CI Runner – GitHub Actions or other configured checks
Architectural patterns & design principles
• GitOps Pattern: content changes flow through branches & pull requests.
• Separation of Concerns:
• Content (Markdown Q&A)
• Process (issue/pr templates & guidelines)
• Assets (images)
• Extensibility Point: contributors can add new files or categories by following CONTRIBUTING.md rules.
• Actors on the left: Reader, Contributor.
• docs/ (README.md, Q-lists)
• images/
• .github/templates/
• meta-files (LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md)
• On the right, Maintainer and CI Service.
1. Reader → (clones or browses) → GitHub Repo → (reads) → Reader
2. Contributor → (fork/clone) → local → (commit/push) → PR to GitHub Repo
3. GitHub Repo → triggers → CI Service → reports pass/fail → Maintainer
4. Maintainer → (reviews) → accepts/merges → GitHub Repo → updated content