How saumy1905/pyqfort works
Project type and purpose
• This is an open-source repository (PYQFort) that provides a centralized collection of PDF question papers (PYQs) for various B.Tech. courses.
• It relies purely on static file storage in a GitHub repository and uses standard Git/GitHub workflows for contribution and distribution.
File structure
• The top-level folders ( “01. 1st & 2nd Sem…”, “02. Computer Engineering”, “03. IT”, …) correspond to branches/majors and semesters, each containing subject directories and PDF files.
• There are no code modules, build scripts, or runtime components—just hierarchical content.
• The presence of README.md at the root describes usage and contribution flow. No CI/CD or dynamic back end is defined.
README for additional insights
• It documents two primary use cases:
a. End users browsing/downloading PYQs via mobile or desktop GitHub UI.
b. Contributors forking, branching, adding new files, and issuing pull requests.
• It mentions nothing about servers, databases, or automated pipelines—purely Git/GitHub-based.
a. Main components
• GitHub Repository (Central Storage): Hosts the entire directory tree of PDFs and metadata (README.md).
• Contributors: Fork–clone–branch–commit–push–pull-request workflow.
• Review/Maintainers: Merge pull requests into main.
• End Users:
• Viewing/downloading via GitHub web UI or mobile browser.
• Cloning repository locally to access offline.
• External Services: Optional analytics or sponsor banner (GitAds in readme).
b. Relationships and interactions
• (Optional) GitAds integration reading README.md for ad placement.
c. Architectural patterns / design principles
• Content repository pattern: Static content + version control.
• Fork-and-PR collaboration: Standard open-source contribution model.
• File-based hierarchy: No database, all metadata implied from directory naming.
d. Key technologies / frameworks
• Git (distributed version control)
• GitHub (hosting, pull-request workflow, static content delivery)
• Markdown for documentation (README.md)
• PDF as content format
Detail
• Both read paths (user downloads) and write paths (contributor commits).
• external endpoints (raw file URLs, sponsor ad endpoints).