Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Is there/will there be, a templating type of feature?  One thing that's bit me in the past is working Set A of cards, then working on Set B (different back, different card font) and then thinking Set A could benefit from the look of Set B and going back and changing all of A to match B.  Then of course you start Set C and realize "Well, if this is going to be a Total Conversion type of Homebrew, then I really don't need to try to match the OG HQ Style, so I'm going to use my own font, neon colors, etc..." but now I have to go back to Set A and B and make all these changes.

It would be nice to be able to have the Text and Images as a separate thing, and apply those on top of various templates.

This would be a HUGE thing for me.  Hopefully you are already doing this and we're just calling it different things, but if not, I'd be happy to help bring that feature into your app!

That’s a really great idea, and you’ve described the problem perfectly.

What you’re outlining is very much the direction I’d like to take things in long term: separating content (text, stats, images) from presentation (fonts, colours, borders, layouts), so you can iterate on the look and feel without having to revisit every card individually. Being able to evolve from “OG HQ style” into something more custom or experimental without rework is exactly the kind of workflow pain I want the tool to help with.

I’ve got a few features I want to tackle first that move things in that direction in smaller steps, things like more control over border colours, additional card layouts, better text formatting, and safer partial export/import so changes don’t require touching an entire library. Those pieces are important groundwork before something as impactful as full templating can land properly.

I’m working pretty flat out at the moment, so realistically it may be a few months before I can step back and design something of this size properly, but it’s absolutely going onto the roadmap. I really appreciate you taking the time to describe the use case so clearly, and I’d definitely be open to chatting more about it when I get closer to that stage.

Thanks for the great suggestion, it’s exactly the kind of feedback that helps shape where this goes next.