[liblouis-liblouisxml] Re: Static website for liblouis
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Mon, 7 Oct 2013 07:26:20 -0500
Keith Creasy from APH is now maintaining the liblouis.org website. I
would like it to contain material for liblouisutdml in addition to
liblouis. The two belong together.
Keith is also maintaining thhe brailleblaster.org website. We also
registered liblouis.com and brailleblaster.com so nobody could grab
them.
Johhn
On Mon, Oct 07, 2013 at 12:47:56PM +0200, Christian Egli wrote:
> Hi all
>
> With all the discussion about how to host our downloads in the future I
> looked at creating a static web site for liblouis which could be hosted
> anywhere.
>
> Why?
>
> It is clear that we will have to find a new solution for hosting our
> downloads. The easiest (and probably the most accessible) way to do this
> is to host them somewhere statically (e.g. via ftp). If we do this we
> might as well move over some of the other content, i.e. not just the
> downloads, and create a static web site. So, just for kicks I went ahead
> and created a static site using Jekyll, which was dead easy and quite
> fun.
>
> Where?
>
> A prototype of the site is hosted at http://liblouis.github.io. It is
> produced offline using Jekyll and Bootstrap3 and then copied onto a web
> server. Since I don't have hosting space lying around I just used github
> pages to host the site for now, but this could be anywhere e.g.
> liblouis.org. The site is produced mostly using text files (textile), so
> it should be easy to edit it using any text editor. To look at the
> source head over to https://github.com/egli/liblouis-website. For
> example the downloads directory contains the zip files and a simple
> index.textile.
>
> What?
>
> I moved all the content from the google code pages over except the
> issues and the source. So there is a front page, the news, the
> presentations, the online docs and the downloads.
>
> So what?
>
> This gives the liblouis project another option as to how we could solve
> the downloads problem and would give us long term a good and accessible
> way to present the project on the web. For now I think the best option
> is to leave everything as is (on google code) and only look for a
> solution for the downloads but long term I think building a static site
> is an idea to be taken seriously.
>
> So my questions for now are the following:
>
> - is this site accessible?
> - would it be easier to edit the site using any text editor, Jekyll and
> command line tools as opposed to some kind of web based management tool
> (like the google code admin pages)?
> - If so does it make sense to use Jekyll?
>
> Anyway, this was a fun experiment for me, if we decide to take this
> anywhere all the better.
>
> Thanks
> Christian
>
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
> -----
> Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter
> http://online.sbs.ch
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.com
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
