Krita Store Assets Repository

[Emmet O'Neill]

Yeah. I missed that exchange in the IRC. We'll use the existing one for
sure!

I've deleted the repo I just made. Slightly a waste of time, but oh well, I
should have kept a closer eye on the chat.

I think we should rethink the folder structure, make it more compatible
> with what we want to have (remember about translations, think about assets
> for different purposes than just stores, like for example logo, or maybe
> the Yanone Kaffeesatz font).


Sure I guess. If we're too general/vague about what kinds of assets we're
thinking about it could lose scope quickly though.

 Also there can be source files for specific store assets, for example .kra
> files for Steam capsules. Where should they be located? I guess in assets/.
> Should assets/ have store subdirs too?


In my view (at least for the repo I just made/deleted) I was thinking that
we wouldn't try to be too cute about reusing store-specific assets between
stores.

At least in the case of Steam, there are very specific resolutions required
for each kind of asset (capsule, banner, etc.), as well as specific content
guidelines that must be followed (for example, which assets can contain the
logos and text, and so on.)
You can read more about that here:
https://partner.steamgames.com/doc/store/assets
I don't know for sure, but I would imagine all the other stores have
similarly specific requirements.

So In the repo I made, I was thinking that we would have a "raw assets"
folder that contains the source materials (like various splash screens, old
and new, in the highest reasonable quality that we can use for a lot of
store graphics, logos, fonts, a written description, high quality example
images, any videos, etc.) That could include KRAs if necessary, but most of
the time just image files would probably be enough.

We would then have various directories (like `stores/steam` and
`store/epic`, for example) that would contain the store-specific assets in
the required formats and resolutions. (KRA files optionally, if needed, but
I think the actual images are probably what's most important here.)

I was also going to include a "scripts" dir, which would contain scripts
for helping to automate the creation of cropped and scaled images as much
as possible. (Wolthera already has a pretty good script for this, iirc.)
In some cases scripts aren't going to cut it, because certain images might
take a bit more authorship and aesthetics to crop them nicely, but
auto-cropping is at least a good quick-and-dirty way to get some kind of
asset in place.

And what about translations? What if every store has the same description
> (which is a source file), so they also have the same translations?


I'll reserve judgement on this. The reason I didn't really account for
translation is that I feel like the least qualified person in our group to
talk about it.
Despite having a degree in Japanese, I think just about everybody in this
group speaks more languages than I do (and at a higher level too.)

Keep in mind that we might not be able to use the exact same description
across all stores, because they all probably have different length limits,
rules, requirements, etc.
However, we can certainly start with a "master description" as a base and
then edit the individual stores as needed. (Again, keeping the
store-specific assets in "stores/steam/words/description.md" or whatever.)
(I'm not sure what that might mean for translations... so if we can get
away with minimal editing we probably should.)

And then we should bring it out of the unmaintained category, move it to
> whatever the sysadmins consider most appropriate, change the folder
> structure, move the issues I made in the Krita main code repository there,
> and start putting in the store assets and Descriptions etc., and then do
> the trick to get KDE translations there.
> What do you think?
>

Sure, I guess so. I've now deleted my repo, so I guess we'll just start
working on that other one if we can.
Should we contact the sysadmins and make sure that we all have access to it
and that it's put into the "Packaging" category or whatever?

Emmet

On Wed, Jul 23, 2025 at 5:17 PM Tymon Dąbrowski <tamtamy.tymona at gmail.com>
wrote:

> Hi,
>
> So, as I mentioned on the IRC channel, we already have this repository
> here:
> https://invent.kde.org/unmaintained/krita-marketing/-/tree/master?ref_type=heads
> (thanks Wolthera for mentioning it!). I think it would make more sense to
> use that, since it already has some assets and it had basically the same
> purpose.
>
> I think we should rethink the folder structure, make it more compatible
> with what we want to have (remember about translations, think about assets
> for different purposes than just stores, like for example logo, or maybe
> the Yanone Kaffeesatz font).
> Also there can be source files for specific store assets, for example .kra
> files for Steam capsules. Where should they be located? I guess in assets/.
> Should assets/ have store subdirs too?
> And what about translations? What if every store has the same description
> (which is a source file), so they also have the same translations?
>
> And then we should bring it out of the unmaintained category, move it to
> whatever the sysadmins consider most appropriate, change the folder
> structure, move the issues I made in the Krita main code repository there,
> and start putting in the store assets and Descriptions etc., and then do
> the trick to get KDE translations there.
> What do you think?
>
> Note that the issue is currently tracked here:
> https://invent.kde.org/graphics/krita/-/issues/1 and it should be later
> moved to that new repository (whether the old one moved to the maintained
> category, or the fresh new one).
>
> Regards,
> Tiar
>
>
>
>
> czw., 24 lip 2025 o 00:46 Emmet O'Neill <emmetoneill.pdx at gmail.com>
> napisał(a):
>
>> Hi all.
>>
>> Based on our quick discussion at this week's meeting I've gone ahead and
>> put together a small repository for managing Krita's various store assets
>> across various platforms.
>>
>> https://invent.kde.org/emmetoneill/krita-stores#
>>
>> I don't know enough about all of the store-specific assets requirements
>> to know for sure whether this will be adequate,
>> but the basic idea is that we keep all of our raw, uncropped and high
>> quality [text, image and video] assets in the `assets/` dir,
>> utility scripts in the `scripts/` dir, and all of the store-specific
>> assets in sub-dirs within the `stores/` tree.
>>
>> Right now this repo is just a skeleton populated with placeholder files
>> to show what I think the structure should be.
>> So the first order of business in wrangling everything should probably be
>> to populate the `assets/` directory with as many high quality assets as
>> possible.
>>
>> Also, this repo is currently under my username, but I think we could
>> probably migrate this over to the "Packaging" project on the KDE gitlab.
>> (I either don't have the permissions to do that myself, or just don't
>> know how!)
>>
>> Emmet
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20250723/69c8d340/attachment.htm>