tinacms VS Textpattern

> Why is are all static site generators (that I am aware of) are CLI? What prevent simplistic drag and drop GUI/WYSIWYG that generates those clean static files?

Check:

- Tina CMS: https://tina.io/

- Primo CMS: https://primocms.org/

Anyway, you seem to be holding the wrong end of the stick. Static generation is the easy part, what you're looking for is a subset that falls under the CMS umbrella, just search for `CMS+SSG` you'll find a diverse set of solutions.

You can also setup any generic Headless CMS to trigger generation for a static site. Why would someone build a full fledged CMS and limit it to a niche market inside a niche?

Tina CMS, formerly Forestry, is one of the best open source Git-based CMSs in terms of the provided feature set. It covers the basics, such as:

Tina CMS: The Editing Renegade of React

Try tina cms https://tina.io

Currently testing it with Docusaurus for our documentation site.

The next step in building this demo blog application is to set up TinaCMS, an open source headless CMS that supports the Markdown format.

Solutions like CloudCanon or TinaCMS use this approach.

With TinaCMS, all your content changes are committed directly to Git. This enables your team to create a variety of workflows for reviewing and merging content updates. By leaning on GitHub, you can integrate CI/CD into your content workflow.

Check out this license for example: https://github.com/tinacms/tinacms/blob/main/LICENSE

It's an Apache 2.0 license, but with adendums.

Would it be reasonable to say that I could fork their repo for own purposes, and argue in court that I was only familar with Apache 2.0, and not their modified terms?

It's from before PDO was a thing, I believe. They have their own "abstraction" on top of mysqli - I'm not sure about the return values, but might be possible to switch in PDO?

https://github.com/textpattern/textpattern/blob/ef91076b7199...

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