Skip to main content

EdGEL (The Edinburgh Global Experience Language)

One of the most admired frameworks in the world of website and web application design is the BBC Global Experience Language.  It is a set of style guides, principles and tools that shapes the BBC's online presence, providing a common look and feel so that users are unaware they are browsing different web sites under the same brand.

I presume that many private corporations have a similar set of guidelines.  The advantage of the BBC GEL is that it is publically available, so we can see the thinking that has gone into developing it.

At the University of Edinburgh, we have developed a similar set of guidelines, which we call the Edinburgh Global Experience Language (EdGEL).  
EdGEL uses a responsive layout, which adapts to the size of the screen that is displaying the content.  It defines common University branding, including typography, colout theming palettes, and standard behaviours (e.g. if you click on the University logo, the web site will always take you to the University's home page).

At the technical level, EdGEL is implemented in HTML5 and Javascript, using the Bootstrap library.  It also uses the LESS or SASS pre-processors for CSS.

The first deployment of the EdGel was  on the central University Website.  It is also available for other web sites, and Development Services have packaged it to be used with all new web applications as well.

So, over time, most of the University's web presence will migrate to this common framework.  This is one way that we will give all our students, staff, and other users a joined-up view of the University that is focussed on your needs rather than internal structures.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…