Marketing site, privacy policy, and support hub for Yendor — a faithful reimplementation of the classic roguelike Rogue 5.4.4.
This repo is the game's public-facing site, not the game itself:
- Marketing landing page (
index.md) — hero, feature grid and a screenshot gallery, built with Jekyll and deployed viagithub-pageson GitHub Pages. - Privacy policy (
privacy.md) — the policy page required for the Mac App Store listing. - Screenshot gallery — six in-game screenshots (title, exploration, combat, inventory, campaigns, settings) served from
screenshots/. - SEO & sharing metadata —
jekyll-seo-tagandjekyll-sitemapplugins with per-pageimage/descriptionfront matter for search and social previews. - Support entry point — routes bug reports straight to the GitHub issue tracker.
- Automated dependency updates —
renovate.jsonkeeps the Jekyll/Ruby gems current.
This is a static Jekyll site, published automatically via GitHub Pages. To preview it locally:
bundle install
bundle exec jekyll serveThen open http://localhost:4000/YendorSupport/ (the site's baseurl in _config.yml is /YendorSupport). The live site is at https://atypical-consulting.github.io/YendorSupport/.
- Download: Mac App Store
- Website: https://atypical-consulting.github.io/YendorSupport/
- Privacy Policy: https://atypical-consulting.github.io/YendorSupport/privacy
- Support / Bug Reports: https://github.com/Atypical-Consulting/YendorSupport/issues
| Title Screen | Dungeon Exploration |
|---|---|
 |
 |
| Combat Gameplay | Inventory Management |
|---|---|
 |
 |
| Campaign Selection | Settings |
|---|---|
 |
 |
Yendor is built with Rust + Tauri 2 + React 19. It preserves every mechanic from the original 1980 Rogue while adding saga campaigns and pixel art visuals.
Developed by phmatray at Atypical Consulting.
Built with care by Atypical Consulting — opinionated, production-grade open source.
- Add a changelog / "what's new" page as saga campaigns ship
- Add a press kit page (logo, screenshots, boilerplate) for coverage requests
- Add a lightweight FAQ / troubleshooting section to cut down duplicate support issues
- Track App Store badge click-throughs to measure how the site converts
See the open issues for details.
- HTML
Contributions are welcome. Open an issue first to discuss any significant change.
- Fork the repository and create your branch (
git checkout -b feat/my-feature) - Commit your changes (
git commit -m 'feat: ...') - Push the branch and open a Pull Request
No license has been declared for this repository yet. Until one is added, default copyright applies — see choosealicense.com if you intend to open it up.