How shklpsh/30-days-of-python works
Project type and purpose
• This is an educational “30 Days Of Python” challenge repository.
• It delivers 30 sequential lessons (each in its own Day_X folder), code-examples (.py), Markdown tutorials (.md), translations (Chinese, Korean, Portuguese), datasets (data/), example packages (mymodule.py, mypackage/), and a small Flask-based demo web app (python_for_web/).
• It’s not a monolithic production service but rather a content-and-code learning platform plus a demonstration web app.
Top-level structure and patterns
• Day modules (01_Day_… to 30_Day_…): each holds a lesson .md and sample .py.
• Translations: Chinese/, Korean/, Portuguese/ mirror core lessons in other languages.
• data/: CSV, JSON, text datasets used in exercises and examples.
• mymodule.py and mypackage/: example Python package illustrating modules & imports.
• python_for_web/: a Flask demo with Procfile, app.py, requirements.txt, templates/, static/ showing an MVC-style web microservice.
• images/: banners and screenshots embedded in the README and lessons.
Core components
A. Content Repository
• Lesson Modules (Day 1–30)
• Translations (CN, KR, PT)
• Static Assets (images/, files/)
B. Code Examples & Packages
• Python scripts (.py)
• Example Packages (mymodule.py, mypackage/)
• Sample data (data/)
C. Demo Web Application (python_for_web/)
• Flask Application Server (app.py)
• Templates (templates/)
• Static files (static/css, …)
• External Procfile / requirements.txt
D. External Services & Tools
• Python Interpreter
• VS Code (editor)
• GitHub (host/repository & Git)
• Static site generator or GitHub Pages (if used)
• Telegram & YouTube (community & video resources)
• PayPal (support link)
Relationships and data flows
• Developer clones the Git repo (GitHub) → Local FS holds all modules, data, web app.
• Python interpreter executes:
• Lesson scripts for exercises → STDOUT / files
• data/ files for analytics demos (pandas, web scraping)
• mymodule/mypackage as importable modules
• Flask app listens (Procfile) → serves HTTP requests using templates/static.
• Viewer/User uses browser to read .md content (on GitHub Pages or local Markdown viewer).
• Community links (Telegram, YouTube) drive into the content.
Architectural patterns & design principles
• Modular lesson structure: one folder per day → clear separation of concerns.
• Content vs. Code separation: .md vs .py
• MVC in demo web app:
• Model: data loading from data/ or MongoDB (27th Day)
• View: Jinja2 templates & static CSS
• Controller: Flask routes in app.py
• Package structure: demonstrates __init__.py, module imports, enabling reusability.
Final advice
• Every folder as a logical component, group by function (lessons vs translations vs data vs web demo).
• Don’t over-architect: this is primarily a content-and-code repository with a side demo app.