Comments on: Why Habari isn’t Ready for Me http://pieceofshep.com/2008/10/why-habari-isnt-ready-for-me/ this is me Wed, 17 Mar 2010 03:06:21 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: mikelietz http://pieceofshep.com/2008/10/why-habari-isnt-ready-for-me/comment-page-1/#comment-21782 mikelietz Fri, 05 Dec 2008 20:06:12 +0000 http://www.mikeschepker.com/blog/?p=880#comment-21782 There's got to be *something* we can use to bribe themers and technical writers. Duly noted about plugins without documentation. I know I'm responsible for at least two or three of them, and should fix that any day now... There’s got to be *something* we can use to bribe themers and technical writers.

Duly noted about plugins without documentation. I know I’m responsible for at least two or three of them, and should fix that any day now…

]]> By: Chris J. Davis http://pieceofshep.com/2008/10/why-habari-isnt-ready-for-me/comment-page-1/#comment-21454 Chris J. Davis Fri, 24 Oct 2008 15:39:33 +0000 http://www.mikeschepker.com/blog/?p=880#comment-21454 Very good post Shep. I agree with most of your thoughts here, Habari is still in many ways, a web app for the tinkerer. But, so was WP in the beginning. We'll get there. Very good post Shep. I agree with most of your thoughts here, Habari is still in many ways, a web app for the tinkerer.

But, so was WP in the beginning. We’ll get there.

]]> By: Chris Meller http://pieceofshep.com/2008/10/why-habari-isnt-ready-for-me/comment-page-1/#comment-21453 Chris Meller Fri, 24 Oct 2008 15:36:45 +0000 http://www.mikeschepker.com/blog/?p=880#comment-21453 These are some very good points, and it's nice to see someone outline them, rather than simply saying "it sucks" or "it's not ready". I know that widgets are on the list for things several people would like to see (myself included). Documentation is a huge thing we need to work on. At present documentation efforts are thwarted by the ever-changing codebase, just as themes are constantly being updated. That makes it particularly difficult to keep updated and only complicates an already tedious, thankless job. The 0.7 release is tentatively slated to focus on themes, and should hopefully help address widgets and help settle things down with the theme API. Once the theme engines are more "set in stone", documentation should also be able to catch up more easily. Stay tuned, and be sure to check back in as we get closer to a 0.7 release, I think you'll be pleased. These are some very good points, and it’s nice to see someone outline them, rather than simply saying “it sucks” or “it’s not ready”.

I know that widgets are on the list for things several people would like to see (myself included).

Documentation is a huge thing we need to work on. At present documentation efforts are thwarted by the ever-changing codebase, just as themes are constantly being updated. That makes it particularly difficult to keep updated and only complicates an already tedious, thankless job.

The 0.7 release is tentatively slated to focus on themes, and should hopefully help address widgets and help settle things down with the theme API. Once the theme engines are more “set in stone”, documentation should also be able to catch up more easily.

Stay tuned, and be sure to check back in as we get closer to a 0.7 release, I think you’ll be pleased.

]]>