<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ranting on Wordpress Plugin Development</title>
	<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/</link>
	<description>mental diuretic</description>
	<pubDate>Fri, 25 Jul 2008 12:42:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Anne Helmond &#187; Review: Justin Shattuck&#8217;s site</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-5903</link>
		<pubDate>Thu, 08 Mar 2007 08:47:54 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-5903</guid>
					<description>[...] Posted by anne on 08 Mar 2007 at 10:47 am &#124; Tagged as: usability, wordpress themes  I first came into &#8220;contact&#8221; with Justin Shattuck&#8217;s when I commented on his post about Wordpress Plugin Development. He seemed to be asking the same questions as I was regarding the configuring and using of WordPress plugins. I am planning on dealing with some of these issues in my MA thesis Blog Software and the Act of Blogging. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Posted by anne on 08 Mar 2007 at 10:47 am | Tagged as: usability, wordpress themes  I first came into &#8220;contact&#8221; with Justin Shattuck&#8217;s when I commented on his post about Wordpress Plugin Development. He seemed to be asking the same questions as I was regarding the configuring and using of WordPress plugins. I am planning on dealing with some of these issues in my MA thesis Blog Software and the Act of Blogging. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Justin</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-3047</link>
		<pubDate>Thu, 11 Jan 2007 15:07:33 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-3047</guid>
					<description>@ttancm:  That is a good point, I feel there should be a standard as well.  Perhaps this is something that could be pushed for easily.  If plugin developers all worked together, I think it could be done rather quickly too.</description>
		<content:encoded><![CDATA[<p>@ttancm:  That is a good point, I feel there should be a standard as well.  Perhaps this is something that could be pushed for easily.  If plugin developers all worked together, I think it could be done rather quickly too.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ttancm</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-3044</link>
		<pubDate>Thu, 11 Jan 2007 10:19:07 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-3044</guid>
					<description>One thing I wish they would decide on plugins as a whole is where the plugin admin interface is going to be. I'm tired of installing and activating a plugin and then having to hunt through the entire WordPress admin menu to find if the plugin menu is under plugins, options, dashboard, etc.</description>
		<content:encoded><![CDATA[<p>One thing I wish they would decide on plugins as a whole is where the plugin admin interface is going to be. I&#8217;m tired of installing and activating a plugin and then having to hunt through the entire WordPress admin menu to find if the plugin menu is under plugins, options, dashboard, etc.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Weasel</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-2299</link>
		<pubDate>Sat, 16 Dec 2006 00:43:47 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-2299</guid>
					<description>I like plugins that just up and work, but during my development I've found that it is technically impossible to actually create certain plugins without editing some wordpress source first. The majority of the plugins you are referring to are probably just lazily coded, but I had to throw that out there.

That said, time to answer your question. I think a plugin should come with the most common and most popular settings pre-set... So that you can just turn it on and it'll work for most folk. There should be a configuration screen that gives VERY WELL DOCUMENTED options that clearly spell out what you can change, why you might want to, and how. This gives the power user ultimate control, gives a newbie a chance to learn, and gives the clueless nothing to worry about.</description>
		<content:encoded><![CDATA[<p>I like plugins that just up and work, but during my development I&#8217;ve found that it is technically impossible to actually create certain plugins without editing some wordpress source first. The majority of the plugins you are referring to are probably just lazily coded, but I had to throw that out there.</p>
<p>That said, time to answer your question. I think a plugin should come with the most common and most popular settings pre-set&#8230; So that you can just turn it on and it&#8217;ll work for most folk. There should be a configuration screen that gives VERY WELL DOCUMENTED options that clearly spell out what you can change, why you might want to, and how. This gives the power user ultimate control, gives a newbie a chance to learn, and gives the clueless nothing to worry about.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anne Helmond</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-2167</link>
		<pubDate>Wed, 13 Dec 2006 13:13:06 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-2167</guid>
					<description>Dear Justin,

Thank you for your comments. My thesis should be ready and available for download somewhere during the summer of 2007 (if all goes well and according to planning of course  ;) ) Right now I would consider plug ins an answer to the constraints Wordpress imposes on its users. Unfortunately only programmers have the ability to work around these constraints because they have the technical wizz to actually build a custom solution to the posed constraint/problem. I think it would be also useful and interesting too look at the community that is creating and writing these plug ins. Also the larger trend of widgets is worth looking at. The "Widgetize Anything" Wordpress plug in is a great example of this. Oi oi. It is time to get my scope narrowed down :)</description>
		<content:encoded><![CDATA[<p>Dear Justin,</p>
<p>Thank you for your comments. My thesis should be ready and available for download somewhere during the summer of 2007 (if all goes well and according to planning of course  ;) ) Right now I would consider plug ins an answer to the constraints Wordpress imposes on its users. Unfortunately only programmers have the ability to work around these constraints because they have the technical wizz to actually build a custom solution to the posed constraint/problem. I think it would be also useful and interesting too look at the community that is creating and writing these plug ins. Also the larger trend of widgets is worth looking at. The &#8220;Widgetize Anything&#8221; Wordpress plug in is a great example of this. Oi oi. It is time to get my scope narrowed down :)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anne Helmond</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1808</link>
		<pubDate>Fri, 01 Dec 2006 10:40:04 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1808</guid>
					<description>I have been using widgets and plugins for a little while now and I love them. 
I have been experiencing some problems with configuring some though. I am currently documenting my problems for my thesis which will deal with software constraints in Wordpress http://www.annehelmond.nl/tag/wordpress

I don't mind a wide array of options as long as the documentation is good. I am semi tech-savvy and I strongly dislike documentation such as "adjust the php on the correct page". Which page did you say? I think there is a strong correlation with the development of the themes. Some plugins seem to mess up the theme or the other way round, some themes don't adjust well to plugins.
Isn't it possible to come up with a solution that automatically adjust the plugin to your page's CSS?</description>
		<content:encoded><![CDATA[<p>I have been using widgets and plugins for a little while now and I love them.<br />
I have been experiencing some problems with configuring some though. I am currently documenting my problems for my thesis which will deal with software constraints in Wordpress <a href="http://www.annehelmond.nl/tag/wordpress" rel="nofollow">http://www.annehelmond.nl/tag/wordpress</a></p>
<p>I don&#8217;t mind a wide array of options as long as the documentation is good. I am semi tech-savvy and I strongly dislike documentation such as &#8220;adjust the php on the correct page&#8221;. Which page did you say? I think there is a strong correlation with the development of the themes. Some plugins seem to mess up the theme or the other way round, some themes don&#8217;t adjust well to plugins.<br />
Isn&#8217;t it possible to come up with a solution that automatically adjust the plugin to your page&#8217;s CSS?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anne Helmond &#187; Software constraints in blogging software</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1807</link>
		<pubDate>Fri, 01 Dec 2006 10:38:38 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1807</guid>
					<description>[...] The framework itself feels restrictive and I have been looking for tools to accomplish what I want. In the case of Wordpress I have been looking for Widgets and Plug ins that can achieve what I want. Or rather, the backend tools that shape and form my blog. Plugins and widgets are solutions to the restrictions in the Wordpress software, but are restrictions being reproduced on another level? What kind of constraints are built into the internet on the content level? How does software control meaning (content). These are several questions I am planning to ask myself in my MA thesis. I recently came across two related posts: Ranting on Wordpress Plugin Development by Justin Shattuck and Ranting on Wordpress Plugin Development by David at Blogger Pro  Bookmark to: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The framework itself feels restrictive and I have been looking for tools to accomplish what I want. In the case of Wordpress I have been looking for Widgets and Plug ins that can achieve what I want. Or rather, the backend tools that shape and form my blog. Plugins and widgets are solutions to the restrictions in the Wordpress software, but are restrictions being reproduced on another level? What kind of constraints are built into the internet on the content level? How does software control meaning (content). These are several questions I am planning to ask myself in my MA thesis. I recently came across two related posts: Ranting on Wordpress Plugin Development by Justin Shattuck and Ranting on Wordpress Plugin Development by David at Blogger Pro  Bookmark to: [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ranting on Wordpress Plugin Development</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1779</link>
		<pubDate>Thu, 30 Nov 2006 18:06:47 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1779</guid>
					<description>[...] Justin Shattuck, who is currently working on some plug-ins for WordPress, has released a rant on how many plug-ins are just too complex. I’ve noticed, recently, plugins are not as simple as I, personally would like to see. Plugins seem to have crazy amounts of options and configuration settings. Multiple tags and some are even extremely difficult to integrate. Even for those of us who are savvy with application development, specifically: PHP, MySQL, Ruby, XHTML and CSS; it can be a pain. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Justin Shattuck, who is currently working on some plug-ins for WordPress, has released a rant on how many plug-ins are just too complex. I’ve noticed, recently, plugins are not as simple as I, personally would like to see. Plugins seem to have crazy amounts of options and configuration settings. Multiple tags and some are even extremely difficult to integrate. Even for those of us who are savvy with application development, specifically: PHP, MySQL, Ruby, XHTML and CSS; it can be a pain. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Whisper</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1777</link>
		<pubDate>Thu, 30 Nov 2006 16:49:02 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1777</guid>
					<description>Well I do agree that a plugin should be "set it and forget it", but SOMETIMES the options are nice.  
The Good -- When I get a plugin I get it because I want the functionality it provides, but sometimes the method it delivers that functionality isn't always how I would like it.  I do like having a few trivial options to turn off some of the features of the plugin, and maybe to configure the way it is delivered.  As far as the extremely technical bits I like good documentation (missing in LOTS of plugins) so I can tackle that stuff on my own if need be.  I don't get upset when this happens cause I understand that most just want to turn it on and trust the developer has things set up just perfectly.
The Bad -- When the options are for setting things that are entirely to technical for one to understand they are a pain.  Not just for the people, it's also a pain for the developer because inevitably people are going to play with the settings and something is going to go wrong increasing the amount of support you have to provide. 
So I guess honestly IMO you should go with your gut, and offer as many options as you think the plugin needs.  Make sure you put it in really plain language so people understand what it's offering, and have really good documentation.</description>
		<content:encoded><![CDATA[<p>Well I do agree that a plugin should be &#8220;set it and forget it&#8221;, but SOMETIMES the options are nice.<br />
The Good &#8212; When I get a plugin I get it because I want the functionality it provides, but sometimes the method it delivers that functionality isn&#8217;t always how I would like it.  I do like having a few trivial options to turn off some of the features of the plugin, and maybe to configure the way it is delivered.  As far as the extremely technical bits I like good documentation (missing in LOTS of plugins) so I can tackle that stuff on my own if need be.  I don&#8217;t get upset when this happens cause I understand that most just want to turn it on and trust the developer has things set up just perfectly.<br />
The Bad &#8212; When the options are for setting things that are entirely to technical for one to understand they are a pain.  Not just for the people, it&#8217;s also a pain for the developer because inevitably people are going to play with the settings and something is going to go wrong increasing the amount of support you have to provide.<br />
So I guess honestly IMO you should go with your gut, and offer as many options as you think the plugin needs.  Make sure you put it in really plain language so people understand what it&#8217;s offering, and have really good documentation.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: &#160; Ranting on Wordpress Plugin Development&#160;by&#160;Blogging Pro</title>
		<link>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1743</link>
		<pubDate>Wed, 29 Nov 2006 17:28:56 +0000</pubDate>
		<guid>http://www.justinshattuck.com/2006/11/28/ranting-on-wordpress-plugin-development/#comment-1743</guid>
					<description>[...] Justin Shattuck, who is currently working on some plug-ins for WordPress, has released a rant on how many plug-ins are just too complex. I’ve noticed, recently, plugins are not as simple as I, personally would like to see. Plugins seem to have crazy amounts of options and configuration settings. Multiple tags and some are even extremely difficult to integrate. Even for those of us who are savvy with application development, specifically: PHP, MySQL, Ruby, XHTML and CSS; it can be a pain. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Justin Shattuck, who is currently working on some plug-ins for WordPress, has released a rant on how many plug-ins are just too complex. I’ve noticed, recently, plugins are not as simple as I, personally would like to see. Plugins seem to have crazy amounts of options and configuration settings. Multiple tags and some are even extremely difficult to integrate. Even for those of us who are savvy with application development, specifically: PHP, MySQL, Ruby, XHTML and CSS; it can be a pain. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
