Textpattern VS Twig

>What's with the insistence of running it off of just MySQL?

I think the most honest answer here is that it's planned but not scheduled. There's an open issue to update Textpattern to PDO:

https://github.com/textpattern/textpattern/issues/345

…which will open up a whole new world of possibilities.

The Textpattern dev team & user base is pretty small, and the user base is largely patient, so Textpattern can sometimes fall into a trap of being 'good enough for now' and go for extended periods of time with few commits. What tends to happen is a release is scheduled, takes place, and then the plans for the next release are more forefront in our minds. The most recent release was nearly two years ago, which is a long time in Textpattern terms, but I'm confident we can get Textpattern 4.9 into the release pipeline this winter. More on that here:

https://github.com/textpattern/textpattern/issues/1879

https://github.com/textpattern/textpattern/releases.atom

Depends on the need...I have a quick LibreOffice HTML template in light or dark. I include metas for mobile use in the document properties. I also have a PHP controller that can easily modify these if I need it to be more dynamic.

Otherwise I use https://picocss.com/ for some things.

For publishing I either drop the HTML file in a folder with or without a controller, or start a new endpoint by creating a new section in TXP [1] and drop in whatever HTML and txp xml tags I need there.

1. https://textpattern.com/

Textile was the driving markup behind Textpattern (https://textpattern.com/), one of the better publishing/CMS tools out there on PHP. It had a nice object oriented approach that was less painful than Wordpress, and gave great flexibility to design aspects in ways that were easier to work with than Wordpress... but Wordpress won the popular marketshare, and TP was relegated to some diehards. Those diehards still pump out fixes and features, and it's worth a look at https://github.com/textpattern/textpattern/ if you want to see something a bit different.

>It bills itself as a "Content Management System", which I've always thought was an amorphous term. I suppose you could use it for a blog, wiki, or something similar.

Textpattern person here. It's readily usable as a blog, corporate site, etc. A wiki would be less straightforward, especially if you have multiple users doing stuff, since we don't have any revision history built into the core software.

Textpattern 4.0.0 (the first production version) was released in 2005, and we're currently working on Textpattern 4.8.8 for release in Q4 this year after PHP 8.1 lands at the end of November.

The 4.9 release series is also being worked on, we'll probably see the first cut from that branch in 2022.

Some links:

* https://github.com/textpattern/textpattern (core software)

* https://forum.textpattern.com/ (community forum)

* https://docs.textpattern.com (docs)

* https://textpattern.co/demo (demo landing page)

* https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=textpattern (CVEs on mitre.org)

Wordpress made a great impact on the net, and I was happy when clients liked its ease of use and relieved from the burden of making content changes. (Though, I've always felt that https://textpattern.com/ was more secure and better than Wordpress).

Consider Textpattern.

As you can see this template will add and configura the Pest test suite with a custom TestCase class that will start the application for your tests, making easy to test your application services (as used by Orkestra itself) and you will see a basic application, with a single route in the file config/routes.php that calls a Controller that simply render a Twig view.

Miscommunication in our projects is costly. A single misunderstood User Story can result in 3 days of wasted development time. Additionally, when developers do not use the same programming language, it may be necessary to construct APIs to facilitate communication, which can also be expensive. It is important to consider why front-end developers may be hesitant to work with Twig and how this can lead to a disconnect between front-end and back-end development.

The first step before generating the PDF is writing the HTML. To generate the HTML string, we will use the Twig template engine, which is the default one in Symfony. It comes with tons of features such as inheritance, blocks, filters, functions, and more.

In the phase of outputting data, you can use template engines like Twig or Blade or htmlspecialchars function.

Joomla dips into and out of php to get vars/logic into the frontend, which is fine, but it's nowhere near as tidy as a full-fledged templating engine like blade or twig which many other php CMSs offer out of the box.

FTLOG, use a template engine. Do NOT use PHP itself as a template engine (ironic given its origins). The best are probably Twig (https://twig.symfony.com/) (used by Symfony and a few others) and Latte (https://latte.nette.org/) (less widely used, but its syntax is *way* more learnable as it's more like PHP itself).

It took me a while to find a PHP project that was simple enough for me to set up on a single Docker image, but after some trial and error I found the Twig project.