wvotta - Wednesday, July 9, 2014 9:37 AM:
One thing that does leave lots to be desired is the way forms are designed and implemented. Another is browser compatibility. So much has to be re-engineered when interfaces deliverable to other platforms and using a 3rd party open source CMS as the backend would no longer make that an Aras concern. Right now there are Drupal modules that help sites work with Google Glass -- something my company is interested in for augmented reality work instructions as part of the documentation package delivered to the shop floor. If we were to implement something like that, the AR interface/experience would be wholly external to Aras and only linked by reference, forcing the operator to be using a Windows or Mac PC with an approved Firefox or IE browser to find the relevant AR link and somehow load it to Google Glass. That alone would scuttle the project. I know apps are being made for mobile devices and maybe folks can code some for Glass, but nothing beats the simplicity of native compatibility. It's like virtualizing applications with spiffy VMWare or Hyper-V servers is all made moot by a website that works on most all devices and is capable of doing everything that application does -- and it's cheaper.
My suggestion is to stop re-inventing the wheel and turn to a real CMS that's maintained by one of the largest communities out there and my vote is for Drupal (Joomla and WordPress are other obvious choices but none with the flexibility and power as Drupal provides). And I'd love it if we could move off of IIS altogether, but understand how difficult that is.
