I think we need a central plugin website

swf · 2004-07-30 00:02:08

would anyone be interested if I created a textpattern website for plugins?

Anyone could get a Freelancer account and a few people could be set up as publishers. This way the site could be moderated.

I think there would be a few advanteaes to this because it could be categorized and less cluttered. People could leave comments if they had questions but it would be less cluttered than the plugin forum section.

I was just thinking about this when I saw Drew’s post. This post is very helpful but I think it would be even better if we devoted a site to plugins. Plus by using a last modified plugin we could list updated plugins making it easier for users to keep plugins current.

reid · 2004-07-30 00:33:10

I think, ultimately, having a central site for the plug-ins is the only way to go. We have the Central Plug-in List here, but like the site you linked (and this one), it does not list them all.

steph · 2004-07-30 01:42:26

Anybody got a wiki handy?

ramanan · 2004-07-30 01:57:17

Whenever Dean comes back, he should start one up at the textpattern domain. I think this is a good idea.

Andrew · 2004-07-30 01:57:28

Yeah – ultimately it’ll all need to be under one wiki roof so it’s not necessary to go to multiple sites in order to get the developer/faq/tutorial info you need.

jimb · 2004-07-30 23:46:10

If Dean doesn’t start an official one for whatever reason, I’d be interested in helping set one up.

JeffClark · 2004-07-31 17:43:03

I’ll help out too. This sounds like something that is definately needed with the growing popularity.

greenrift · 2004-07-31 22:21:48

A cool Instiki or MediaWiki (Instiki has Textile support, but MediaWiki is what runs Wikipedia) setup for Textpattern in general would be awesome. It would probably help Dean out the most, because we could begin to write and modify documentation and other stuff that might take a while for him to get to.

jason · 2004-08-01 00:18:28

We can start an official one. Right now, Dean is cleaning up the subversion repository for Txp and running through Trac.

marco · 2004-08-01 02:54:49

Take a look at this for an good example of a plugin repository and plugin documentation wiki.

ramanan · 2004-08-01 03:47:04

Jason, good to hear that. I think this is something that should be started by Dean. It ads an air of authority to the whole thing.

JeffClark · 2004-08-01 16:27:00

We should hold a design contest for it too. Little out of scope I know, but then it would look cool and be functional.

Remillard · 2004-08-01 16:33:15

As a note, the only reason the Chaosnet list isn’t updated was because of the Central Plugin Post in this forum. The issue was that authors wanted to be able to update their listing at any time.

If that post was made sticky it would go a LONG way to making it more usable.

However, I had some up with some proof of concept stuff for creating a table of TXP entries where it listed a bunch of the plugin stats (version, forum discussion, etc) and the permalink went to to the full article page. It was a good use of the additional entry fields in TXP.

Unfortunately, I have since axed that portion, once again due to the Centra Plugin Post which seemed like a better idea at the time.

I have gotten one e-mail in the last couple of weeks about someone else trying to do something like this as well. Whatever happens it needs to be organized, and have community buy-in. Otherwise it will never work the way it really ought to.

Just a few thoughts.

Regards,
Remillard

jason · 2004-08-01 20:53:36

There’s a plugin branch in the subversion repository.

Then I want categories, then plugin name or developer name.

Each plugin developer will have commit rights to their part of the repository, and people will be able to check the most current and also view the change history of the entire thing.

There will a wiki page for all plugins, wiki pages for each plugin (along with “description files in the repository”), wiki pages for how-to make a plugin, wiki pages for how to install a plugin …

And there will be http://lists.textpattern.com/mailman/listinfo/txp-plugins (or more correctly there is …).

The idea is not only to provide a resource for people who want to use the plugin but to also aid in their development and maintenance. The idea is not to just have a page or forum-thing listing everything, but to actually have a facility for both developing, tracking and distributing. Know what I’m saying?

jason · 2004-08-01 20:55:31

Making the Central Plugin List sticky is a good idea. I can’t seem to do it with only moderator rights.

Textpattern CMS

Textpattern CMS support forum

#1 2004-07-30 00:02:08

I think we need a central plugin website

#2 2004-07-30 00:33:10

Re: I think we need a central plugin website

#3 2004-07-30 01:42:26

Re: I think we need a central plugin website

#4 2004-07-30 01:57:17

Re: I think we need a central plugin website

#5 2004-07-30 01:57:28

Re: I think we need a central plugin website

#6 2004-07-30 23:46:10

Re: I think we need a central plugin website

#7 2004-07-31 17:43:03

Re: I think we need a central plugin website

#8 2004-07-31 22:21:48

Re: I think we need a central plugin website

#9 2004-08-01 00:18:28

Re: I think we need a central plugin website

#10 2004-08-01 02:54:49

Re: I think we need a central plugin website

#11 2004-08-01 03:47:04

Re: I think we need a central plugin website

#12 2004-08-01 16:27:00

Re: I think we need a central plugin website

#13 2004-08-01 16:33:15

Re: I think we need a central plugin website

#14 2004-08-01 20:53:36

Re: I think we need a central plugin website

#15 2004-08-01 20:55:31

Re: I think we need a central plugin website

Board footer