This is a blog post our marketing and community engagement departments strongly warned us against publishing. At least we imagine they would, had they existed...

Hiding behind labels

Computer hardware and software projects typically have a code-name hung off them to ensure drunken bar room boasts don't become valuable slivers of knowledge in the vast game that is corporate espionage.

The Amiga prototype was known as 'Lorraine', 'Chicago' shipped as Windows 95, and during its development, Backpage3.0 became known as 'Oak Ridge'.

What's in a name?

Most code-names are random, but that was not the case with Backpage3.0. What is the significance of Oak Ridge in this particular case? It wasn't the scene of a first kiss, court to an epic sports victory or the rolling windy field beneath a beautiful act of losing a carnal innocence...

No, Oak Ridge is a laboratory. A place of research and development. This institute was born as one of the thrusts of the massive 1943 Manhattan Project. America poured massive resources into the development of nuclear weapons to counter a perceived attempt by Nazi Germany to do the same. To this end the Oak Ridge complex was tasked with the development of separation techniques that would yield weapons grade fissionable material.

Errm...! I don't get it?

The Manhattan Project was a secret. To the lay observer, Oak Ridge was nothing more than a large factory. A factory that demanded massive numbers of men, machines and an endless feed of bulky raw material ... but it didn't seem to produce anything. For years endless resources went in... but nothing ever came out!

This pattern rang a familiar bell. We couldn't help but get the joke and the moniker kinda stuck...! :)

We've adopted shorter development sprints now. Honest!

How do I love thee, let me count the ways**

1. My soul can reach, when feeling out of sight
   HTML5 has given us gearless local storage, a client side database and the ability to build apps that work without an always on 'net connection
   
2. I love thee freely, as men strive for Right;
   For the first time EVER, browser developers will have a spec that covers not just a desired behavior when everything goes right, but instruction on what to do when things go wrong - consistent, cross browser error handling is finally somewhere in sight***  \o/
   
3. In my old griefs, and with my childhood's faith.
   HTML5 builds on the original promise of HTML, redefining its comfort zone against which we've fought for over a decade, while widening and deepening to embrace modern use cases
   
4. I love thee with a love I seemed to lose
   HTML5 has relit our love for client side work - long may it last!
   

*Poets we ain't! This poorly rendered blog post was brought to you by the people who should know better!
**Backpage CMS went HTML5 native in July 2009 & has no intention of ever leaving!
*** We feel this is, bar none, the most important addition to HTML5!
Credit: Elizabeth Barrett Browning

I heard the most fantastic derisive comment today: the acronym WYSIWYG is commonly used for "What You See Is What You Get" when it usually applies to "What You Get Is What You deserve*"! :)

* with a generous dose of artistic license

A measure of spit and polish has been applied to the Web Manager and Blogging tools. The most obvious change is the addition of a date view and a cosmetic change to a number of icons, but the changes run deeper:

• Quick search can now search dates
• Quick search results are keyboard navigatable
• Quick search UI polish
• All views now show a document page type icon
• A/Z and date views can now be sorted acesending and decesending
• Document properties now allows for template independent addition of header and footer items (useful for page specfic styles or script)
• The tool now weighs in at 70% of its predecessor and makes three quarters fewer XMLHTTP requests

A little notice on some of the upgrades we're currently sweating over that will soon find themselves coming down the line.

• Support BpTags for shop, one for store categories, the other returns the contents of a users shopping cart
• Google sitemap now shows products at a higher priority
  
• Upgrades to the front and backend user management
• Section headings added to AZ module
  
• Improved HTML5 support for the FSE

The editor

Those of you sporting HTML5 websites may have run into occasional glitches when using the full screen editor (especially with block level elements).This is a known issue and we're working on a fix.

In the meantime we're chalking it all down to one of the joys of being on the leading edge (while ignoring the phrase 'Pioneers get the arrows, settlers get the land'...!).

They say necessity is the mother of all invention. I'm going to add an addendum to that. Hatred works too!

Backpage grew out of a frustration with repetitive tasks and a deep, vocal dislike for a mandatory three column layout. Most modern websites need templating, a data access ability and the facility to be extended in ways and means that are often impossible to divine. When development work on version one of Backpage began, few sites used a CMS (and most balked at the acronym) and those that did shared a very common layout. 

Templating typically took one of these three routes:

• Three columns, like it or lump it
  
• A XSLT (or similar) templating language
• Wrap-around server side includes that didn't apply a predefined page structure
  

On paper the XML/XSLT route is a marriage made in heaven. But this is real life. The XSLT route is nothing but troublesome, its promised benefits of flexibility and strictness are quickly lost under a mire of error prone and unintuitive programming with an undesired server-side overhead. I'm unreliably told most designers aren't programmers.

The SSL wrap-around include approach works well, but it isn't a natural environment for a designer and when done wrong (I'm looking at you WordPress) it just makes matters much much worse. Backpage would use this method for a time, but we couldn't help but feel, like the other approaches, it really sucked! ... So we continued to caste around for a superior alternative.

Temp-late

We took very deep peeks into the various templating engines out there, and while most had immense merit, we felt they were all a little too complicated for their own good- certainly nothing you'd open up to the less tech savy. Finally we came to the conclusion that everything was awful and we'd have to built our own!

The requirements:

• Ability to use ANY tool to create a template
• Support for xHTML
• Support multiple designs simultaneously
  
• Not enforce any design methodology on a designer
• Embrace best standards
  
• Reduced maintenance overhead
• Be simple! ... ish!
  

The result met all the requirements and birthed another Backpage feature: BpTags. The templating engine makes no assumptions or demands, allowing a designer to create a layout in the environment they are most comfortable with, yet can support the craziest of designs (I've yet to see a layout that can't be achieved!). Coupled with BpTags, complex, data driven designs became a piece of cake! And we like cake!

A full rundown on Backpage templating is available in our 'skins' support area.

I've written many words in the past on the subject of comments and moderation. In truth I find myself flip-flopping - loving the idea of growing an unfettered community that accurately portrays 2% of a websites visiting audience but reeling with the knowledge there's an inevitable need for the iron fist of censorship required to grow a useful and balanced article feedback mechanism.

Of course then I remember I'm just the guy who builds the tools and I get on with the task at hand!

Upgrades

The comments engine has received an subtle upgrade. The internals now take full advantage of the Backpage 3.0 API, so opinions and flames are poured to screen faster while using fewer server-side resources. The engine has also been opened up to support more than just blog posts, and can now handle product reviews for 'shop' and dozens of other applications.

The upgrade can be found on the comments module page.

Are you ready to hear the least imaginative name for an e.commerce platform ever? Shop! Yep, we called our main e.commerce module 'shop'! Not 'superZen', 'HyperBucksStoreCart' or 'profitMaker'. Just simple, boring 'shop'. We contend that all our imagination went into building it, so much so the ultimate christening became an afterthought.

So what does shop bring to the table?

• Easy categorisation
• Automatic image overlays
• Easy templating
• Ability to support a number of different payment gateways
  
• Real-time multi currency support
• RSS feed
  
• Search engine friendly uris
• Tagging and mapping of products
• B2B support
  
• Search
• All the usual shopping cart goodness
  

And we've stuck to our pillars of 'ease-of-use', 'search engine coziness' and 'speed'!

Shop is undergoing its trail by fire on a trio of backpage installations. Once lessons learned have been applied it will become available to everyone!

From time to time the question of software design philosophy comes up, and I find myself half cringing and half smiling. Over the years I've found myself falling between the cracks of the well established principles. I wanted all the best parts of KISS, UCD, TIMTOWTDI etc, but none of the baggage.

So rather than languish in some undefined principal-less netherworld, I did what any student of Aristotles theory of knowledge would; labelled my own.

The mosquito

The de Havilland DH.98 Mosquito was a World War 11 era light bomber which joined the RAF Bomber Command in 1941. In service 'the mossie' was noted for its speed and diversity (it would serve as night-fighter, transport and everything in between) and it was the platform of choice for a number of the crazier operations against Germany during the period.

But it's the early development stage of the Mosquito that interests me most.

Mosquito development

The DH.98 concept genesis was an Air Ministry specification titled P.13, issued on 8 September 1936. P.13 called for a twin-engined "medium bomber" suitable for "worldwide use" with the ability to carry a modest bomb load. The RAF hierarchy expected a heavily armed bomber made of metal and designed around the idea of fighting its way to and from a target (an idea that quickly cost lives, even for the mighty US 8th airforce and their armadas of gun bristled B-24s and B-17s). You can imagine their disgust when the plans for a small wooden airplane was presented to them...

de Havillands prior experience convinced him that a small streamlined wooden twin engined aircraft could be made fast enough to evade any potential fighter opposition, removing the need for a heavy defensive armament and associated crew.

The Air Ministry was not impressed. de Havillands bomber didn't conform to their concept of heavily-armed bomber formations and were very dubious of claims that speed would be a viable defense. They also questioned the use of wood, a design approach that flew in the face of established best practice - surely the evolution of the mighty Spitfire had proven sleek metal designs were the way forward.

But wooden construction would have the advantage of using a readily available non-strategic material that could be easily acquired while taking advantage of the existing skills of the large number of furniture makers in Britain. Consequently, production would be faster and easier with a delivery rate far in advance of any competing designs.

In production the Mosquito would live up to every promise de Havilland had made. Its wooden construction resulted in a light and easy to construct aircraft than was faster than the current models of the Spitfire, itself a very fast aircraft. When the Mosquito entered service in 1941, 'The wooden wonder' had a top speed of 382 mph, while the vaunted Spitfire could only reach 369 mph.

On 30 December 1940 the Air Ministry placed an order for 150 Mosquitoes, from then on the only complaint the RAF had about the Mosquito was that there were never enough of them! Cameras, cannon, radar and torpedoes were all hung off the aircraft as it found itself engaging fighters, tanks and submarines - roles never envisaged by the original RAF specifications, but roles the 'Mossie' was successfully employed. A total of 7,781 would roll off the lines until production ceased in 1950.

The mosquito principal?

So, that little history lesson leaves us with the following points and principals:

• Don't let trends supplant common sense
  
• High speed at any cost
  
• Small size
• Simple to maintain and extend
• Easy to pilot (*ahem*... use!)
  
• The innate ability to be extended in ways that override all the above features!
  

Backpage has been created with all these principles in mind, and like the venerable Mosquito, has found it has a propensity for appearing in the strangest of places doing the strangest of things!

Those of you wanting to know a little more about the wooden wonder could do worse than checking out the Wikipedia article on de Havillands 'Mossie'.

We're massaging existing backpage features as feedback and gripes are shared with us. The latest two tools to go under the knife are the tagging and mapping systems.

Mapping

Geotagging, you cruel mistress! Yet you languish unused on so many installations. Those who use it, love it but had a few suggestions to make it better. So with our listening hat on we've changed the user interface, contracting the 'mega-buttons' to give a more tag like look. To follow up with the change of 'look', we also added a tagging 'feel' - now multiple geographical areas can be associated with a web document or blog post.

Admins can also delete Geographical references by double clicking on the geotag they want to destory. Editing remains unchanged.

Tagging

A lot of people (read: everyone) HATED that we'd ignored the usual tagging convention of a comma delimited list of tags, going with a space delimited list instead. Well, we've come to our senses and rewritten tagging so it behaves as a user might expect. We also took the opportunity to tweak the UI, giving tags a 'button-like' appearance.

Finally we changed how tags are edited / removed, staying with the double-click approach seen in mapping, once you double click a tag a panel will appear offering the options to delete or edit a tag in-place. Fun!

Metadata typically doesn't ignite passion in most of us, but the following addition to the METATAGS bpTag made me giggle!

The ICBM meta tag

The "ICBM" name comes from an old Internet joke where a latitude-longitude coordinate pair is an "ICBM address*", that is, the destination of a nuclear tipped InterContinental Ballistic Missile. Good times! 

A little more geotagging goodness for BP!

* Don't worry, real ICBM coordinates would also include elevation data so this is only of limited use to terrorists! Probably.

...because it's been a while

So, what were we up to? Only retooling the 'little CMS that could' into a leaner, meaner beast. We've taken a long hard look at the content management tools arena, jotted down what we liked, crossed out things we hated and imagined things we've never seen but would love to play with. It all fit a pair of beer mats* and looked a little like this:

• HTML5 + xHTML support (we like those trailing slashes!)
• Full screen document editing
• Document versioning
• Sexy but simple UI
• Author transparent search engine optimisation
• A smaller, shared API
• Simpler/smaller database design
• The ability to draft pages (previous versions published 'on-save')
• Much improved external RSS handling
  
• Simple templating that doesn't rely on a programming language to implement
  

We continued to like the flexibility of reading everything from a database on request, but decided to up the ante with more agressive caching. Reexamining the BpTag idea we found it compared well with competing approaches and wasn't broken, so no need to fix it. We also retained the document hierarchy, augmented rather than replaced with a tagging system.

This resulted in a complete rewrite of the administration area and subtle refinements on the user end which has resulted in ... this little puppy!

* Yes, we actually bullet pointed our beer mats!

Yaaaay - the inargual Backpage Blog post! Right here we will share the inevitable hints & tips, our thoughts and reasoning on certain features, latest news etc. Tune in, it'll be fun!