v_kyr

Wordpress/Mysql is probably the most used combination for such website backends and nowadays offered by most hosting services. If you have made good experiences with that one you named, use that then. There are thousends of wordpress templates free and commercial, look through some plain simplified/reduced to show the basics ones and choose one your daughter likes. Usually here those templates which deal with photography, art etc. are good candidate templates to showcase things. Like ... - Clean photography - Photography themes - etc.

Another interesting new font, especially here for developers (coders), so those who have to write/read a lot source code, is the JetBrains Mono typeface. - See: JetBrains Mono typeface

Somehow have missed and not seen this thread before. That can also be used (taken over from APh) to AD and would then there preserve text and shapes as vectors. Related to other initially in this thread shown distortion methods, the free form distortion works mostly everywhere I've seen those implemented, on enhanced curves, meaning here on a vector node base, instead of shapes. Envelope distortions in contrast here via predefined shape/form presets (hence the name envelope).

A 30cm horizontal ruler on an A4 landscape sized page ... Ruler_30cm_horiz.afdesign

It's always a difference if you can start an architecture design from scratch considering these things, or instead have to care, update and restructure a long time existing monolith. So no surprises here. The way they deal with vector transformations is mostly algorithmic implementation depending, they already do a bunch of vector plane oriented transformations (translate, rotate, skew, mirror, reflect ... etc.) via their below graphics/rendering engine, which also supports several individual or selected node transformations etc. And since they share their engine, file formats, layers etc. among their apps that's no theme to add this. I don't judge the company, that's more what others did here with their in contrast to Adobe etc. comparisons, statements and the like. I also don't excuse them for certain decisions they make or don't made, that's all (or lies in...) their responsibility and handling not mine. Further I also really don't care if Serif is a big or small company etc., that's overall irrelevant for me to this software tread theme here, were I agree with others that it would be time and fine to add a specific missing feature/functionality.

Well there is always room for improvements in this regard, meaning possibly adding over time the one or other software functionality which might be useful for more flexible AD brushes organisation purposes. And yes, certain things are actually still clunky.

BTW and since I think it's probably related to the organization theme here, what I didn't saw (or maybe have overlooked) is a sort of search feature. - Meaning suppose you have a category, or a bunch of categories, with always a lot of brushes inside. Let's also assume you named those in some intelligent searchable manner, how do you search among 1000 brushes in order to find and use that specific one you are interested in (?).

That's what I implied, other times, other hardware/software capabilities and their restrictions, other software development techniques etc. Nowadays we can do all those things faster on a smartphone than years ago. Some actual smartphones have more processor and GPU power than some desktop hardware still laying around here. Nowadays common people can quite easily build the one or other software or certain tools (be it for desktop computers, smarthphones etc.), there is a huge pool of working things they can just reuse, enhance or modify in order to overcome with the possible envolved complexity. Add to that the evolution of what operating systems and third parties do offer today and give you into your hands for reusage (APIs, frameworks, libs ... and so on), all the stuff that wasn't available in the past to such an extent. I'm myself a software architect and developer, although working in/for completely other IT domains, but in timeline I went more or less through most related dev based infrastructures till today. So I believe I know one or two things about software development and software in paticular. Further I wouldn't have been skeptical about some comments from people here, if I wouldn't be sure if what they tell is not relevant to what is the main theme here. In order to be more concrete here, in this case for a "vector based warp, distort function" it doesn't matter that much if Serif might have only 50 or 150 developers here, it's more a matter of putting it on a priority of their agenda and then adding it. I say this especially given the fact that they already had this functionality in their previous software. This would allow them to adapt and reuse their algorithms, which shouldn't be that big deal. - Everything else above that other people bring here in as arguments, like comparisons of Adobe's employee size vs that of Serif etc. is pretty much more like an unnecessary defense of something end users usually either way have no internal knowledge of and have no idea about. Allowed is not the overall right wording or sense here. so more that the common market (potential buyers, customers) and software competition might to some degree dictate what base functionality would be expected (ultimately then, as always, the customers and their complaints). Sure if there is nothing comparable you can't compare, though not always what you believe is best is also what your customers believe, they might have a different view or opinion on it than you. They might have other usage scenarios than you thought and thus maybe aren't satisfied with what you offered so far and thought to be best etc. They already reuse a bunch of APIs for, RAW/lense/Exif conversion, several file format read/write support libs, tons of Apple and MS and other third party (freeware and commercial) libs ... etc. Without those you won't go nowhere today, since you would have to reinvent the wheel again and again and need 10 years more for development. - Related to the small team, other software teams in this domain (most of those newcomer software) are even smaller, some are even a single fighting developer to whome then Serif would be a giant in comparison. Also what most of you don't seem to take into account here, Serif is no newcomer, they are nearly 33 years in that business and already have done a bunch of such software before, which also already had many of the features (and thus the algorithms behind those, vector distortions in this specific thread case) sometimes demanded here. Also there have been many things already taken over from those former legacy products, it's not always the case for everything that they had to start at point zero, one have to differentiate among those.

I believe it's the same way as you would organize your styles or assets, namely you have to make certain categories, name them to what makes sense for you and then import into those categories. - See what the brush panel offers in this regard ... Brush panel

See under the forums resources section: Fuji Film Simulations 8 LUTs Reusing filmstrips as photo borders (film template frames etc.) etc.

Doc model, how that? - All here is requested is based on some specific algorithmic for Shape/Node distortions, aka ... ... that's all. They had such vector based node support before in their former software, as can be seen above. - Further it's similar like applying such node manipulations here, just other algorithmic coordinate transformations for the nodes then.

Adobe Illustrator started 1987 - 33 years ago QuarkXPress started 1987 - 33 years ago CorelDraw started 1989 - 31 years ago So another bad example and therefore an Apple & Oranges comparisons, since there were pretty much other times those days 33 years ago, so limited hardware/software (CPU, GPU, HDDs etc.), much worser development tools, available frameworks and APIs for coding etc. In other words, other times other hardware/software capabilities. - Development tools speed and overall capabilities, techniques changed a lot over 33 years hear too. Today none of them (Ai, CD, QXP) would miss those from start up, nowadays they couldn't afford not to have these things, as these are today pretty usual/common standards and most of that is even supported by every OS graphic APIs nowadays. - The only thing I accept here is, that the development team is probably small, but that was what the others were at those former times too.

The roaring silence means usually nope.

Not sure there is such an Affinity guide or tutorial dealing exactly with that materia. - But you can always ask and search via Google after such theme topics, or at least after individual steps which have been taken in that PS guide. So here via Google ... "affinity photo" "star reduction" affinity photo star reduction (Youtube search) affinity photo select color range affinity photo selection feathering affinity photo minimum maximum filters etc.

Well usually not my domain (Astrophotography), but maybe you can recreate and follow this PS way here. - There should be equal or similar behaving tools & filters in APh (see also related Aph min/max filter).