Ember and SEO challenges regarding discourse.org

AI-generated summary

The discussion revolves around the challenges of building an SEO-friendly site using a client-side app framework like Ember, specifically in the context of Discourse.org. rcorsaro inquires about the trade-offs and potential solutions for developing a site that requires SEO optimization, citing the need to create each page twice (server-side and client-side). codinghorror references a related topic on meta.discourse.org and later shares a blog post by Robin, eviltrout, which addresses adding search engine support to JavaScript applications.

What were the challenges and trade offs of making a site that needs to be SEO and uses a client-side app framework like Ember? It seems like you have to make every page twice, once for server side and once for client side. Is there anyway to lighten the work? Anything you learned that you would do differently next time around?

This is covered in

I think? Or do we need two topics, is this about the development side?

Yeah, more about the development side. Overall, what’s the impression. Any lessons learned? As someone developing a few Ember.js apps, I’m interested. But it’s equally applicable to any client side app framework, I think.

See Robin’s new blog post at

1 Mi Piace