How faridrashidi/kaggle-solutions works
Project Type and Purpose
• This is a static site generator project built with Jekyll, intended to compile and present a comprehensive list of Kaggle competition solutions.
• Markdown files in resources/, YAML data in _data/competitions.yml, and HTML templates under _layouts and _includes produce the final static pages.
Main Components
• Content & Data Layer
• resources/ (kernels.md, symbols.md, videos.md)
• _data/competitions.yml (structured competition metadata)
• Template Layer
• _layouts (default.html, resource.html)
• _includes (header.html, footer.html, head.html)
• Asset Layer
• assets/css/ (Bootstrap, custom styles)
• assets/images/, assets/logos/
• Script Layer
• _scripts/extract.py (possibly updates or extracts competition data)
• Configuration
• _config.yml (Jekyll settings)
• Build Engine
• Jekyll (Ruby-based static site generator, invoked via bundle install / jekyll build)
• Version Control & Hosting
• GitHub repository + GitHub Pages for deployment
Component Interactions
1. Data & Markdown files feed into Jekyll, guided by _config.yml.
2. Templates (_layouts & _includes) render that content into HTML.
3. Assets (CSS/images) are copied into the output.
4. The build script (extract.py) may preprocess or refresh _data/competitions.yml.
5. Resulting static site is pushed to the gh-pages branch or served directly by GitHub Pages.
6. End users browse the rendered HTML over the web.
Architectural Patterns & Design Principles
• Static Site Generation: separation of content, template, and assets.
• Convention over Configuration: Jekyll directory naming drives build.
• Single responsibility: scripts only handle data extraction; templates only handle presentation.