80 comments

[ 3.3 ms ] story [ 78.5 ms ] thread
This is very cool
The coolness is enhanced by the fantastic setup instructions and documentation. Excellent work rigoneri!
Thank you. I've been thinking about putting up a personal site for a while but never got around to it. I tend to be one of those "consumers of content" rather than producers (especially when it comes to blogposts). Hopefully this will change but this looks totally in line with what I am looking for!
{"meta":{"status":200,"msg":"OK"},"response":{"blog":{"title":"rigoneri's blog","posts":11,"name":"rigoneri","url":"http:\/\/blog.rigoneri.com\/","updated":1339467147,"description":"","ask":false,"likes":0},"posts":[ ... ]}

How does Google take to this? As far as I can tell it has to evaluate the JS before it can crawl the site; I got a few seconds of "Loading..." after the page had finished loading while it was pulling in the JSON.

https://www.google.com/search?q=google+bot+is+chrome

edit: when I click on an external link and then click the back button, I get the JSON too even with chrome. This is bad.

This is a known issue with Chrome. See: http://code.google.com/p/chromium/issues/detail?id=94369

The best way to circumvent the issue is to prevent the browser from caching the request (ex. cache busting via random querystring parameters), or to use different URLs for the HTML and JSON response (ex. appending '.json' to the end of the path).

THANK YOU SO MUCH! I've been thinking about how to go about setting up my personal site, and this is a perfect combination of producing and consuming/aggregating from my other services. Definitely going to start playing around with this.
JavaScript required to view the blog postings is a slight turn-off. What is the reasoning for it?
Good point. The reason was so I can swap from Django to Node easily if I wanted to without to much work and so the page can load faster on first request... I can probably change that eventually or just wait for a pull request :)
Woah thats a fantastic idea you have put together there. Well done sir!
The author's web site (http://rigoneri.com/) is cited as an example "Syte", but when I view that page on my iPad the right-hand side of the page is chopped off. Doesn't seem to be all that responsive (despite the author's claims).
It's at specific widths. I've seen other responsive sites behave like this and I presume it's just something with the media queries in the style sheet. If you continue to narrow your browser you'll see that it does respond correctly.
I fixed this issue just haven't pushed to rigoneri.com yet.. Thanks!!
Fix deployed! Thanks again!
I dont think so. Im using hackernews app on iOS,which displays your page truncated and unusable. Responsive means all widths are possible, not just some of the more common ones.
I don't know what this fix included but I can't see part of the text in my browser (about 1100 width). There should probably be some margin on the right side as well so text doesn't touch the border (or overflow).
Related, on http://rigoneri.github.com/syte/, down the page where it talks it about Responsive, it shows two images side-by-side.

One is clearly an example of responsive on a phone or tablet, but the other appears to be an example of broken responsive where the content got truncated as the OP of this thread mentions?

Why show an example of broken responsive design?

Spotted a bug on this. If you go back or forward in your browser to a blog post, it just shows a bunch of JSON code. You have to reload to get the site to properly show.
Also noticed this bug and wanted to mention it in case it wasn't just myself.
Noticed this as well. Throw this in your JS file somewhere:

$.ajaxSetup({ cache: false });

Great catch, I'll fix it... The reason is that it uses the same URL for a regular HTTP request and a XMLHttpRequest...
(comment deleted)
Why did you build it that way instead of having a specific API path?
Also, middle-clicking a link opens it in the same tab/window. Is that intentional?
I abhor things like this. Certain types of navigation completely override browser behaviour in this regard and it is somewhat maddening.
That and command-clicking on Mac both need to be controlled for when capturing the click event for links for sure.
Issue fixed. Please let me know if you find any more issues, or create an issue in github. Thanks!!
(comment deleted)
Thanks for taking care of this! I like what you're doing with this. As a Tumblr-head, I think you should also consider adding follow, like and reblog functionality. The API also has functions for this.

But either way, I'll be keeping an eye on this!

Anyone remember Friendfeed?
This looks really cool, the world needs more stuff like this.

One minor complaint is with the scrollable slide-outs. When you scroll down through a slide-out like the Instagram one, and reach the bottom, the page behind starts scrolling.

This is a common problem, and why I dislike using scrollable areas on web pages in the first place. There must be a good way to fix this. I just don't want the outside area to scroll when my context is inside the small scrollable area.

Had the same issue. Would love to not have the outside area scroll if I'm trying to scroll the slide-out.
Seems like one possible way would be to overflow: hidden the background scrollable area while a popover is open, assuming that doesn't screw up its scroll position. Big problem with that is that it makes scrollbars go away :/
Good work. I was thinking of something along the lines of Diaspora, but on a smaller scale. You kinda nailed it.
This is pretty cool, good work.

If you're a web developer+designer, it's probably not as useful, but for everyone else it rocks - and I hope to see people use/customize it to their liking. I love how it pulls so many services together. It seems like there's still some desire for some basic template for blogging after Dustin Curtis' last ordeal and now this, although it kind of seems like Twitter's Bootstrap has solved all of those basic problems for a lot of people.

This is pretty cool, I've been wanting to build something almost identical to this using node.js. Inspiration, this is!
Maybe you should make a Node.js fork... I was thinking about doing one myself!
Wintersmith and Blacksmith are both Node alternatives.
Clicking on twitter en the menu just takes me to the twitter account. I guess I'm missing something?
Due to the unexpected number of hits... Twitter is rate limiting the requests per hour... So instead of doing nothing it redirects to twitter...
Aha .. smart default!
Thats really smart. Maybe edit that into the blog post for now, otherwise people are going to be confused and submit bug reports (like i was going to).
Alright. I'll bite. I'll deploy it tomorrow and give it a whirl and see how it stands up :)
This is very, very cool. One request: would you consider making the color thing not part of the license but just a "polite request"? I understand where you're coming from and have no problem complying, but it's a little confusing and unclear what the legal implications of the rule might be. For example, what if someone forks it and changes the design, getting rid of the border around the pic entirely? I think your rule is very reasonable, but would be better enforced through the honor system, not the law. (Or edit it to make it clear it's not part of the license.)

Also, I personally found it surprising that a second click on one of the social links (e.g. Github) opens the full page on Github. I expected it to be a toggle where the second click would make the Github tab disappear. Not sure if that's just me, but maybe a separate "pull out" or "full window" icon you can click would be more intuitive.

Agreed! Will do! Thanks for the suggestion!
(comment deleted)
I really wanted to hate this, but this is actually really well done. Great integration while making it feel native to the site. I love this.
Same here -- I'm not a fan of anything but self-hosting, but I LOVE the simplicity of this thing, it's very sexy. I just wish it would support OStatus, for example. There's depending on third parties, and there's depending on third parties :P But that's what open source is for, right?
Wow, this is totally awesome! I'm going to give it a whirl tomorrow. I just switched from Django to Ruby on Rails and fell in love with the framework, so maybe I'll try porting Syte to Rails someday.
Hell, yes. This is one of the kickass ideas I've ever seen in a while. Simple, matter of fact and very usable. Thanks!
The design has a problem on my eeepc, because I can only see half of the menu items on the left. I know that "position:fixed" is the "chic" thing to use currently, but still: don't. It almost always causes some problem.
I'm seeing the same thing on my 1366x768 display. I think screen height is often overlooked in responsive designs.
I love the idea, design, and choice of frameworks/libraries, but I have one beef: I really, really dislike sites that prevent me from clicking with my middle mouse button. I open almost all links in new tabs using my middle mouse button and, currently, I can't do this on Syte.
Horrible border around the image. And no mention of your inspiration? Come on man, you even use the same spelling type. We can't change the border? Seriously...that's ridiculous.
Very good job. And props for setting it loose! Love the git integration :)