[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Discussing and helping with openlilylib.org relaunch
From: |
Urs Liska |
Subject: |
Discussing and helping with openlilylib.org relaunch |
Date: |
Sat, 13 Feb 2016 12:29:34 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Now it is finally time to review https://openlilylib.org and give it a
new life. The site that is currently online is completely out of date,
not only visually and technically, but above all conceptually. What it
should become is a rather small site about openLilyLib as what its core
intends to be: a library infrastructure. So I'm going to throw out all
the secondary projects that aren't directly related to that idea.
In addition I want to prepare a structure for presenting package
documentation which will go to subdomains like (non-existing)
https://scholarly.openlilylib.org.
I would be happy about any assistance with this project because I
*could* do it alone but a) I don't have sufficient time to work my way
through all the obstacles and b) of course when doing something like
this with a few people chances to succeed and finish are significantly
higher ...
The main site will have a general introduction to openLilyLib and a
catalog of packages that are considered members of the openLilyLib
family and that are documented on such subdomains.
I want to create the main site and the doc sites using Bootstrap as
statically served pages. The main site *could* be done hand-written but
I would prefer finding the appropriate static site builder to create it
from Markdown files and assets. The documentation subpages of course
*have* to be generated through a builder, and I would very much prefer
one written in Python, because that's what I know best and because I
expect to use python-ly for several aspects of generating the package
documentation pages.
So the first step is creating a new website for the main site, the
second designing a template structure and design for the package docs.
Building a script for generating package documentation will be a third
step that we'll hopefully start doing as well, but in a way it's
independent from the first steps. This will be a tool that can be run
against any single oll-compliant package and create a self-contained
website that is usable as a "child" to openlilylib.org (that is, a
"Home" link to openlilylib.org will be the exception to the
self-containedness).
So as said I'd be happy about anyone approaching me who
- is interested in openLilyLib and
- knows
- Bootstrap
- LESS
- the visual part of web design
- (Python based) static site builders
or any usable subset thereof.
Best
--
Urs Liska
www.openlilylib.org
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Discussing and helping with openlilylib.org relaunch,
Urs Liska <=