How utnfrrodsw/desarrollo-de-software works
Project type and purpose
• This “DSW: Desarrollo de Software” repository is not a typical codebase but an information‐hub (static documentation) for a university software‐development course.
• Its purpose is to aggregate links to media channels (YouTube, Telegram) and related GitHub repos (TP, PoC, material‐BE, clases) and to provide scheduling and grading-policy details for students and faculty.
File structure
• Top level contains only LICENSE and README.md.
• No source code or build scripts—this is a static documentation site hosted on GitHub (often via GitHub Pages).
• The README acts as the sole “content” component, linking out to other services and repositories.
README for additional insights
• Sections: Media links, repos, faculty list, grading rules, timelines.
a. Main components
• Documentation Hub (the README + GitHub Pages static site)
• External Code Repositories (TP, PoC, material-BE, clases)
• Media Platforms (YouTube channel & playlists, Telegram group)
• Users (Students, Professors)
b. Relationships & interactions
• Users → access Documentation Hub (GitHub Pages)
• Documentation Hub → links out to External Code Repos
• Documentation Hub → links out to YouTube & Telegram
• Users ↔ interact directly with External Code Repos (clone, issues, PRs)
• Users ↔ consume media on YouTube & Telegram
c. Architectural patterns & principles
• Static site hosting (no backend logic): all content is client-side.
• Link‐aggregation pattern: a central portal that redirects/links to specialized subsystems.
• Separation of concerns: documentation vs. code repos vs. media platforms.
d. Key technologies & services
• GitHub Pages (static host), Markdown (README)
• GitHub Repositories (TP, PoC, material-BE, clases)
• YouTube Data API (implicit integration)
• Telegram Bots/API (for group integration)
• Web browsers and Git clients as user interfaces