[documentation] Proposal for handbook maintenance automation

[Steven Peck]

Tabs doesn't solve the structure problem.  It can help/solve it for
individual content and is something we should look at, but the overall
strucutre is still not solved with it.

On 8/9/07, Peter Wolanin <pwolanin at gmail.com> wrote:
> Fore *presentation* of different versions as tabs, perhaps we could
> convince the d.o maintainers to allow a small jQuery plugin/script so
> that with JS enabled sections of the content on the page could be
> organized into tabs using a simple stadardized set of classes or other
> tags?
>
> such as:
>
> http://www.stilbuero.de/2006/05/13/accessible-unobtrusive-javascript-tabs-with-jquery/
>
> Note with a super-small module to add the JS we could implement
> hook_form_alter so that this structure of the list and divs is the
> default content for new handbook pages...
>
> Or a custom filter could add this list to every handbook page (hence
> you jsut update that code when there's a new core version) and
> transform some custom tags like <drupal6></drupal6> into divs with the
> right classes?
>
> -Peter
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>