How wreckage0907/sdot works
Project type and purpose
• This repository (“SDOT”) is not a traditional full-stack application but rather a static documentation/site generator combined with a curated collection of Python solutions for algorithmic problems (likely LeetCode).
• It uses a codes directory for Python scripts, a Jekyll configuration (_config.yml), and a GitHub Actions workflow (.github/workflows/generate_readme.yml) to auto-generate or update documentation (README).
File structure
• Top level:
• .github/workflows/generate_readme.yml: CI pipeline to regenerate the README from codes/ (or similar).
• _config.yml + index.md: Jekyll configuration and content for a GitHub Pages–hosted site.
• codes/: folder containing ~60 standalone Python scripts, each solving a separate problem.
• README.md: the root readme (likely auto-populated by the workflow).
• Patterns:
• “codes” directory is the core content.
• GitHub Actions → read code files → regenerate central documentation.
• Jekyll → static site generator → index.md plus any templates (not shown) → HTML pages.
README
• The README only shows “# SDOT,” implying it’s primarily auto-updated by the workflow.
• No explicit architectural description, so we infer from file names and workflow.