@elkex that's not how things work for image transformations in twill. it's dynamic, where the cropped image is only generated when accessed. By using parameters on the image url, you can generate any transformation you need on the fly. See https://glide.thephpleague.com/

when you use image helpers on your twill models it returns the url with the crop parameters as query string, and you can add parameters to control width and so on

You can also use area17/twill-image for an automated frontend setup

hi there

is there a framework-agnostic version of twill?

Hi @aolko Twill is built with and for Laravel, so no. Do you mean for vanilla php, or for another php framework?

raw, vanilla php

rip 🪦

@aolko rip what?

Rip, the detailed answer to that question

Like, really, what prevents you from reimplementing that in pure php?

nothing is preventing me, but I don't need it, nor does our community here, not sure what your point is.

my point is average user wouldn't want to learn yet another dependency to use the cms

and yes, this approach is only right if you are writing something for yourself only

and since other people use it, instead of "hmm, i'll keep using this framework that __i like__ and __i find comfortable to work with__" it should be "hmm, i wonder, will it be better for the users to stick to this framework? Maybe it's too complicated for them, i'd rather port it over to the language itself"

I wouldn't qualify the Laravel community as myself only, still not sure what you're saying. Laravel is the most used PHP framework and there are plenty of users looking for an open source CMS toolkit built for and with Laravel.

you are not considering the stage when only you know about the script

not the proverbial "Laravel community"

besides, they __already__ have other, sometimes better CRUD admin panels that do the same and more

because, let's be honest, it's just a crud admin panel, no more, no less. To make it a cms - you have to restrict it more, you have to add the base content types and base fields, add supports for plugins, themes and provide more unnecessary tools

look at wordpress/joomla/drupal/dle

so rigid and bloated

those are for sure CMS, almost the same goes for MODx/b2e/grav/pimcore/processwire

those are CMFs, a bit more flexible sure, but still bloated

while, for example, sanity or directus are CRUD admin panels, even though they brand themselves as "data platforms" or "headless cms"

the only half-decent crud admin panel in vanilla php is cockpit, but it blows whatever is there in the pit so hard, that's not even funny

I agree with you about the solutions you mentioned being bloated and rigid. Twill isn't bloated or rigid, and it is much more than a CRUD admin panel. It's also not throwing a pricing page at you nor it is trying to become an opinionated turnkey CMS. You seem frustrated by other solutions and probably haven't actually tried Twill, so I'm still not sure what you're looking for. There are Laravel beginners enjoying Twill, as much as there are very experienced developers finding something they don't find elsewhere here. There are even people ending up learning Laravel through Twill, and I don't think that's a bad thing.

yea, i don't like frameworks at all, i'm a procedural "purist" like that. Imagine directus written in raw php and this is basically what i'm looking for.

except infinitely flexible, allowing for infinite content types and infinite fields

Hi, good day! How to show other fields like these?