We currently have a lot of content on MathHub an only an experimental version of MWS running on pine. The MWS service on MathHub should be made a primary feature that is fully integrated into the front-end and backend. This means in particular,
integration into the build processes (the MWS needs to be updated when things are re-built) (see #259)
we need a configuration about what is indexed that is either in the META-INF of the libraries and archives or in some Drupal-level config (not just some files on pine)
we need a (set of) good front-ends at the MathHub level that give access to the MWS daemon.
The reason we bring this up now is that we have a new student @a-hambasan who is starting to take care of MWS proper.
We currently have a lot of content on MathHub an only an experimental version of MWS running on pine. The MWS service on MathHub should be made a primary feature that is fully integrated into the front-end and backend. This means in particular,
META-INFof the libraries and archives or in some Drupal-level config (not just some files on pine)