Textpattern CMS support forum
- Plugin Author
- From: Porvoo, Finland
- Registered: 2008-12-03
- Posts: 203
Thanks for showing interest towards that project, colak. :-]
That site is actually in it’s 2nd major version. In the first version I had made a plugin management system where authors could publish, edit and delete their plugins by sending special commands via email messages to a
textpattern.info@ inbox. Before actually using it publicly I got worried it might (probably: would) get spammed, so that’s why the site now is how it is.
Coding the current version I wanted to extract useful information from the plugin files themselves, but they’re not standardized, so… So it’s more frustrating than fun to maintain.
We’re revamping the plugin repo so if you’d like to coordinate with us or share anything, just drop us a line.
- Core designer
- From: Haslemere, Surrey, UK
- Registered: 2009-06-11
- Posts: 3,337
Let’s try and get the new plugin site up and running in quarter 1 2020. Not sure my current route of solely relying on github api is going to be satisfactory. Too many different workflows people use there (some people tag release, some people never tag, etc). Maybe a combination of manual and automated is the way to go (although I did want to automate the plugin site as much as possible).
Still thinking about it. Apart from that the structure of plugins site is quite far along with build and structure.
philwareham wrote #320719:
Maybe a combination of manual and automated is the way to go (although I did want to automate the plugin site as much as possible).
Totally agree but that sounds wise. Perhaps either a semi-automated means of discovering new plugins / new releases and bringing in data from GitHub etc. for final manual curation (e.g. easing the transfer of information) or alternatively an interim collection repo on GitHub with an agreed format that curators, plugin authors and outside contributors can create PRs for. Just throwing out some ideas.
TXP Builders – finely-crafted code, design and txp