Website Working Group

Happy to help with programming + content.


Would like to be considered a stakeholder for starters - can help with other things subject to languages used

I’ll be back on Friday and pick this up then.

It’s a 30 second job to convert the markdown into HTML and just put it up on the site, so I’m not so worried about that.

1 Like

Have released some minor changes to the current placeholder website - focusing on rendering the List of Spaces from the master google spreadsheet. The process is a quick’n’dirty hack, but at least we don’t need to manually sync the two lists anymore.

Hack improved to mildy stained… also added a map

And finished the evening with some styling - nothing about the new look is final, but it starting to look a bit nicer :slight_smile:

Last call otherwise we’ll call this the working group and move forward to set a Skype call or similar to kick things off.

However it would be great if all the above could write one post with links to research, documents and other useful stuff they have so far as a starting point for us to all get up to speed.

1 Like

Stakeholder and code.


Shall be lazy and start by linking to Russs’ list:

1 Like

summary of stuff I’ve been up to last week or so, wrt the website

  • Added some styling to the index page, a nice map and an auto-generated list of spaces
  • Space info now in a database with an admin UI - @stanto is master curator of space info
  • Developed a “github browser” that allows the markdown content in the /resources and /foundation repos to be browsed from the main site… thus acting as a kind of CMS

In terms of research, it can probably be summarised as:

  • Platform choices seem to boil down to: Python3 + Django OR nodeJS + ?
  • We could try to build some compatibility with a space member mgmt app (e.g. shared modules, architecture)… if we did this, the only real candidates I’ve heard of are South London Makerspaces site (nodeJS, see github: or CiviCRM
  • Existing (v1) website is python3 + django, with bootstrap-based styling on top - this could easily be the basis of all the extended functionality we’ve discussed, subject to a final choice on platform

Website before and after (comparing Dec 2016 as don’t have a snapshot of it from a week ago) :slight_smile:


We’ll hold an initial kick off meeting on Google Hangouts on the 20th April 2017 at 20:00 > 21:30 please RSVP to let us know if you can or cannot make it.

We’ll just reuse this Hangout to save making a new one:

will attend :slight_smile:

Will try to attend :slight_smile:

Damian Axford wrote:

have summarised my thoughts (inc issues on git) as to what an end-state website must, should and could do:

Have used the repo wiki to make this easily editable, as I’m sure it’ll undergo some changes and logging this all as issues seemed premature :wink:

Please feel free to add additional items and/or re-prioritise, but please don’t remove anything at this point… we can debate their validity later.

Payment Handling
Although a lot of the final discussion happened in the Web telegram group, we now have a decision on payment handling: GoCardless

We may change or add additional payment methods in the future, but for the foreseeable, we’ll work with GoCardless.

@russ already setup an HSF GoCardless account back when bank account was setup, so we’re almost ready to go with accepting payments and thus membership

Software Stack

Following discussion today the web working group (WWG) have made the following stack decisions:


As mentioned above this was selected.

This choice was made by considering the needs of member organisations, with business accounts, it was agreed that 99% of spaces would have accounts capable of direct debit and manually processing an annual BACs transfer wouldn’t be complex, and should it become an issue we’d revisit this.

The primary concern was that barclays-scrap shouldn’t be relied on as it puts more pressure on Russ to maintain it and he in effect vetoed this as the author.

We can in future look at Tide integration as they have a full API.

Python and Django

The existing site was built in this and the majority of professionals who want to help in the WWG use this throughout the day, so it seemed we’d get the best job by implementing this.

Template Django Template Language

Django guidelines suggest using DTL unless there is a real reason not to, it’s TWIG/SWIG esk so we selected this, although there was a nod to using something HAML-esk like PUG, but this isn’t a deal-breaker.


We’ve decided to use Bootstrap for now, and minor CSS changes, with a view to use SASS later as there is a python compiler for when we want to do some more substantial CSS modifications.


Web group are currently working through implementing the sign-up process - as described here (option 2 - Joe’s story):

Individual member sign-up code is complete - now in testing. Hope to release soon. Then it’s into Member Space sign-up.