Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #338222:
I’m seriously tempted to take the (now defunct?) slir package, fork/update it for modern php versions and just drop it in our /vendors directory.
It shouldn’t take much if you understand php ;-)
I managed by using a work-around of the single function that causes SLIR to error under php8; include the image’s ratio in the calling SLIR string slir/w640-c123:456/path-to-image and no more errors.
I currently exclude .webp and .svg from using SLIR in my <txp::figure /> output (by querying the extension column!). Hopefully appending .webp into txp-slir is feasible/straight forward.
Offline
Re: RFC: Textpattern 5 ideas & feature requests
I’ve published my in-progress alladmin2 admin theme as a html demo at dev.all-sorts.biz.
.
After too many Nova-regex search and replaces on my html and getting this far, I read about CodeKit’s .kit feature.
Offline
Re: RFC: Textpattern 5 ideas & feature requests
giz wrote #338224:
I’ve published my in-progress alladmin2 admin theme as a html demo at dev.all-sorts.biz.
That. Is. Radical. (but I love the experimental reduction!)
TXP Builders – finely-crafted code, design and txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #338222:
The only sticking point is how to migrate people’s existing arsenal of images to the new one. That’s potentially a bit of a challenge. Ideas welcome.
I’m a profound profane in everything image-related, but if it is a right thing to do, bwc should not be an obstacle. That’s what major updates are for.
Online
Re: RFC: Textpattern 5 ideas & feature requests
giz wrote #338224:
I’ve published my in-progress alladmin2 admin theme as a html demo at dev.all-sorts.biz.
It would be great to find a minimal markup/styling that makes txp back-end usable and still allows for a full customization. Please don’t be hold by the current layout if something more flexible is possible.
IIRC, we even discussed a possibility to fully compose an admin layout using txp tags, just like on the public side.
Online
Re: RFC: Textpattern 5 ideas & feature requests
etc wrote #338229:
IIRC, we even discussed a possibility to fully compose an admin layout using txp tags, just like on the public side.
Yes! *dreams*
I’m a profound profane in everything image-related, but if it is a right thing to do, bwc should not be an obstacle. That’s what major updates are for.
To a degree, yes. But I have at least one client running a site that has 6000+ images, and climbing. They’re not going to upgrade if it means uploading them all again.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #338230:
Yes! dreams
Some plugins allow already the public side editing, so this is something to rethink of. A nice headless API and here we go, at least for some parts.
But I have at least one client running a site that has 6000+ images, and climbing. They’re not going to upgrade if it means uploading them all again.
Probably, a script could do it for them? Well, that’s just to say something :-)
Online
Re: RFC: Textpattern 5 ideas & feature requests
etc wrote #338229:
It would be great to find a minimal markup/styling that makes txp back-end usable and still allows for a full customization. Please don’t be hold by the current layout if something more flexible is possible.
We could leave the current structure and class names exactly as is, and make do with high specificity css selectors when targeting some page widgets. This has a compounding effect on child elements though; even more specific selectors will be required (including !important gasp!).
Adding a couple of new classes to select nodes will improve specificity considerably — leaner css.
I’ll continue chipping away at my node diagram. As a break from the diagram tedium, I’ll start on the basics: css variables, colours and styling of plain/unclassed html elements. Layout niceties can wait until our foundation is solid :).
(Should we create a new thread for this meme?)
Offline
Re: RFC: Textpattern 5 ideas & feature requests
giz wrote #338232:
I’ll continue chipping away at my node diagram. As a break from the diagram tedium, I’ll start on the basics: css variables, colours and styling of plain/unclassed html elements. Layout niceties can wait until our foundation is solid :).
If it’s any help, I made a start at this as a basis for making another admin theme:
https://github.com/jools-r/hive-revo
Unlike your approach, it doesn’t start from scratch but is more of a conversion of Hive v4.9 to use css variables for font sizes and layout parameters as well as logical properties. I also switched from 13pt to 16pt as the base unit. I was tinkering for my own purposes and didn’t use Phil’s build setup or the flat hive variant. Instead it uses parceljs so that you can use state-of-the-art CSS and have it transpiled back for old browsers (parcel uses lightningccs from the same author for this).
I had hoped that by using logical properties (block & inline rather than top, left, bottom, right) it would be possible to dispense with a lot of the LTR / RTL code. However, as yet the browsersl.ist settings seem to insist of transpiling back to language-specific settings rather than leaving the logical properties CSS as is, so the compiled CSS is not markedly smaller (see also this discussion). An update of parceljs with many fixes came out a couple of days ago, which I’ve yet to try.
As such, it’s a work in progress and not directly usable as a theme. I got ahead of myself with the more opinionated theme I was developing and haven’t backported later solutions into this version. But maybe it is of some help all the same.
(Should we create a new thread for this meme?)
Yes, I think so.
TXP Builders – finely-crafted code, design and txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
giz wrote #338232:
We could leave the current structure and class names exactly as is…
We won’t have time to change it in 4.9 anyway, but for 5.0, is wrapping content partials in div.txp-layout-4col-3span etc really necessary? Might something like grid-area be more flexible? Currently, content and markup are mixed a bit too much in core, imo.
Adding a couple of new classes to select nodes will improve specificity considerably — leaner css.
Suggestions welcome.
Online
Re: RFC: Textpattern 5 ideas & feature requests
Discussion about Textpattern 5 admin UI css continues.
Offline
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #338213:
Here’s a proposed directory structure moving forward. Not sure how achievable it is, but that’s more closely aligned with the multi-site layout and has lots of nice little wins about it.
That’s absolutely ideal. Love it.
I don’t know the reasoning for being worried that naming directories TXP will cause Google issues, but may I suggest TEXP or TEXT instead. Much nicer than CMS.
Offline