I'd really like to help with this as much as I can. I've read a good deal about React, but haven't experimented with it in any projects. I'm hoping my experience with Ember.js will help me pick it up quickly. No matter, I'm happy to help and want to step up my involvement in Anahita.
Your knowledge will be invaluable. I'm doing research right now on what each technology provides, their ecosystem, and how they can be part of Anahita's architecture. Then I'm going to write a few paragraphs to outline what needs to be done in 4.4. Then we can start prototyping and gradually build forward.
It's more than just MobileFirst. We want Anahita to become a progressive web app. Right now we are partially there, but JQuery isn't the best technology for that purpose. Right now we are providing the user interface baseline and then progressively load additional snips of html code to add more to the page. Ideally we would want to only load data and do all the html rendering in the browser.
That would be very much appreciated - perhaps touch on some high-level terminology as well if you could and how it relates, eg progressive... things seem to have evolved a bit since mobile first had once meant responsive, at least as I had understood them at the time. And perhaps related, I've noticed google starting to cache some pages under technology termed AMP I believe, intended to facilitate mobile consumption relative to bandwidth and some other factors.
Part of the motivation in asking was also that I have been looking into 2017 priorities for new custom Anahita apps, one being more content-oriented and the later being more-presentation oriented. I think your comments here are enough alone to put one above the other for now, but the additional insight could certainly help drive the planning on the later, or even both.