[Falkirk] Volunteers wanted for the website

[iain matchett]

Erm...I lost my dueling pistol in my last duel :(

I'm best with functionality or if someone gives me a design I can work to -
don't know where your strengths lie Douglas/or if you want to do
it collaboratively/if you want to RPS for it?

OpenTechCalendar has a JS library - should be easy to modify (if needed),
they also say they have a JSON feed so that part can all pretty easily done

In terms of Octopress etc - I'm cool with anything, I can normally pick up
a new CMS pretty quickly, new languages even quicker (yes, I'm a rare breed
that hasn't touched ruby yet! but I got Ghost and some ugly ASP enterprise
thing down in a couple of hours)

Iain




On Tue, Aug 18, 2015 at 11:34 PM, Greg Sutcliffe <greg.sutcliffe at gmail.com>
wrote:

> Thanks everyone for the replies. Let me go through this a bit ;)
>
> On 17 August 2015 at 23:12, Douglas McCallum <dgmccallum at gmail.com> wrote:
> > I can do the HTML/CSS stuff if someone better doesn't come forward
>
> On 18 August 2015 at 06:40, iain matchett <iainmatchett at gmail.com> wrote:
> > Web guy checking in - I'm in :)
>
> Douglas, Iain - cheers! Do you want to duel to decide who gets away
> with not doing it? :)
>
> On 17 August 2015 at 23:52, Rathgild <rathgild at gmail.com> wrote:
> > Why not go down the line of using a CMS like Drupal or Joombla ? That way
>
> On 18 August 2015 at 10:03, iain matchett <iainmatchett at gmail.com> wrote:
> > A static site would probably be a good idea
>
> On 18 August 2015 at 09:18, Dougal Matthews <dougal at dougalmatthews.com>
> wrote:
> > I would recommend doing something as simple as possible.
>
> I agree with something simple and static. The only thing I have
> familiarity with is Octopress, itself a wrapper around Jekyll, which I
> use to write my infrequent blog. It's a triviality to run "rake
> generate", add it resulting changes to git and push it to Openshift.
>
> CMS is a good suggestion, but probably overkill for what we need.
>
> > What are the goals of the website? Just to show the next event?
>
> Aha, the can-o-worms question. Right now, yes - a landing page we can
> direct people to, next talk, and probably talk history so prospective
> new members can see what stuff we cover (and so I can avoid repeatng
> myself with topics/speakers).
>
> We do post stuff to OpenTechCalendar - would that work as a source of data?
>
> For hosting, I can set up a dedicated (free) Openshift account with
> multiple managers easily enough. Openshift is pretty straightforward
> (similar to Heroku, if you've used it) where you push a git repo to
> your instance. Sane?
>
> On 18 August 2015 at 11:31, Craig Skinner <skinner at britvault.co.uk> wrote:
> > Template Tookit is bloody good at this:
> > http://template-toolkit.org/
> > http://en.wikipedia.org/wiki/Template_Toolkit
> >
> >> then updating the website could be as simple as sending a pull request
> on
> >> GitHub (I'd set up Travis or similar to deploy the site).
>
> Good suggestion, thanks! I'll look into it. Should be easy enough to
> hook it to Openshift, I would expect. I was expecting to be using
> Github, yes - there's nothing to hide here, after all, so we may as
> well use a public host for the source.
>
> > For something this small, a local CVS repo would be fine:
> Wait, CVS? Why is that not dead yet? -10 internets for you ;)
>
> On 17 August 2015 at 23:52, Rathgild <rathgild at gmail.com> wrote:
> > I should point out that edlug have the lug.scot domain so if you want to
> > use, say, falkirk.lug.scot get in touch and we can sort something out.
>
> We already have falkirklug.org (currently a redirect to Google+) but
> if you wanted to CNAME, I'll happily buy you a beer or two - cheers!
> ;)
>
> Greg
>
> _______________________________________________
> Falkirk mailing list
> Falkirk at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/falkirk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/falkirk/attachments/20150819/8a6091fd/attachment.html>