[ciphershed] Re: Website & publicity
- From: Titanus Aegis <titanus_aegis@xxxxxxxxxxx>
- To: "ciphershed@xxxxxxxxxxxxx" <ciphershed@xxxxxxxxxxxxx>
- Date: Wed, 18 Jun 2014 13:18:17 -0500
My advice is to go for WP or a similar CMS platform. Html is quite viable, but
it places a time burden on the person in charge of maintaining and updating its
contents, it and creates a potential bottleneck. More importantly, even if
Niklas wants to take on the task of maintaining an html website, by consuming
his free time with these low-difficulty tasks he'll lose out on time available
to invest in the more technical tasks (which less people are capable of doing)
involving developing CipherShed. A CMS allows verified third parties to devote
their time updating documentation and articles with little burden to the
webmaster.
Luis
> From: aforget@xxxxxxx
> To: ciphershed@xxxxxxxxxxxxx
> Subject: [ciphershed] Re: Website & publicity
> Date: Wed, 18 Jun 2014 13:15:12 -0400
>
> > On Wed, 18 Jun 2014 12:44:49 -0400
> > "Jason Pyeron" <jpyeron@xxxxxxxx> wrote:
> >
> > If it were me, I would keep the site in SCM (git for us), and publish it to
> > the
> > server via script (server pulls based on SCM change notice). It won't
> > matter if
> > its WP today and drupal tomorrow, and plain jane html in between.
> >
>
> Having git as a backup for the site sounds nice.
>
> I suppose when someone edits a page in WP (or whatever tech we use), we'd
> have to do occasional commits to git to make sure the version on git reflects
> what's currently on the website?
>
> Alain
>
>
Other related posts:
