12.14.2006 // 11:54 AM // 12 Comments More blog layout…

More blog layout...

After I showed the last one, some people were concerned about the two-column layout. To be clear, I’ve buit in the two-column layout as an option, but I wouldn’t envision myself using it too often — only on shorter entries in which the typical visitor could fit the entire height of the column on their screen at once.

Here is an example of the more common one-column layout, with an inline Flickr favorite and ma.gnolia link objects.

The inlines are my favorite part of this new system. Unlike a typical HTML link to an image, these are directly tied to Flickr/Ma.gnolia/wherever they come from originally. Thus, if I change a photo’s description on flickr, that description will also get updated in any blog posts I’ve embedded that photo into. I have the ability to display any attribute of that object in the blog post (for example, I could — if I wanted to — add the date/time a photo was taken or the model of camera used to take it).

And these embedded objects aren’t just for external content, either — I can also embed stuff whose original source is my local database, like uploaded files, Flash objects, MP3s, other blog posts, comments on blog posts, etc.

I love how they can be inserted contextually at any point in the blog post such that they exist near the entry’s text which refers to them — rather than just in a sidebar somewhere.

View at flickr »

Comments

  1. 001 // Luke Dorny (luxuryluke) // 12.14.2006 // 1:29 PM
    Freakin’ brilliant work. Love the automation of changes part. Really like the inline stuff you’re doing. keep it goin’ full steam! Pfff. smart people.
  2. 002 // Michael Heilemann // 12.14.2006 // 1:31 PM
    Now that’s some damn smart thinkin’… And it looks good too.
  3. 003 // gravesit // 12.14.2006 // 2:03 PM
    When are we gonna see this live?
  4. 004 // Jeff Croft // 12.14.2006 // 2:37 PM
    Hopefully within a week or so. :)
  5. 005 // ubernostrum // 12.14.2006 // 6:15 PM
    Yeah, that’s some smart thinking, Jeff… I wonder how you came up with the code for that stuff ;)
  6. 006 // Jeff Croft // 12.14.2006 // 8:57 PM
    Blah blah… What James is referring to is that Ellington, our commercial CMS has the same inline concept as what I’m doing with my blog. No doubt, this was the inspiration — but to be sure, I didn’t swipe any code from Ellington, and I’m actually doing it quite a lot differently than the way Ellington handles it. That, and James helped me a time or two when I got stuck in Python. :)
  7. 007 // ubernostrum // 12.14.2006 // 9:11 PM
    I was mostly referring to the “time or two” you got stuck… Ellington’s inlines are a far different beast.
  8. 008 // Jeff Croft // 12.14.2006 // 9:39 PM
    Indeed — a far more complicated, cool, and sexy beast that would be far more over my head. :)
  9. 009 // D. Keith Robinson // 12.15.2006 // 8:37 AM
    Looks great man. Now launch it. ;0)
  10. 010 // whalesalad // 12.15.2006 // 6:32 PM
    I know the domain of your sandbox :) It’s looking awesome dude, keep it up, and please don’t close it out, I’m having fun checking in on it once and a while! Oh and don’t worry I haven’t told anyone where it is, I don’t want to ruin the surprise for you.
  11. 011 // Jeff Croft // 12.15.2006 // 11:09 PM
    Wow, good guessing! I thought it was pretty obscure! :)
  12. 012 // whalesalad // 12.16.2006 // 12:11 PM
    Lol its actually a pretty sweet domain idea, you should try launching with that :) have www forward there or something.