I'm trying (desperately) to collect good ideas for a backend form to manually map various types of content to navigation items.
The problem is apparently very common, but since there are gazillion types of content, and as many content management systems, no common approach appears to even exist.
To the point. Can anyone recommend an example of simple yet functional form that would allow an inexperienced user to quickly attach various content to navigation? The supported behavior should cover thoughts like "this menu item should contain articles with tag 'foo', 10 items per page", or "this menu item will contain feedback form and an image gallery named 'bar'" (no pun intended :).
The best approximation to combining very different things in one visual form I've seen so far is the advanced search form in Mac OS X Finder (attached, in Russian, but you get the idea), but since it is meant for a totally different application, it's a bit off.
Any input would be appreciated.
It seems that a bit of technical detail wouldn't hurt. The system in question uses 100% code-design separation, meaning that upon user request a dom document with dynamic data is built and passed to the templating engine to produce xhtml.
Dynamic data is prepared by php methods, the engine allows for URL-to-method(s) mapping.
There is a need for a backend-configurable controller that would link certain URLs, essentially navigation item identifiers, to a set of method calls that fetch the data.
So, in theory I need a form that allows to translate URL like
into a method call, say:
cms::listArticles('about', 10, 0); // ^^ tag, ^^^^ limit/offset
in a user-friendly way.
Hope this didn't make things any more confusing :-|