Since themes are theoretically less complex to maintain than plugins there is a case for doing Textpattern-only management.
For example, themes should only need a minimum Textpattern compatibility version as it would be assumed that we won't be bringing website-breaking changes in future Textpattern releases (I'd hope not alway!). There is also a single download point for each theme (a zip file bundle of the files).
However, I do quite like the team-based maintainability of a curated list repo - as I would not really be keen in personally maintaining the content of the site going forward (apart from maybe creating initial articles for themes when a new one is needed).
@Bloke @petecooper @jools-r I'm gradually building out the themes site at https://themes.textpattern.com as I get spare moments.
It's come to the point in construction where we need to decide how we handle the day-to-day content off that site. i.e. do we go with a curated theme repo list similar to https://github.com/textpattern/textpattern-curated-plugins-list as previously discussed and implemented for the plugins site. Or do we handle updates solely within the Textpattern admin panels.
Since themes are theoretically less complex to maintain than plugins there is a case for doing Textpattern-only management.
For example, themes should only need a minimum Textpattern compatibility version as it would be assumed that we won't be bringing website-breaking changes in future Textpattern releases (I'd hope not alway!). There is also a single download point for each theme (a zip file bundle of the files).
However, I do quite like the team-based maintainability of a curated list repo - as I would not really be keen in personally maintaining the content of the site going forward (apart from maybe creating initial articles for themes when a new one is needed).
Thoughts?