I’m look­ing for­ward to meet­ing many of you at Con­nect Web Expe­ri­ence in Basel. I’ll be lead­ing a ses­sion “Adobe Expe­ri­ence Man­ag­er 6 Dig­i­tal Asset Man­age­ment: Inte­gra­tions, Inte­gra­tions, Inte­gra­tions.”
What inte­gra­tion we are talk­ing about? As part of the demo cre­ation team and we often have a sim­ple job — impress the AEM future cus­tomer. While our team works under tight time­frames to cre­ate com­plex solu­tions, we are able to cre­ate work­ing pro­to­types lever­ag­ing superb AEM inte­gra­tion capa­bil­i­ties. Cus­tomers pre­fer to have solu­tions rough­ly work­ing from start to end rather than pol­ished frag­ment of this solu­tion and rest as fairy tale.
Dur­ing my ses­sion at Con­nect I will present inte­gra­tions that extends DAM capa­bil­i­ties:
  • FrameMak­er inte­gra­tion (what is FrameMak­er huh? The tool still used by seri­ous tech­ni­cal writ­ers http://​www​.authorxml​.com/)
  • Phan­tomJS and Slimer­JS (script­able Fire­fox and Chrome HTML ren­der­ing engines)
  • GeoSpa­tial AEM (did you know how good spa­tial index­es we can cre­ate with AEM and SOLR?)
Dur­ing the ses­sion I will focus on visu­al effect, but I know that in many cas­es imple­men­ta­tion code is as impor­tant as result. As soft­ware engi­neers it is not enough for us to know IF some pro­to­type is work­ing, but also HOW?
Feel free to con­nect with me on Twit­ter and GitHub.
0 comments