Comments for http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml en-gb 30 Sat 20 Dec 2014 18:41:24 GMT+1 A feed of user comments from the page found at http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml Tico http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=94#comment16 This post has been Removed Mon 28 Dec 2009 22:10:10 GMT+1 i_amGeorge123 http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=88#comment15 This post has been Removed Thu 12 Nov 2009 20:04:55 GMT+1 Mark Cronin http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=82#comment14 This is awesome stuff. I have been web building for quite a while now, and i would love to get into the nooks and crannies of the BBC site. Dynamic pages are always going to be the way forward, and learning things like ASP and PHP are a given.I'm just going to enjoy my Egypt holidays, until i must return to the dreary office from whence i came! :) Wed 11 Nov 2009 11:46:05 GMT+1 Jon-Jauncey http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=76#comment13 This post has been Removed Wed 09 Sep 2009 18:46:30 GMT+1 dextacy10-13 http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=70#comment12 Another good read, "If you're working in HTML make sure you design your document to be semantically correct and accessible" In regards to this section I read a couple of articles in dot net magazine one about reset browser styling to help ensure cross platform usability and another about printing out a design of the page with the most complex layout and then writing the html elements such as "img, h1, h2, a " on the page ignoring elements such as div so as to guage the best way to create a uniform site layout with tidy css pages. The articles was in dot net may 2009 entitled "slicing like a pro" and "css/reset documents".RegardsJames MyersWebsite Designer Tue 08 Sep 2009 17:08:31 GMT+1 Saurav_Rimal http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=64#comment11 This post has been Removed Tue 08 Sep 2009 11:59:57 GMT+1 HughDP http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=58#comment10 Interesting article but why do the BBC (and many other sites) still insist on fixed width layouts?Screens are getting wider and wider yet many sites still use a thin strip of content down the middle. Fri 26 Jun 2009 12:52:11 GMT+1 bigalanbuchanan http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=52#comment9 Although I enjoy making my websites at home it would be great to be part of such a huge organisation like BBC and be part of the web design team. I'm jealous.Alan Wed 03 Jun 2009 16:13:49 GMT+1 Monker09 http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=47#comment8 Hi there,I liked your clearly presented account, you make it sound so simple ! I would add that you should bear in mind rendering issues between browsers especially internet explorer because it is riddled with bugs.MonkerLink Building Specialists Thu 02 Apr 2009 17:50:58 GMT+1 tristanf http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=41#comment7 @afrodigital - Decisions on what sites are built and what content is published are generally taken by a combined team of technical staff (who design and build things) and editorial staff (who work closely with the radio networks and audiences) based on our strategy and the requirements of the radio networks.As you suggest, this will happen before the process described above, but it won't necessarily be a completely different set of people. Wed 25 Feb 2009 09:55:49 GMT+1 afrodigital http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=35#comment6 This is fascinating. Well done. Not only is the thinking lucid and logical -- the fact that coherent, conscious thought happens in this aspect is very satisfying to know. Question: WHO makes the decision(s) as to what content is publiched online -- and HOW (i.e. on what bases)?PS: E.g. particular bugbear of mine for years: Why does Moral Maze have neither a podcast nor an archive?PPS: From your exposition, it seems that you (info arch) go get the domain expert: would that be upon your having been commissioned for the site etc? Thu 19 Feb 2009 16:00:12 GMT+1 Andy Mabbett http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=29#comment5 And not a single mention of microformats!Nice work, Michael. Wed 18 Feb 2009 23:11:17 GMT+1 dradford http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=23#comment4 Hi there,I was first introduced to domain driven software design about five or six years ago, building enterprise software. A group of us started really getting into the Fowler ideas through the PoEAA and Analysis Patterns books. It's great to see the methods applied to web application design. The BBC work is looking really good at the moment, with the Comet-based radio visualisation, the iPlayer and the music beta site. Can't wait to see the new events site!!Damienweb developer, triple j radio (Australian Broadcasting Corporation) Mon 02 Feb 2009 01:04:31 GMT+1 oudineche http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=17#comment3 This post has been Removed Sun 01 Feb 2009 23:16:16 GMT+1 Alan Ogilvie http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=11#comment2 In my days as a web-developer I remember giving a presentation at the Design Council about 7 years ago with colleagues from information architecture and design. We presented how important it is to make sure all areas are represented when starting to build a website.Michael's presentation, as I understand it, is from a stage further on from the beginning - as there obviously has to be input from engineering about what is possible.By maintaining collaboration effort between the disciplines during development - engineering, design, information architecture and the 'business' - successful delivery can be achieved. In the same way as one wouldn't wish to end up with something that looks fantastic, but performs so poorly that is unusable - we wouldn't want to have something that has all the amazing engineering to make it top-performing but the interface is unusable.I remember working for an agency where we worked on a key implementation of a new CMS system for a big organisation. If it hadn't been for engineering work with information architecture we wouldn't have used all the facilities that CMS had available as the engineers were able to interpret the CMS and explain those features to the Information Architects. In the other direction - the IAs pushed the engineers to make the CMS 'sing' so we could implement, what was described by the CMS company, the most innovative use of their technology at the time.Team work. Sat 31 Jan 2009 13:26:55 GMT+1 ckorhonen http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=5#comment1 @trailbehind I see what you are saying, but I think in most cases the approach outlined works - with most websites you need to consider your data and the views you create atop of that data, which can be translated into your run-of-the-mill HTML/CSS.If we look at your site, you have what looks like a google map with data - something which could otherwise be represented as data in a table.Where Ajax/JavaScript/Flash/Flex/Silverlight comes in is where you start considering how the user will be interacting with the data. Not fundamental at any way to the data structure or how the backend works.Same goes for video players, or any other kind of rich interface.In the case of the article, I'd say that whilst it is keeping with the principles of progressive enhancement, it makes sense to start thinking about the need for these rich-frontend-technologies a bit earlier, around the same time you are designing your decor/layout CSS, since the frontend-experience will make or break your website. Fri 30 Jan 2009 02:44:15 GMT+1 trailbehind http://www.bbc.co.uk/blogs/radiolabs/2009/01/how_we_make_websites.shtml?page=0#comment0 I agree with all you have said, except for the bit about javascript/ajax. For a site like mine (www.trailbehind.com), all we have is javascript and ajax, along with some data embedded in the static pages for the search engines specifically.But the ajax/Javascript can't just be a tacked on thing. We have thousands of lines of Javascript. It's fundamental. Thu 29 Jan 2009 23:14:19 GMT+1