I think you might do well with a mixed approach. I'd keep your Home, Article and User pages server-side rendered. The more interactive pages that don't need to be SEO (dashboard, post article, search) look like good candidates for AngularJS. No need to make a single SPA app, those can be 3 separate apps, there's really not much overhead in doing that.
On Monday, February 25, 2013 at 7:13:12 PM UTC-6, Colin Huang wrote: > > > > > > > > > > > > > > > > > > *First of all, I have spent three weeks in getting my hands on AngularJS > and I am absolutely in love with it. Thanks to the folks who have > contributed their precious time to this remarkable work.Now that I have > picked up the fundamentals of AngularJS, it’s time for me to apply it to my > current project. My project is, however, not a single-page application, so > I am worried that the benefits might not justify the overhead costs, of > adopting AngularJS for the project. My project is broken down into six > sections (ie. the server needs to render the initial state for these > sections and return the result to clients in HTML). Within each section, > all functional/dynamic behaviours are in AJAX and thus this is the level > that I am considering to adopt AngularJS for.Home Page: A somewhat static > page that displays news and updates of the site to the audience. Search > Page: Allows users to search for articles/users with different criteria and > the results get displayed in the same page.Dashboard Page: This is where > users manage their own articles (ie. retrieve, update, and delete).Post > Article Page: This is where users submit new article to the platform; > before finalizing the submission, the user gets to preview the > article.Article Page: Every article has an unique and static URL; needs to > be indexed by search engines. If an authenticated user is viewing her own > article, she has the option to edit the article from here.User Page: This > is the public user profile page for registered users. Every user profile > has an unique and static URL; needs to be indexed by search engines.With > the structural design mentioned above, is my project a good candidate to > adopt AngularJS for? If the answer is “yes”, are there any concerns you can > think of that I should pay attention to?The only concern that I can think > of with this approach is to do with authentication. The server is basically > a hybrid of traditional web/html server and web API server. I have no idea > how the authentication should be done. Please help. Thanks a million. * > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
