List view
The goal is having all current "snippets" evolve into modules of the new "libraries". Actually this milestone has several parts to it: - deciding about a set of libraries and find maintainers for them (this is actually a non-trivial task) - moving units to the new location - properly document the units along the way.
No due dateCreate a website and an automated system that creates static web sites for `http://<LIBRARY>.openlilylib.org`.
No due dateCreate tools (Python script(s)) to retrieve the documentation from the openLilyLib files and produce usable HTML documentation from them. Consider intermediate data exchange formats for that step in order to be able to also produce documentation in other formats, e.g. PDF.
No due dateopenLilyLib has to be auto-generating its documentation. This is not only intended as a tool for openLilyLib but as a generally usable solution to document LilyPond code. This "API documentation" should then be accessible e.g. for IDEs like Frescobaldi. This milestone targets discussing and deciding about the input documentation syntax
No due date•0/1 issues closedUse the libraries that have already been created/moved to the new structure to consolidate the new structure. THis may result in breaking syntax changes but the code *using* it should still be manageable.
No due date•2/2 issues closedThe repository has to be reorganized, after an intial phase of growth. It has been discussed on [lilypond-user](http://lists.gnu.org/archive/html/lilypond-user/2014-07/msg00037.html)
No due date•1/1 issues closed