title: Transition from a core framework
body: <p>I wish all of you a happy new year.</p>
  
  <p>I'm new in a project that relies on Apache Wicket which is not exactly known for having a big user base these days. In fact, it makes it hard for us to find new people and we would like to transition to a newer framework eventually. Unfortunately, the codebase is just too big to "simply" rewrite the whole damn thing. </p>
  
  <p>What I wanted to ask is the following:
  Does anyone have a viable strategy for transitioning from a framework like Wicket to a more "modern" REST-Interface + JS-Webframework approach? I would think that it should be possible to use the existing API that Wicket must be exposing for its own frontend for whatever js framework we'd be choosing to later down the road create the whole frontend.</p>
  
  <p>Any ideas?</p>