So i had an idea to make pkgdoc into a sort of go get proxy and a terminal based package manager client similar to pacman on arch linux.
This leads to a list of things im personally looking into implementing.
We need to provide a pkgdoc semantic for tags in the documentation for a search query that can also be used to provide an efficient way to sort libraries into a categorical fashion.
That way we dont get lost in a sea of packages.
I suggest to support this by adding a semantic like this. .
//This is a golang wrapper for redis
// ect ect ect..
package Redis
//[TAGS: redis, datastore, wrapper]
If the TAGS semantic isnt provided in doc.go then we can just have it added to the unsorted section. Also we could define a default list of categories that will match with certain tags, for instance datastore would be a good example of a genre of code that would provide better organization of package when navigating from the browser.
Also another idea is to have it pkgdoc.org act as a proxy that will redirect go get to the appropriate package. Then you could introduce authenticated users who have permission to change where this redirects. This would greatly help situations where a project moves from one service to another while not breaking code that depends on the original location.
Example:
import "pkgdoc.org/redis" //Redirects to stored url to package hosted repo master branch
import "pkgdoc.org/Mortdeus/redis" //redirect to user Mortdeus's forked repo
import "pkgdoc.org/redis/test" //redirects to test branch if it exists else returns 404
There are a bunch of cool ways this could be used and in my opinion is a prettier and much more convenient way to use go get import semantics.
Also I think we could extend pkgdoc.org into being a general purpose web application for other languages to. I assume you were thinking of that since you have the url for pkgdoc.org.
We would just have to introduce a specific format for documentation in languages to be used in pkgdoc.
I mean we could have a py.pkgdoc.org, ruby.pkgdoc.org, c.pkgdoc.org, cpp.pkgdoc.org, ect...
Just a thought, but im already going ahead and working on making this legit. Also ill work on the aesthetics of the website and create a logo if you want.
Heres some examples of my design work.
http://imgur.com/a/vN1o1,
http://www.gocos2d.org/ (still very early in terms of website layout, but the logo is finished)
Let me know what you think about all of this. :)