Open Cheeseness opened 10 years ago
Good idea, however, we should soon begin using databases instead, then we could just foreach it instead of creating all that manual content all the time.
Yup +1
Just to play devil's advocate here...
We could just have some structured easily generatable files (e.g. JSON) dumped in a directory somewhere.
But yes, a database works too, and would probably be a whole lot easier in regards to possible filtering (by geographical location, for example), if we ever decide/need to implement that sort of thing.
@meklu I thought about that as well (or reuse code from the cast notes..), but we should save some work if we just went directly to SQL instead of JSON -> SQL.. \o/
Only downside of putting it in a database is that it's harder for contributors to help out with. When we get Steam login stuff online, we can potentially expose edit access to guild admins?
Yup, exposing it to promoted authed‐in users seems like a smarter goal for the feature.
Wonder if having guild pages support steam event listings, and if that encourages us to have new groups for those. Would be nice to have an ‘invite me to guild’ feature, not sure how much is in the webapi to let us automate some of that though.
It feels like we'd have very disparate levels of support for those sorts of features. I know GOI Online doesn't expose anything for clans outside of the game :(
As soon as they let us schedule in-game events for GOI Online, I'm going to lean towards not scheduling Steam events for it and use that instead to leave Steam events for bigger scale stuff.
Other things this needs:
Thinking about how we can do this in chunks:
It'd be nice to have a page listing our active game specific guilds/clans (Dota 2, Guns of Icarus Online, and maybe some others?).
For each one, I'd imagine that we'd want to list:
Such a page would live under the projects page until we look at restructing our menus.
Anybody got any thoughts/alternative perspectives?