How datasciencenigeria/dsn-50-days-of-learning-2023 works
Project type and purpose
• This is not a running application but a content‐repository for a 50-day online learning program (“DSN and Microsoft-50-days-of-Online-Study-2023”).
• It consists of four separate course modules (Machine Learning with Microsoft Azure, Microsoft Power Apps, Microsoft Power BI, Machine Learning with Python), a root README that ties them together, and shared media assets in an images folder.
• Its purpose is to host and publish static course materials, with links out to registration, Slack/Telegram channels, and social-media invites.
File structure
• Top level:
• LICENSE (project license)
• README.md (program overview & links)
• images/ (shared pictures & logos)
• Four subdirectories, each containing a course’s README.md and, presumably, day-by-day lesson files.
• There are no code files, build scripts, or dynamic back-end services—this is purely a Markdown-based static content repo.
README for additional insights
• Describes the 50-day program, its four tracks, objectives, prerequisites, audience, and registration/distribution channels.
• Calls out external integrations: registration (Bitly link), Slack channel, Telegram channel, Twitter.
a. Content Repository (GitHub)
b. Static Site Generator (SSG) or Markdown renderer (e.g., GitHub Pages / MkDocs)
c. Hosted Site / CDN (GitHub Pages or equivalent)
d. End-User (Learner) via Web Browser
e. External Services & Links:
• Registration Form (Bitly → external registration)
• Community Channels (Slack workspace, Telegram channel)
• Social Media (Twitter sharing link)
f. Shared Assets Store (images/ folder, could be served via CDN)
Relationships and interactions
• Content Author → pushes Markdown & images to GitHub (repo).
• On push → SSG pipeline (e.g., GitHub Pages) builds static HTML/CSS/JS.
• Built site → deployed to hosting/CDN.
• Learner uses a web browser to navigate to the site.
• Learner clicks links to register → directed to external registration service.
• Learner joins Slack & Telegram via invite links from site.
• Learner can tweet course info via embedded Twitter link.
Architectural patterns & design principles
• “Content-as-Code” pattern: everything lives in Git, versioned as Markdown.
• Static-site delivery: no custom back-end, leveraging built-in hosting.
• Clear separation of concerns:
– Content modules (courses)
– Shared assets (images)
– Distribution & community channels
Relevant technologies & frameworks
• Markdown for content
• Git & GitHub for version control
• GitHub Pages (or any static site generator) for build & deploy
• Bitly for registration link shortening
• Slack API (invite link) & Telegram deep links
• Twitter intent URL for social sharing