Pete Cooper

My 2c: wait for 4.9 for deprecation, more eyeballs will see it in the release notes.

If it's straightforward to do, I really like @Bloke's approach in https://github.com/textpattern/textpattern/issues/1726#issuecomment-993003830 Bearing in mind there will be a longer gap between releases if we're going to 4.9, it makes...

So, presumably, if we can spin out a doc for `items_count`, and make mention in `HISTORY.txt`, this is all that's needed for 4.8.8, right?

I'm gonna update the title to this shortly, since we're at a point that it's ready for 4.8.8 (via https://github.com/textpattern/textpattern/commit/0f659c149495597eb3b8fd5eb5e0142fe16d268a - thanks @bloatware). We can do the docs tweaks after...

@philwareham - like this a lot. 1. This looks great. I would perhaps err towards `default-content` rather than `initial-content` but I'm verging on nitpicking. Perhaps some sort of JSON package...

>Question: how do you plan to handle inline textile Presumably standard HTML would be a fallback if Textile can't be cajoled into accepting multibyte or non-Latin character sets fully.

@philwareham - ToC for the language, whether it's formatted in Textile, Markdown, HTML or other, whether the article is translated or not, generated checksum for the stuff that's going to...

>If Textile can't be fixed to allow this, then maybe we should be careful to make sure the welcome article overall doesn't contain and breaking Textile syntax, or tailor each...

>can you give an example of what the JSON file would contain? Actually, there's nothing I can think of that has to live outside the various XML files, so bin...

Since we're making this article and the default fixtures and fittings more global-ish, I am trying to think objectively and fairly about _all_ languages, and lower/remove any hurdles that translators...