How liikane/tallinn works
Project type and purpose
• This repository is a small documentation/static site project (likely a GitHub Pages site or a docs site) containing a short operational guide ("WP uudiste lisamise juhend" — guide for adding news to a WordPress intranet). Key intent: host simple documentation/checklists for editors and optionally automate issue/project management via GitHub Actions.
File-structure analysis (what the tree tells us)
• .github/workflows/add-issue-to-project.yml — CI/CD automation using GitHub Actions; likely responds to issues/PRs or pushes to update a GitHub Project.
• CNAME — custom domain mapped to GitHub Pages (site is served under a custom hostname).
• README.md — human-facing guide/checklist (the actual content).
• SUMMARY.md — convention used by static-doc tools (GitBook, mdBook, or similar) to build navigation; indicates a docs site structure.
• index.html — root page for the static site.
• kana.txt, test.txt, tallinn — additional content files (sample pages / assets).
Overall pattern: content files + build/hosting metadata + a workflow. No server-side code, no database in repo.
Additional insights from README
• README is a step-by-step checklist for editors to add a news post to the WP intranet.
• Project is operational-documentation, not an application: actors are people (editors), target is an external WordPress system.
• The workflow file suggests some repository-side automation (project board management) that supplements the human process.