title: Spring and rich clients (React.js, etc), preventing duplicate templates
body: <p>It sometimes seems to be that the answer of Spring to the explosion of rich web clients is: @ResponseBody. However, the ability to just supply json imho is no longer enough. As the client becomes ever richer, templates have to live on the frontend as well. There is handlebars and dust to help you deal with this although Spring doesn't document any of this. But just having the raw technology is not the same as having a smooth development path.</p>
  
  <p>What we struggle with is the question how to have things like </p>
  
  <ul>
  <li>Use the same templates on the client, that may be mobile, as on the server</li>
  <li>Server side rendering  </li>
  <li>Smooth integration with React.js</li>
  </ul>
  
  <p>All of this with Spring in stead of Node.js where everything on this front seems to be a piece of cake. There seems to be precious little information on these challenges and if you have a significant template base, the idea of duplication on the frontend and backend becomes problematic.</p>
  
  <p>Any suggestions how to deal with this?</p>