I assume user input is welcome here... I have a "small" business site that will easily have 100-200 pages that I'm planning to move to radiant. On its way to publication, it is common to adjust the parent of a page as we settle on our structure and linking.
> I don't think reparenting should be a drag/drop operation - I quite liked to > idea of having a 'parent' drop-down list in the page metadata (though that > also has the problem with large numbers of pages). A drop-down list would be hard on the writers having to read through all possible parents. By the way, I am more likely to move a page up or down a level than to move it laterally (make its aunt/uncle its new parent). A lot has to do with the interface design, but teaching users one operation (drag-drop) for everything should be easier than remembering two and when each is to be used. Another thought. I've only looked briefly at things like scriptaculous JS drag-drop operations. Do they allow for cases where the destination location is off-screen (scrolling needed)? Otherwise you still run into problems with large numbers of pages (though you could move a page using multiple hops). > I'd also like to see the option of leaving behind a redirect action to > maintain cool uris. BIG thumbs up for this idea. I wish all the uri adjusting only happened on the way to publishing but the real world doesn't seem to always work that way for me. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
