On Tue, 2008-11-11 at 18:29 -0500, Owen Winkler wrote: > Benjamin Hutchins wrote: > >> * How do we best educate a WordPress themer (essentially the people > >> we're trying to woo) to produce a Habari theme? > > > > Most people are not willing to learn. However, those people will have > > to. We can't use Wordpress's theme system because they're theme system > > is based off a series of idiotic functions. Instead of a foreach as we > > do it, and the $post->permalink, they do things such as a > > while(have_posts()) and the_permalink and get_permalink. If we bloat > > Habari with these Habari will soon become a mess. > > > > I would suggest a support team and a full set of pages on the wiki > > would be a good start. > > Yes. A page that tutors potential WordPress converts on the differences > would be useful. > > I'm not in these cases saying we support these themes directly, or make > Habari like WordPress by using their functions. But I do think there > are conveniences that WordPress themers come to expect of which Habari > is missing an analog. For example, easy functions that output category > lists.
I don't believe we even have categories in Habari? However, things such as that can be made in the theme.php for every theme. Perhaps we should add more to the baisc theme and allow customizations though files. I for one am not a fan of the the wordpress category lists (or their other outputs) becuase they're not very easy to alter. So if we had basic features such as they do and allow themes to have files where they can change the output such as plugins can do. Doing this for comments, tags, and menus would be good. > >> * How can we make the theme system more easily handle common theming tasks? > > > > Now this is a good question. In modern Internet usage there are a few > > key aspects to consider: > > * XHTML is growing. Whether Habari wants to use HTML or not, many > > designers use XHTML now. A compliance must be made. > > Whether we even include functions in core that allow users to make > decisions on HTML/XHTML output format is a much larger discussion. I know of no CMS that can actually achieve valid XHTML as-is. However if you output XHTML as XML or just use XML then you get many advantages. IE8 is also adding support for this so not having support for it will put Habari behind. > >> * Is there a way to provide both WordPress and Drupal-style theme systems? > > > > Drupal? You'd have to be insane to try and have built in support for > > their themes. I would again suggest a support staff and documentation. > > Providing features such as this will make Habari become a bloated mess > > for those who use it because it's core nature. > > When I said "-style", that's what I meant, not direct support. The > contrast being that Drupal-style themes have a main wrapper template and > put content of different types inside it, whereas WordPress-style themes > have a different file for each type of content and then pull common > elements in via includes. > > Supporting both of these methods would benefit our users, allowing users > with either thought process to move comfortably into Habari's templating. > > In other words, I think we ought not focus specific on WordPress-style > theme support features, but instead target wooing potential non-Habari > themers in general. Okay. Sorry I misunderstood. I understand what you're saying here that makes perfect sense. Though I feel Habari and Wordpress themeing are very close. I would put more focus in support Drupal-style and Mobile and add a few more simplifies for the wordpress crossovers. > Owen > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
