Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: The evolution of Textpattern
michaelkpate wrote #301236:
I seem to remember there was some sort of purge of posts that were deemed no longer relevant but I am not really sure.
Yeah, there was a movement of posts to an archive category. Were they later purged, were they moved to a hidden location, I don’t know.
mrdale wrote #301237:
We should use any tools available to make developing TXP easier and better.
There are two ways to answer that, because there are two audiences.
As a web developer, you like the speed of Textpattern, the tags, the ease of pages and forms, plugins, etc.
As an end user, you work in the admin, writing your content and editing your site.
So for a web developer, Textpattern is this site rendering machine. You feed it your layout, configure some settings, save the code, backup the database, deliver your product.
I’m an end user, but also the client.
Sell me on Textpattern beyond the benefits you as a web developer enjoy.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: The evolution of Textpattern
mrdale wrote #301237:
Interestingly enough, I was talking to a Microsoft developer this weekend, talking about how great all these new (and free) tools are and he lamented the fact that tey are not permitted to use any of them because of NIH. Glad we don’t have that problem.
I was momentarily confused why the National Institutes of Health would prevent Microsoft developers from using open-source development tools.
Offline
Re: The evolution of Textpattern
hcgtv wrote #301238:
Sell me on Textpattern beyond the benefits you as a web developer enjoy.
From a front-side site user or back-side site editor’s perspective, the benefits of using these tools would be abstracted one level.
SASS/Grunt just makes a project easier to manage and should result in tighter more consistent css. That is a secondary benefit to the above group. Because everything is in formulas and variables it actually should make variations on the stock admin theme WAY easier to customize.
I guess I have to ask, why do you care if someone uses SASS or not?
Offline
Re: The evolution of Textpattern
mrdale wrote #301241:
I guess I have to ask, why do you care if someone uses SASS or not?
I don’t mind at all, SASS is CSS on steroids, I’m still wrapping my head around CSS.
It’s not about what you use, or I use, it’s about what an end user can or would do with a zipped up Textpattern. It’s about improving that experience, because we all know that Textpattern rocks.
The core renders pages on my mobile of the TXP Tags site instantaneously.
It really is a hidden gem of a CMS.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: The evolution of Textpattern
hcgtv wrote #301242:
The core renders pages on my mobile of the TXP Tags site instantaneously.
That’s nice to hear, and 4.6 is ~50% faster than 4.5 on pages with many tags, especially if your db server caches queries. On TXP Tags you can gain another 30% if you make 4-col-portfolio
stylesheet cacheable (rvm_css
plugin?).
Last edited by etc (2016-09-09 08:29:44)
Online
Re: The evolution of Textpattern
etc wrote #301245:
That’s nice to hear, and 4.6 is ~50% faster than 4.5 on pages with many tags, especially if your db server caches queries. On TXP Tags you can gain another 30% if you make
4-col-portfolio
stylesheet cacheable (rvm_css
plugin?).
TXP Tags is running Bootstrap, so the CSS in the Textpattern database is very small, 27 lines.
I’m waiting on TXP 4.6, already got all my other web based software updated to their latest versions.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: The evolution of Textpattern
hcgtv wrote #301253:
TXP Tags is running Bootstrap, so the CSS in the Textpattern database is very small, 27 lines.
Its size doesn’t matter (much), it’s still processed by txp and not cached. From my place I get about 280ms waiting time for your main html and 135ms for css. And .png logo is not cached neither.
Online
Re: The evolution of Textpattern
etc wrote #301254:
Its size doesn’t matter (much), it’s still processed by txp and not cached. From my place I get about 280ms waiting time for your main html and 135ms for css.
Ok, I’m serving the CSS off the VPS’s SSD drive.
And .png logo is not cached neither.
Ok, you got me, how do you cache an image, wouldn’t that be the job of the browser?
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Online
Re: The evolution of Textpattern
etc wrote #301258:
The server must say to the browser “you can cache this” first. The common way is through .htaccess.
Ah, thanks for the link, I’ll adjust accordingly.
And thanks for your work on the parser for 4.6, will post benchmarks as soon as it’s released.
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline