How statickidz/temariodaw works
Project type and purpose
• This is not an executable “application” in the usual sense but a static course‐materials repository (“Temario DAW”) containing PDFs, ZIPs and other assets organized by subject (BBDD, DAW, DIW, etc.).
• Its purpose is to store, version and serve educational content for the “Desarrollo de Aplicaciones Web” module (and related topics).
File structure
• Top‐level:
• .github (CI/CD configuration)
• BBDD, DAW, DIW, DWEC, DWES, EED, EIE, FOL, LLMM, PROG, SSII – each containing lecture PDFs and exercises
• README.md
• No server‐side code; the content is purely static.
• Likely deployment via GitHub Pages (or another static‐site host).
• No database, no backend services.
README for additional insights
• Confirms that this is a static syllabus/notes repository.
• Points to José Luis Comesaña’s site as original source.
• No mention of build tooling—presume Jekyll (GitHub Pages default) or simple direct file hosting.
a. Main components
1. Version Control Repository (GitHub)
2. CI/CD (GitHub Actions or other)
3. Static‐Site Generator (e.g. Jekyll) – optional
4. Static File Host / CDN (GitHub Pages, Netlify, S3+CloudFront)
5. End Users (Students / Browsers)
b. Relationships & data flows
• Developers (maintainers) commit updates to the GitHub repo →
• CI/CD pipeline (if any) triggers build →
• Static‐site generator processes Markdown/ directory structure into HTML/CSS/JS + assets →
• Artifacts deployed to static host / CDN →
• End user browsers request content via HTTP(S) → CDN serves HTML, PDF, ZIP, etc.
c. Architectural patterns & design principles
• GitOps / Git‐driven deployment
• Static hosting (pre‐rendered assets) for scalability and security
• Separation of concerns: content (repo), build (CI), delivery (CDN)
d. Relevant technologies/frameworks
• Git / GitHub
• GitHub Actions (or equivalent CI/CD)
• Jekyll (or Hugo) static‐site generator if dynamic nav is needed
• GitHub Pages / Netlify / AWS S3 + CloudFront
• Optional: Google Analytics for usage metrics