Hello, To answer part of your question, changes you make are only affected by updates if you directly change the UNA code and the files you changed are replaced by those from the update. In the example you quote (categories), there is a way to do it with the internal tools of UNA, see here => https://github.com/unaio/una/wiki/Browseable-categories

So future updates won't change what you've done. Another example, if you need to modify CSS code, do so through the mix of the template you are using, rather than modifying the code of UNA. If you want deeper changes that you can't do with UNA's built-in tools, then it's best to ask a developer to do a custom module for you. This way you will not be affected by future updates.

Hi Baloo, 

As I wrote, we did everything as it is described in the githube ...
and as I thought from the description that it has been working for a long time ...
- I am also a programmer, among other my skills ...

But after the update, I don't know how it would behave if someone from UNA in the future will finish programming of features which are in description but are missing in reality.  ... 

Maybe when creating a new ALBUM, there would be two places to choose a category ... 

That's why we wanted an answer or opinion from developers .. for example ... of the ALBUMs module. 

No, I don't need them to do anything special for me .... 

But when someone buys something, where the properties are described, they should work ...
and not only for me but also for others who buy it ...

And if someone makes something with standard UNA tools, it is still useful and good to consult it beforehand ... and when the question is asked, the answer should come ... 

I can't imagine that anyone from our company would dare not answer to our customers ...
several times ...
Most likely, the customer would leave us.

And I would most likely have to fire that member of our team ... .. 

Greetings 

Juraj