…For editing, at least. Sites built with Concrete5 will work in any browser, if they're coded for it. But the editing interface and the dashboard, both of which feature some pretty complex interface work, are only supported in:
- Safari 2+
- Internet Explorer 7+
- Firefox 2
Other browsers, like Camino and Opera, will likely support Concrete5 just fine. But IE 6 will not. Not even close. As I was mulling over this blog post I caught another one on the same topic. It seems that Apple is doing exactly the same thing with their forthcoming suite of web applications, MobileMe.
Not bad company to be in, and necessary. The sheer amount of time that goes into debugging things for one specific, eight-year-old browser is mind-boggling. However, dropping IE 6 support is not without its pitfalls: the sheer amount of time saved might overwhelm the typical developer, as she finds herself with much less to do and much less stress about the web in general. The key is to fill this time with something productive. Try tending a garden; read a lengthy Russian novel; teach yourself Spanish; take a cooking class.
(Oh, and install that IE 8 beta in some of your free time – it'll be released before you know it. And Firefox 3 just came out, so you'd better download that. And Opera 9.5. And Safari 4 is on the horizon.)
Maybe you'd better read a shorter novel after all.
one week later, we're ranked 800 out of 179,523 projects on sourceforge, with over 150 downloads. We've got handful of people helping in various countries, we're hard at work on our hosting and marketing materials… Our booth for osCon2008 is purchased, we're hoping to leave that event with 30 active developers contributing their time… we've basically got 6 weeks to get ready… very exciting…
Just had our 100th download of concrete5 on sourceforge. We've been talking to several developers who are helping us further refine the install process. Some guy from Brazil is even pitching in!
open source is neat.
Okay, who the hell turns their speaker volume up so loud that you can hear "YOU'VE GOT MAIL!" from their AOL account through their floor (our ceiling)? Our upstairs neighbors have received four pieces of mail today. We need to figure out a way to strike back. I'm thinking ceiling-mounted speakers and Ahnold.
From the beginning, Concrete has been designed as a system that makes the creation of pages easy, with a flexible "block" system available for placing items of content within these pages. As Concrete has matured, new data types have been created for different types of tasks. In Concrete5, for example, we have all sorts of these: single pages, page types, themes, blocks, elements, user attributes, page attributes, email templates, and more.
Well we still have a long way to go before I'd call it a polished product that didn't have a lot of lose ends, but the whole thing is stable and the important bits are working well. The UI has also settled down so it really feels like cleanup time to us. We're launching concrete5.org to try to drum up some help from the open source development community as I type. Sadly there's nothing for me to do but bug people about getting C's in the right cases right now, so I'm posting here so my team will stop scowling at me.
concrete5.org is live! yay, tell your developer friends.
I opened our fridge, and this is what I saw:
It occurred to me that this moment sums up exactly why Concrete is an excellent place to work. Let me put it out there for you:
Reason 1? An abundance of beer.
Reason 2? An abundance of humor. No, for the confused amongst us, we aren't PETA-hating, raw-animal-eating nutjobs. We are, however, irony-loving, hipster-leaning, Arrested-Development-watching nerds.
(Note: I did not open the bag.)
I arrived at work today and prepared to engage in my typical morning routine. Step 1: Put lunch in fridge. Step 2: Brew Coffee. Step 3: wait nervously until step 2 completes. Step 4…well, you get the idea.
Hey all, this is Andrew. I'm Director of Technology here at Concrete Websites, and I'm going to take the reins from Franz for a second.
I've been making websites for more than ten years – first as a production/HTML guy, then a web and database programmer, and now as a director of some very talented programmers. Through it all, a number of things have remained constant. One of those is the impressive amount of bullshit involved when talking about the web. For example, in preparing for this post I took a trip to The Web Economy Bullshit Generator, and while its layout is dated, its content is as hilarious and spot-on today as it was when it debuted. And as the web changes, new sites have arisen to chronicle its changing lexicon. Everyone, it seems, is hatin' on buzzwords.
Why do buzzwords get such a bad wrap? See, as engineers, programmers and information architects, we like precision. We crave it. However, language by its nature is mostly antithetical to precision; terms that get created to express complex concepts can't help but miss some of the nuance, because that's what language does: it distills the complex into something that a person can wrap their minds around without wanting to shoot themselves in the face. But engineers look upon this compromise between precision and accessibility with disdain, and as a result consider buzzwords a bunch of hokum.
I understand this distrust. However, as I've moved from doing day-to-day work in the trenches to more conceptual and managerial work, I've found myself engaging in the unthinkable: I've started to use terms like those so mocked above in serious and non-ironic ways. It started with AJAX, a decent word used to express a technical concept. Now I can't stop: words like "leverage," "scalable," and "monetize" are a part of every day conversation.
Why all the back-story? Hopefully, it convinces you that what I'm about tell you isn't the result of some knee-jerk antipathy toward "buzzwords." I use buzzwords. I think they have their place. I think they can assist in communication. However, when used in excess and in place of any actual content, they deserve to be mocked mercilessly.
Let such mocking commence. The victim? TechCrunch. Their latest article, Bill's Gold Watch, is bafflingly incoherent. Check out some of these quotes, as helpfully disected from the "article" by the second commenter:
- "cloud infrastructure battle"
- "made that platform relatively salivating"
- "while Google methodically mows down the marketplace"
- "going to consolidate Facebook's equity in social metadata and create a groundswell of OpenID adoption"
- "warm fuzzy feelings for Web site owners who become part of an expanding network of reuse of the original log-in"
- "The terms of service for accessing social clouds will normalize over the next few months as users gravitate toward sites that leverage their original investment in OpenID registration"
- "producing affinity based on less work, common interface guidelines, and pressure on Facebook and outside clouds to modify their terms of service to avoid having to reinitialize access to their social data over and over."
- "starting to accelerate in real time streams over Jabber and XMPP"
- "allowing the kind of piping currently enabled between Gchat/Talk, iChat, AIM, and Twitter, which together produce a common set of streams that all are recorded and archived in Gmail's Chat repository"
- "the last time we saw this type of viral spread, it was Adsense carried on the river of the blogosphere"
- "social graph being formed out of the combination of follow and filtered Track"
- "can provide infrastructure to model the unique characteristics of Twitter's dynamic graph using Facebook's avatars"
- "can fit into this like a glove, feeding downstream vertical versions of affinity groups to skinned Silverlight containers"
Jesus. Come on! I first thought of this blog post after reading the sentence "It's not that Friend Connect is going to slow Facebook down; to the contrary, it's going to consolidate Facebook's equity in social metadata and create a groundswell of OpenID adoption which in turn will drive Open Social app development." Who actually believe this?! I'll talk to you all day about social networking, social bookmarking, and grid/cluster computing, but if someone opines in my presence about the "social cloud," they're probably in for a confused look, at the very least. And the sentence "Live Mesh can fit into this like a glove, feeding downstream vertical versions of affinity groups to skinned Silverlight containers." It reminds me of that episode of The Simpsons, in which Lisa, upon seeing a sign for a "Yahoo Serious Film Festival," remarks, "I know those words, but that sign doesn't make sense."
Every industry and field has its echo chamber, in which nonsense is amplified to the point of credulity. The web, with its ability to propagate concepts so quickly and effortlessly, is probably worse than most. Perhaps TechCrunch is a victim of this. Or perhaps they're just trolling for article hits. But if you want people to take you seriously when you say something, it helps to actually say something! I'm convinced that's the true problem with buzzwords: they make it all too easy to write 500 word articles without saying anything at all.
So I originally architected Concrete CMS in a nice little bar in SE Portland to deal with an adCouncil gig we had with too many stakeholders and not enough time. That was many years ago, and since the early days my dear friend and comrade Andrew Embler has taken the loose direction outlined in my sketchbook of "blocks and collections" and made it work on fixed budgets for demanding clients. Concrete has had some really compelling concepts since those early days, but like any box of tools you use hard – there's some idiosyncrasies that drive you up the wall. Being the guy finally responsible for training clients, and getting content into working sites that make sense – I've been looking forward to getting my hands on the complete re-haul concrete5 for some time. I've peered over shoulders a lot, but today was the first time I got to play with it on a site I need to deal with.