Web Services
  • Social Media

  • A A A

    A BIG thanks to the IS Web Team!

    By , on 26 October 2011

    Just a short note to thank the guys in IS for their work behind the scenes on the Silva infrastructure.  Adrian Barker’s team have done a great job providing us with the infrastructure we need to improve the Silva CMS performance.  In particular Debs Pollard and Andy Sykes who did excellent work in moving the service over to the new Virtual Machines.  It was great to come through the difficult start of term period with very few problems.  We also have new caching servers available which will make things even better when we can implement caching as part of our upcoming upgrade.

    More on the upgrade soon!

    Why did we choose Silva!?

    By , on 23 September 2011

    A question often asked of us here in Web Services!  The choice was ultimately made by me and Neil Martin, we were the two Web Support Officers at the time but our choice was severely limited.

    The Content Management System Project Group (CMSPG) was set up in April 2002 to look into the options available for a CMS.  Very early on in the process that group settled on Zope as the framework for the future development of the CMS.  I was initially unimpressed by Zope on my first dealings with it.

    Several other universities had already started using Zope but with different CMS built on top of it.  In November 2003 I organised a Zope users meeting at the UCL and we had visitors from Bristol, Birkbeck, Oxford Brookes, ICH and others.  They were using different CMSs including Zope’s Content Management Framework (CMF), Plone and EasyPublisher.  In February 2004 I demoed some of the options for Zope to Information Systems (IS).  To say they weren’t impressed is an understatement!  Just after that meeting Neil discovered that his former employers, Luton University were using a Zope based CMS that we hadn’t heard off, Silva.  I quickly installed it and we arranged to go visit them.

    Compared to other CMS on offer Silva provided out-of-the-box organisational workflow which compared favourably to the community based alternatives where we would have had to develop the workflows separately which was something that would have been difficult to achieve quickly given our, then, limited Zope, Python skills.  The templating system was also very simple compared to the others and Neil and I could reproduce UCL templating very quickly.  It was also easier to build simple tools into it for template menuing etc.  It was the obvious choice for us.

    IS signed up Debs Pollard in late May 2004 to give us sysadmin support for the CMS and we finally started up the live service in early 2005.  Jon Bowlas joined up shortly after as our Silva Developer and we made great progress after that.

    There are now around 540 sites in Silva and we have some promising new developments on the way for 2012!  More on that in an bit.

    … and it’s goodbye from me.

    By Nick Dawe, on 31 January 2011

    Just a quick post to say that I’ll be leaving Web Services this week, so this will be my last post. It’s been great to be part of a skilled and enthusiastic team at Media Services, and it’s also been a pleasure writing this blog (although apologies for not posting much in the last few months!).

    All the best


    Joke of the day…

    By Nick Dawe, on 19 January 2011

    ‘So this SEO copywriter walks into a bar, grill, pub, public house, Irish bar, bartender, drinks, beer, wine, liquor’

    Goodbye to Neil…

    By Nick Dawe, on 10 September 2010

    As many UCL readers will know, our Web Services manager left us last month in order to emigrate with his family to Australia. Neil’s been working in Web Services for 8 years – a time that has seen huge changes in the Web and the way that we use it. At the beginning of this year, Neil’s role extended to becoming manager of Design and Web Services, in which he also had to grapple with the areas of print and graphic design. As well as being a encouraging manager and an expert on Web standards, we’ve also consistently enjoyed his humour, enthusiasm, and the opportunity to play with his iPad.

    A rare image of the Web Services team smiling. L-R: David Gillies, Jon Bowlas, Neil Martin, Ralph Bartholomew and Nick Dawe

    Silva updates

    By Nick Dawe, on 6 September 2010

    Here are a few Silva CMS updates we’ve made in the last month. We’ll endeavour to post similar updates as we continue to develop, fix bugs, etc. for the system over time.

    New code sources


    • Horizontal menu: It is now possible to display a single level horizontal menu based on the root items of your site using the UCL branding layout. This will display throughout your publication.
    • Mobile view: The custom mobile view of the UCL branding layout now displays in Android devices.

    Amended code sources

    • Accordion: it is now possible to add multiple accordions into a page.
    • Accordion: a bug that caused the code source to show incorrectly in IE6 has also been fixed.
    • Caption an image: browser compatibility bug fixed
    • Tabbed box and accordion: a bug that was generated when these two code sources appeared on the same page has been fixed

    Silva at 400

    By Nick Dawe, on 2 September 2010

    Just a short post to say that there are now nearly 400 websites using Silva at UCL (we expect the 400th to come in the next few days!). These don’t include test sites, or sites within sites (such as the many subsites in e.g. www.ucl.ac.uk/isd).

    As the service grows, we’ll continue to develop and improve its various facets as well.


    By Nick Dawe, on 12 August 2010

    I’ve been really inspired by the ongoing competition at JS1k challenging developers to build a JavaScript demo in under 1kb (and if possible, to fit inside a Tweet!). Many of the demos use the ‘canvas’ element, allowing for more intricate visualisations, while others are demoing fascinating techniques which I’ll be sure to investigate further.

    Anyway, here are some of my favourites:

    What's a good URL?

    By Nick Dawe, on 4 August 2010

    It may seem like an unimportant issue, but web editors might be interested in reading a recent post from CSS-Tricks detailing good practice for writing URLs:

    I was particularly struck by the URI ‘speech-friendly’ test: Can you easily say a URL down the phone to someone else, or do you have to pause between characters to say whether they’re lower/upper case? Do you have to describe any funny punctuation marks that appear? Is the URI unhelpfully long, and indeed does it even make any sense?

    Fight the system!

    By Neil Martin, on 30 July 2010

    Earlier this week a few of the Web Services team ‘attended’ a free webinar presented by Paul Boag of Headscape. For those who haven’t heard of Paul before (and who hasn’t?!), Paul is a bit of a guru for the web development community. For many years he’s been blogging and podcasting on all things web. What’s particularly great is that he completely understands that web-related work is often all about people and relationships.

    The webinar was titled ‘Fight the system’ and was targeted at internal web teams in large organisations. Large organisations, by their very nature, can create an environment that occasionally leads to issues of conflict between interested parties, departments, etc. and the web team have to negotiate their way through these difficult waters. This can then potentially lead to tricky relationships, poor decision-making, scope creep and an outcome where nobody is really very happy with the website.

    Paul focused on four key areas that web teams should consider. These were:

    • Raising the reputation of the web team
    • How to deal with conflicts, politics and problem people
    • How to get signoff
    • How to avoid scope creep


    In terms of reputation, some internal web teams (not necessarily this one!) feel undervalued and lacking the ability to steer a web project in the right direction. Paul suggested that we could all do a lot more to improve our standing and reputation. He suggested to consider some of the following:

    • Charge – even if it’s only for a small amount to add value to the work. We have a basic and extended service which does have a charging component. We’ve introduced this because we think it will better define the service that we offer. It should also add value to the extra work we do, such as additional edits that aren’t part of existing templates.
    • In your demeanour, be upbeat and positive – try not to say ‘no’ just for the sake of it. If a piece of work is going to be difficult to implement, explain the consequences and consider a phased approach.
    • Establish yourself as an expert – be willing to cite other experts as well, and make much better use of facts and figures. For instance a green banner with red text isn’t going to be great, because of accessibility issues, so rather than just saying it’s a stupid idea, show the ‘client’ links to an ‘expert’ article which explains why this won’t be ideal.
    • Celebrate good pieces of work – debrief after projects, and don’t be afraid to tell others about how well projects have gone.

    Conflicts, politics and problem people

    One thing that’s wonderful about web, but can also be frustrating, is that it produces an emotional response from users. Most of the time people do have strong opinions as to how their website looks. This doesn’t, however, mean that they understand best practice and user-centric design. In larger organisations there is obviously going to be politics between various silos, e.g. between technology and marketing teams. Also during meetings there may well be an individual that through sheer presence of personality can force through their ideas even if it’s not beneficial to the website. Paul recommended the following:

    • Accept it – learn to live with it, and find better strategies to deal with it.
    • Keep talking – problem people sometimes just want to have their voice heard, and will be most frustrated if no-one listens.
    • Avoid confrontations - there’s no positive outcome from such situations
    • Empathise with stakeholders – share their pains and concerns.
    • Show, rather than tell – web teams can sometimes use a lot of jargon which is unhelpful to the client. If you want to demonstrate, for example, a cool jQuery carousel, go off to a website that has one that you like, rather than talk about it using terms like ‘jQuery’ and ‘carousel’.


    Getting decisions made about web projects can be quite challenging as it’s sometimes not easy to identify who the decision maker is. This is, dare we say, a particular problem within HE, with its traditional committee structures. Paul gave us some food for thought and we may well adopt some of the following approaches:

    • Establish the decision maker – quite often this can be quite a senior member of staff, which does present its problems, as they are often very busy people. However trying to make decisions with an intermediary or a group of people tends to end with fuzzy results. Paul suggested meeting with key individuals, rather than groups, as you’re possibly going to get a much clearer picture of goals and objectives.
    • Try and adopt some of the processes that are used in agencies, in other words, set clear milestones and timeframes for each key decision. Explain this process to the client from the offset and make them aware of their responsibilities in meeting deliverables within the timeframes set (for example, delivering content on time).
    • Capture requirements – and be comprehensive!
    • Include them in the development process. Ask them to consider stuff on the fly during meetings. Collaborate, and also refer to earlier decisions where perhaps new ideas conflict with those agreed earlier.
    • Get them to focus on business objectives and less on opinions, such as what the website colours should be. Remind them of the user exprience when conversations steer more into subjective territory.
    • Manage feedback – ask the client to identify problems rather than solutions. Instead of asking for the homepage to be bright green, ask the question: what is the problem that this decision solves? Is the user base going to specifically benefit from having such a colour scheme?

    Scope creep

    The bane of all web developers is when a project changes considerably from its original objectives. This can be unnoticeable at first, but obvious half way through. For example a client changes their mind about design elements like fonts, colours, number of pages, site structure, ad nauseum. To avoid this happening Paul offered some advice:

    • As mentioned above use an agency approach. Detail the scope of work from the offset and set key milestones and deliverables.
    • Explain the process so that it’s well understood with no surprises later on. Establish roles and responsibilities of all parties. Make sure they concentrate on their role and not someone else’s!
    • Have a phased approach. If a client comes up with a great idea that is out of scope, mention to them that this is possible, but will have to be shifted to a new phase of the project. Collect the ideas there and then and spec them for later.
    • If everything fails fall back on charging!

    There was  a lot in Paul’s webinar that has given us plenty of ideas as to how to both better manage ourselves, and our stakeholders, and we’d like to thank Paul for sharing his insights – it was a really worthwhile event to be part of!

    If you’d like to find out more, it is available (although there is a small charge):