Open-source Concrete CMS packages for gaming communities: events and LAN signups, teams, logins with Steam, Discord and Battle.net, a members’ wiki, a bar kiosk and a shop that knows store credit. Built for the Turicane LAN, running in production.
Open source · Concrete CMS 9
Each package works on its own and plays well with the others. Pick what your community needs.
In action
Screenshots from the live site of the Turicane Game Club. Member names are blurred.
The story
How FragStack came to be, written by the AI that built it with TuBorg.
It started as one package for event signups. Ten days later the Turicane Game Club had a new website: seat maps, a bar kiosk that knows your badge, a members’ wiki, a terminal with bad manners, a server move, a big cleanup and two side projects.
Claude wrote down how it went: what was built, what TuBorg cut because it went too far, the mistakes along the way and why every piece is a package of its own. With screenshots and the numbers from the Git history, and how 30 people signed up for the LAN in a terminal.
Read “Zehn Tage, siebzehn Pakete” →
In German, on the Turicane blog
Why FragStack
Every package started as a problem at our own LAN party and has to survive it every year.
Runs turicane.ch: signup, seats, tickets, checkout and the kiosk at the LAN, with real people and real money.
Blocks, dashboard pages, permissions, tasks and translations the Concrete way. No framework on top of the CMS.
Install only what you need. The packages work alone and connect where it helps, e.g. events with teams and the shop.
Honorable mentions
FragStack is a thin layer on top of other people’s open-source work. Thank you to everyone who builds and maintains it.
The CMS every FragStack package is built for: pages, blocks, permissions, the dashboard, tasks and the console. Created by Andrew Embler and Franz Maruna, developed by PortlandLabs and its community, open source under the MIT licence.
Andrew Embler · Michele Locati · Korvin Szanto · Mike Lay · Takuro Hishikawa · Michael Krasnow · Joe Meyer · Karl Dilkington · Derek Cameron · Remo Laubacher
The shop behind our tickets, the bar kiosk and store credit. Four FragStack packages extend it. Maintained for years by Ryan Hewitt, together with a group of Concrete developers.
Ryan Hewitt · Michele Locati · Nour Akalay · JeRoNZ · evgk · difi68 · edbeeny · danklassen
Forum answers, add-ons, translations, docs and the Migration Tool that moved our content to the new site. Thanks to everyone who keeps Concrete CMS going, and to the people we learned the most from.
Michele Locati · Takuro Hishikawa · Remo Laubacher · Nour Akalay · Ryan Hewitt · Karl Dilkington · Derek Cameron · Joe Meyer · ignasigarcia · biplobice
Components under Concrete; CLI Mode’s terminal runs on Symfony Console.
The ORM behind every entity in our packages.
Icons in Concrete’s dashboard and our blocks. Created by Dave Gandy, made by Fonticons.
Names from the projects’ GitHub contributor lists, most commits first; thousands more people have contributed. The logos are the projects’ own marks, shown to say thanks.
Get started
The packages are Composer packages from their GitHub repositories. Add the repository, require the package, install it in Concrete.
# in your Concrete project (composer-based install)
composer config repositories.event_manager vcs https://github.com/haeflimi/concretecms-community_event_manager
composer require haeflimi/community_event_manager:dev-master
# then install the package
./public/concrete/bin/concrete c5:package:install community_event_managerWithout Composer: download the repository as ZIP, unpack it to packages/<handle> and install it under Dashboard › Extend Concrete. Questions or ideas? Open an issue on GitHub. Who built this? Meet TuBorg and Claude.