How microsoftlearning/pl-300-microsoft-power-bi-data-analyst works
Project type and purpose
• This repository is not a running application or microservice-based system; it is a content‐centric, documentation and lab file repository for the PL-300 Microsoft Power BI Data Analyst course.
• Its purpose is to store and publish:
• Hands-on lab files (PBIX, SQL backups, CSVs, PowerShell scripts) under Allfiles/
• Lab and demo instructions (Markdown) under Instructions/
• GitHub metadata for collaboration (.github/)
• A Jekyll/GitHub Pages site configuration (_config.yml, index.md, readme.md, _build.yml)
File structure
• Top-level directories:
• .github/ → PR and Issue templates, contributor docs
• Allfiles/ → course assets:
– DatabaseBackup/, Demos/, Labs/, Resources/, Setup/
• Instructions/ → Markdown guides for Demos and Labs
• Configuration files:
• _config.yml and _build.yml indicate a static site build (likely Jekyll)
• index.md and readme.md drive the GitHub Pages homepage
• No backend code or service APIs; content is static, version-controlled, and delivered as downloads or via a static site.
README for additional insights
• Confirms the repository is for open contributions by MCTs (trainers), using GitHub pull requests.
• Mentions a separate “Docker-Build” repo for building lab instructions, but in this repo the build is a static site pipeline.
• No runtime components; emphasis on updating content as Power BI evolves.
a. Main components
• GitHub Repo
– Source of truth: all Markdown, lab files, assets
– .github/ for collaboration workflows
• CI/CD Pipeline (GitHub Actions)
– Triggers on push or PR, runs _build.yml to build the site
• Static Site Generator
– Jekyll (or equivalent) transforms Markdown and assets into HTML/CSS/JS
• Hosting
– GitHub Pages serves the generated site at https://microsoftlearning.github.io/PL-300-Microsoft-Power-BI-Data-Analyst/
• Consumers
– MCTs (trainers) clone/download the repo or browse the site
– Students (indirect) receive lab files from trainers
b. Relationships and interactions
• Authors push commits → GitHub → CI pipeline → build HTML → deploy to GitHub Pages
• Consumers clone repo for local labs or browse published site for instructions
• PR/Issue templates guide collaboration back into the GitHub Repo
c. Architectural patterns and design principles
• Single repository hosting both content and site code
• Static site generation for low-maintenance publishing
• GitOps workflow: version control, CI/CD, automatic deployment
• Clear separation of content (Allfiles/, Instructions/) vs. build config (_config.yml, _build.yml)
d. Technologies, frameworks, or libraries
• GitHub and GitHub Pages
• Jekyll (implied by _config.yml) or similar static site generator
• GitHub Actions (defined in _build.yml)
• Markdown (.md) for instructions and docs