Hi Michael,

Thanks for taking time to reply.

That is great to know that the page nesting is coming up. I don't think 
we can use habari for our clients until that's in. looking forward to it.
Is that going in version 0.7?

In regards to the ordering. I agree with you that /some/ ordering can be 
achieved by using the right query, but that's a fairly rigid 
implementation. There should be some easy way for a client, as a site 
admin, to choose an arbitrary ordering that's not based on a content 
field like the title or the id or the publication date.

In the situation of using habari as a website cms, if we have a given 
page section - say 'Our products' to pick a common example - and below 
that a bunch of sub-pages for each product, the ordering might not be 
alphabetical by title, or by id, it might just be the client's choice to 
have one item before another (say if they want to push a new product at 
the top of the list). They likely will also want to be able to change 
that order at any time... they can pay the developer to edit a menu 
every time they add or change something in the admin. I reckon the 
administrator should be given a way to do so through the interface.

WP for instance did introduce a 'menu_order' field to their page system, 
which I actually really don't like, it requires people entering 
numerical values in a field to specify the order - seems they really 
didn't try very hard with that /feature/ (there you go, here's a free 
field) - but that does at least give the ability to specify an arbitrary 
order.

The WP comparison stops here. I guess if habari was to have something 
like that, it should be a smarter approach than just a free field like 
Wordpress did. That would put habari above WP in that area too.

I guess in a way i'm speaking on behalf of our clients - which will 
drive our potential use of habari - and this ordering thing has been a 
requirement over and over. I can't think of any website that we did 
where they didn't want to do this one way or another.

I think this would be a great addition if it's thought through and 
integrated a-la-habari :)

Ben

Michael C. Harris wrote:
> 2009/5/22 Ben Lagoutte <[email protected]>:
>   
>> The two main things that seem missing for us is the page structure:
>>
>> * There is no nesting of pages. I cannot see any way to nest a bunch of
>> pages together below another. Without that we can offer our clients a way to
>> organise their website structure.
>>     
>
> The next version of Habari will have taxonomy support, allowing for
> the description of all sorts of relationships between objects, and
> there will be a subpage plugin that uses that. There is actually a
> subpage plugin at the moment that lets users define a page as a child
> of another page, but it's incomplete and not production ready.
>
>   
>> * There is no easy way to order the pages. I know it can be done by
>> modifying the publication date but this doesn't fit that ease of use I
>> mentioned above. Seems overly complicated for a client to have to do that
>> just to order a few pages.
>>     
>
> I'm not really sure what you mean here. How and where do you want to
> be able to order pages ? In a way, pages are designed to be standalone
> for display rather than ordered. There is a page menu plugin that's
> specifically for ordering page menus.
>
> You can also pass an orderby parameter to Posts::get() that can order
> by any column in the database. A silly example.
>
> Posts::get(array('content_type'=>'page', 'status'=>'published',
> 'orderby'=>'title DESC'));
>
> It may be that taxonomy is the answer to your page ordering issues too.
>
>   
>> Otherwise, wow, genius!
>>     
>
> I have nothing to say to this point, but I can't snip it :)
>
>   

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to