Re: moving LilyPond blog to our website

[Urs Liska]

Am 04.06.2013 10:55, schrieb Janek Warchoł:
> Hi all,
>
> it seems to be decided that we're moving the blog to our website (i.e.
> to be hosted on lilypond.org),

Makes sense to move away from a commercial provider.

>   and we're doing it asap, because as
> Paul said:
>
> > > Installing WordPress is a one click operation. Don't forget to remove 
> > > install.php and readme.html for security when it's done.
> > >
> > > To backup the site, export the database structure and data, which is easily 
> > > done with cron, and rsync the folder contents elsewhere.
> > Please discuss!
> >
> > Janek
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> 2013/6/4 Paul Morris <address@hidden>:
> > people will link to it, and the longer you wait to move it,
> > the more broken links you create

+1. There already are links which will be broken.

> As i see it, there are a few decisions we have to make: 1) are we 
> going to use WordPress or something else, for example Mezzaine: 
> 2013/6/3 Federico Bruni <address@hidden>:
> > Another option could be Mezzanine, a CMS based on Django which has many
> > built-in features (including blogging).
> > Considering that many lilypond developers know python, it could be a wise
> > choice in case we need to hack on it.
> > Mezzanine has some scripts to import from other CMS (Wordpress included):
> > http://mezzanine.jupo.org/docs/blog-importing.html
> ?
> (my vote is with Wordpress, but i really have no experience apart from
> last few days)

The fundamental question is whether to host the blog on a 'live' (i.e. 
php based) system or with a static site generator.
What are the capabilities on the lilypond.org server (wrt installed 
programs and performance)?
lilypond.org is (currently) a statically served web site.

I think using a static site generator isn't really an option because any 
update would have to be compiled and uploaded by someone with the 
necessary write access.
But we first should know whether lilypond.org actually can serve a 
Django or PHP based site.

WordPress seems to be a quite 'big' application so there would be much 
overhead. OTOH the fact that it is quite comfortable to use makes it a 
good choice when we actually want to use it (and not to be busy 
configuring and maintaining it).

Of course Python would be a good thing, but PHP isn't hard to hack either.

> 2) what the precise address/location should be?  Paul suggests:
>
> 2013/6/4 Paul Morris <address@hidden>:
> > Ideally it could be at www.lilypond.org/blog/ on the lilypond.org domain and
> > to some extent integrated into the main LilyPond website.  (i.e. make it
> > easy to navigate back and forth between the two sites seamlessly)
> (another option could probably be blog.lilypond.org, but i have no
> idea whether that's a purely cosmetical choice or has some
> implications.)

I think I'd prefer lilypond.org/blog because it's consistent with the 
other menu entries.
But a subdomain could be more straightforward when it comes to running a 
live web application.
A subdomain can also be transparently mapped to another service provider 
if the lilypond.org server doesn't provide the necessary infrastructure.

> As for the integration, i think that the blog should be accessible as
> an item in the top menubar (I.e. next to Introduction, Manuals,
> Download and Community).

+1

We could also modify the "Pondings" box to point to the newest or a 
random blog post (of the 'productions' category).
(That's a redundancy anyway, and if we host the blog on lilypond.org we 
should sort it out).

> If we go for WordPress, Jacques Menu showed a starting point.
> Jacques, i count on your help as well! :)  There is no way i could do
> this alone.
>
> 2013/6/3 Jacques Menu <address@hidden>:
> > Hello,
> >
> > I've switched from CMS Made Simple (lives up to its name) to WordPress for its 
> > power and rich set of plugins.
> >
> > Using 3.5.1 and a child of the new twentytwelve template makes browsing on 
> > phones and templates much more practical (you can check  with 
> > http://gioiacantar.ch).
> >
> > You'll need:
> >          - write FTP access to the folder hosting the site;
> >          - a dedicated MySQL database;
> >          - PHP activated;
> >          - ability to run cron tasks.

As mentioned above this would be crucial. So someone involved in the 
hosting should check and clarify .

Urs