Use advanced help module for project* in D6?
| Project: | Project |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | 6.x-1.0 wishlist |
Jump to:
I've been using Views2 quite a lot, and one thing I like about it is that it's tied in nicely with Earl's new Advanced Help module. I think we should think about using this module for project* in the D6 version (though we probably wouldn't require the module).
My thought was that we could create some general documentation that would come with the module. Then, sites would be able to basically create a "translation" of the advanced help documentation for their own sites if they wished. We might do that for d.o to help users out.
I don't see much downside in doing this, other than time. Since views strongly suggests the use of the module (but also doesn't require it), I think there's a good chance that many project* users will have installed it anyway.
Any thoughts on this?
#1
+1
#2
Just today I had a user of my project system say "it would be nice if there were a little help icon next to each of the boxes above the comments so I know what they all mean."
So...count me on the list of people willing to help test and write the docs. I'd be fine if it were a requirement or if it were just a module that could be added which would then be used if it's installed (much like Views does it). Either one seems reasonable...
#3
I'm in favor, too, so long as it's not a required dependency, but an optional add-on. Yay for documentation that lives close to what it documents.
#4
This would be a great way for people outside of the core project* team to contribute to the port (and UI for d.o).
#5
Tagging for #439958: Document issues left before 6.x official release