How haimonvieira/desenvolvimento-de-software-multiplataforma works
Project type and purpose
• This is not a traditional software application but rather a content‐repository for academic materials (PDFs, slides, exercises, simple HTML demos) organized by semester and discipline.
• Purpose: provide a structured storage and navigation for teaching resources across multiple courses.
File structure
• Top‐level:
• DSM1/ (first‐semester disciplines)
• README.md
• Under DSM1/ each folder (ALP, DD, DW1, ES1, MBD, SORC1, PI) represents a distinct course and contains subfolders for “Materiais”, “Exercicios”, “Slides”, “Programas”, etc.
• Only DW1/ contains small HTML sites and CSS assets—indicative of demo web content.
• No build scripts or backend code are present—content is static.
README for additional insights
• Confirms this is a course material repository.
• No mention of an automated build or deployment pipeline.
• Navigation is manual: pick a discipline, then view materials.
a. Main components
1. Content Store (Git repository holding PDFs, DOCX, HTML, CSS)
2. Static Site Generator (optional—Jekyll/Hugo) or CMS (e.g., Netlify CMS)
3. Continuous Integration / Deployment pipeline (e.g., GitHub Actions)
4. Hosting/CDN (e.g., GitHub Pages, Netlify, AWS S3 + CloudFront)
5. End‐User Web Browser
b. Relationships & interactions
• Developer/Instructor commits new files → Git repo
• CI picks up changes, invokes Static Site Generator
• Generated static HTML/CSS/asset bundle deployed to Hosting/CDN
• End‐User browser requests pages from CDN
c. Architectural patterns
• Static content architecture (no runtime server)
• Repository‐driven documentation
• CI/CD for automatic rebuilds and deployments
d. Key technologies
• Git/GitHub for version control
• Markdown/PDF/HTML/CSS as content formats
• Jekyll or Hugo as static‐site generator (optional)
• GitHub Actions or Netlify Build for CI/CD
• GitHub Pages/Netlify/AWS S3 + CloudFront for hosting