How ajshooting/vtuber-palette works
Main Components
• Frontend/UI:
• Assets: index.html, search.html, search.js, app.js.
• Auto-Update Module:
• Contains: Python scripts located in auto-update/ (with subdirectories for “seesaawiki.jp”, “vtuberinfo.net”, “wikiwiki.jp” etc.).
• Data Store:
• Assets: CSV files in “colordict” (each representing different VTuber agencies or groups) and “source.csv”.
• Purpose: Provide the core dataset that is used by the frontend to generate the visuals.
• Deployment & CI/CD:
• Contains: GitHub workflows (in .github/workflows) that may automatically trigger and run the auto-update scripts.
• Purpose: Automate periodic data fetching and ensure updated CSV files are committed/published.
Relationships & Interactions
• The auto-update module runs independently (likely on a schedule defined in the GitHub workflows) to scrape external VTuber information and update the CSV data in “colordict” and “source.csv.”
• The CI/CD pipeline (GitHub workflows) coordinates the scraping and updating process so that the front-end displays the latest information.
• Data flows from external websites → auto-update scrapers → CSV Data Store → frontend visualization.
Architectural Patterns and Design Principles
• Separation of concerns: The project clearly separates the UI (static assets and JavaScript) from the data acquisition layer (Python-based scrapers).
• Scheduled/automated data ingestion: Use of GitHub workflows to trigger automated tasks.
• Data-driven visualization: The front-end is designed to be data-centric, reading parsed CSV files to produce dynamic representations.
• Modularity: Each scraping script in auto-update is responsible for a particular source, making it easier to maintain or extend if new VTuber sources need to be integrated.