I’m happy to announce a brand new https://pkg.julialang.org site. You can search for packages by name and topic (topics are populated from GitHub) and view the docs for all registered packages in one central place. In the near future it will also have full documentation of all packages and regex code search.
We hope that this service will not only help Julia users discover great packages more easily, but also make it a little simpler to develop and publish those packages. It removes the burden from package developers of figuring out how to host docs and provide search functionality. The service is based on DocumentationGenerator.jl and has been the result of the efforts of many people, including @pfitzseb, @Venkatesh_D (both at Julia Computing) and @sdanisch (at NextJournal). Major thanks to all who have contributed!
The package doc & search service is part of the JuliaTeam Vision and is one of the services that Julia Computing is developing, hosting and maintaining to support the open source ecosystem. The service is also available as part of the JuliaTeam product for organizations that want to have centralized package doc & search for their private Julia packages.
It seems that the documentation link defaults to something built from the package readme. This sounds like a good fallback, but in many cases the package has a native documentation that perhaps would be better to link to. I noticed that the native documentation is indeed linked in some cases, but not all. Can one edit this link manually somehow?
The website seems excellent! I am very happy that one can search by tags, this makes perfect sense and seems to work! Hopefully this will make finding Julia packages easier for new users. We now all have to take good care to choose proper and plentyful github tags to help everyone!
I also appreciate the attempt at “automatic generation” of documentation, but it may backfire… Most packages built their own docs which has nothing to do with the README file. Wouldn’t it better to just link the documentation page instead of automatically generating something? README files have a “docs” badge, you can use this to automate the process.
For example, Finding DynamicalSystems.jl and clicking documentation just shows a rendering of the README and then has a long list of failed docstrings. This just gives the impression of non-professional documentation. I’d certainly like to avoid this given the absurd amount of time I’ve spent making the true documentation as professional as possible.
It would be nice if the “Explore Packages” link in julialang.org linked to pkg.julialang.org. I apologize if this appears unappreciative to the JuliaObserver devs (the current destination of that link), but I didn’t get the impression there were particularly serious intentions to maintain that (correct me if I’m wrong).