Textpattern VS WHATWG HTML Standard

>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.

WHAT-WG HTML

There's a long-standing WHATWG feature request open for it here: https://github.com/whatwg/html/issues/2791

And several userland custom element implementation, like https://www.npmjs.com/package//html-include-element

One of the cool things that you can do with client-side includes and shadow DOM is render the included HTML into a shadow root that has s, so that the child content of the include element is slotted into a shell implemented by the included HTML.

This lets you do things like have the main page be the pre-page content and the included HTML be a heavily cached site-wide shell, and then another per-user include with personalized HTML - all cached appropriately.

The `allow` attribute on iframes is a relatively recent API addition from 2017

https://github.com/whatwg/html/pull/3287

I think there's a pretty strong argument at this point for this kind of replacing DOM with a response behavior being part of the platform.

I think the first step would be an element that lets you load external content into the page declaratively. There's a spec issue open for this: https://github.com/whatwg/html/issues/2791

And my custom element implementation of the idea: https://www.npmjs.com/package/html-include-element

Then HTML could support these elements being targets of links.

> Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/

I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.

I'd love to see something like HTMX get standardized, but I'm extremely pessimistic for HTMX's prospects for standardization in HTML.

In talking to a few standards folks about it, they've all said, "oh, yeah, you want declarative AJAX; people have tried and failed to get that standardized for years." Even just trying to get

to target a section of the page that isn't an has been argued about and hashed out for years.<p>Why is that? Well, for example, here's the form you have to fill out to start standardizing a front-end feature. <a href="https://github.com/whatwg/html/issues/new?assignees=&labels=addition%2Fproposal%2Cneeds+implementer+interest&projects=&template=1-new-feature.yml">https://github.com/whatwg/html/issues/new?assignees=&labels=...</a><p>It asks three main questions:<p>* What problem are you trying to solve?

The issue with a single global event handler is discussed here: https://github.com/WICG/close-watcher#a-single-event

If you use popover="", you get the kind of functionality you're discussing for free. For

, the discussion is in progress and reaching a conclusion: https://github.com/whatwg/html/issues/9373