Make Advanced help more dynamic/flexible by using a content type instead of simple html files.

This system isn't really meant to store data in the database, it's meant to provide help for modules that can be standalone. Putting this into the database seems like what you really want to do is use it for a completely different purpose.

OpenBand talked about a module we call Context Help during one of our sessions a DrupalCon DC that answers the issues you raise. It essentially uses a content type to allow writing help pages and reference them to other site pages through the target page's URL. When a help button is clicked on the target page, the site displays the help node in something like a thickbox lay-over.

We built it because we needed to

• allow a user role the ability to edit help files and allow translators to post page translations without having to give them shell or ftp access to the site's server,
• provide help content for non-contributed module pages like core modules, views or exhibits, and
• manage the help content, and keep page revisions, through the CMS interface, rather than trying to version-control individual HTML files.

The help pages are stored in the site database but can easily be exported and transferred to other sites, allowing storage of the site's custom help info.

It's tied into a system we maintain so we haven't released it to the community yet. It got some pretty stellar reviews at DrupalCon, though, and Darren Ferguson, our engineer that built the module, will be breaking it into an individual module. I'd be happy to shoot you an email when it's available to give it a try/see if it meets the needs you have.