The Flight InDesign Plugin that we developed a year ago is getting renewed attention recently, including an update for 2017 and new, easier, installers. I spoke at the Canto DAM Summit last week, and in preparation I explored a new cool feature that we’re slating for the next release, made possible thanks to the gradual evolution of Adobe CC Extension technology. Related to that is a better way of expressing the value of our core Silicon Connector technology, which can be seen by looking in a bit more detail at the other, bad alternatives to it. Below is my presentation from the Canto DAM Summit Americas 2017.
Seven years ago, Silicon Publishing stumbled into an opportunity to connect Adobe InDesign to remote assets in a very powerful and efficient way. Through the work of our developers, several of whom were part of the original team that built InDesign, we were able to make a very direct connection from InDesign to remote assets via URLs. InDesign DAM Connectivity has become a significant part of our work.
While other approaches rely on technologies such as WebDAV, which is known for latency and headaches, our direct approach has proven itself to be far more efficient, and is now the way that most leading DAMs handle such connectivity. We have over 20 DAM partnerships so far, with more on the way.
This post talks about 10 of the Connectors we’ve built, specifically those with partners who also have booths at the upcoming DAM NY 2017 conference. They are in chronological order, and nothing here is intended to say that one is better than another, but simply to talk about the unique characteristics of each as we’ve seen them in the context of connectivity from the Creative Cloud applications.
I recently participated in a presentation at Dscoop Phoenix with three companies that I’ve known for over a decade: Pageflex, XMPie, and Marcom Central. We had joined a “Composition Engine Panel Discussion” with web-to-print luminaries Jen Matt (of web2printexperts.com) and Chris Reisz-Hanson.
It was quite an honor to be on this panel, but an even greater honor has been the opportunity to work with these companies’ rendition technologies since they first came on the scene. I have been involved in solutions involving all four technologies, and I’ve met the developers critical to the success of the underlying rendition codebases. These range from: FusionPro, the composition engine under Marcom, which dates from the 1980s; to PageFlex, the PDF rendition library from BitStream also originating in the 1980s; to InDesign, dating from the late 1990s. InDesign is the engine that we and XMPie use – it was created in part by our staff.
Meeting the beast
I tried Adobe InDesign 1.0 roughly 18 years ago. I felt like I was in the cockpit of a spaceship, as I had felt before, when working with “professional” design tools: FrameMaker, Xyvision, QuarkXPress had been similar experiences. Working for one of the largest print conglomerates in the world, I knew that such a tool could produce flawless output worthy of the finest publications and the largest productions runs. I also knew how unlikely it was that I would ever produce documents with it by myself. Perhaps in collaboration with a professional designer or typesetter, but life was (and still is) too short for someone with my attention span to master such a thing without a compelling reason.
Historically, Silicon Publishing has delivered publishing solutions across a gamut of communications channels. In the first place, our Silicon Paginator product (first released in 2005 as the “XML Formatting Engine”), is a platform for flowing data through InDesign templates. As in traditional XML publishing, Paginator generates web, email, print and mobile app output from a single rendition-agnostic content source (or from diverse, orchestrated, content sources).
Multi-channel rendition, connectivity and interfacing are persistent themes in our practice, ever since the late 1990s when “multi-channel” became a buzzword to deer-in-the-headlights printers faced with the need to generalize into “communications” from the too-physical, too-easily-commoditized, craft of print.
I remember a channel called “CD-ROM” and now face channels such as “WebVR”, “IoT”, and “geolocated social” – the only constant is change.
Silicon Connector for Box 2.0 is finally available! When Silicon Connector for Box first came out in 2013, it was designed to let InDesign users access assets in the Box cloud directly. Since then, the Connector product has become so popular that we’ve added Connectors for 10 other DAMs/storage platforms. We have gotten continually better at extending Adobe Creative Cloud technologies, and we have now applied that experience to bring integration between Adobe CC and Box to an entirely new level.
I was thankful to attend Drupa 2016 and spent most of my time in Halls 7 and 7a looking at the range of online editors from around the world. The following five online editing solutions stood out for me from among the 15 or so that I explored.
For seven years, our Silicon Designer product has expanded in use, across many countries, languages, and use cases. From B2B applications where franchises easily manage brand collateral, to some of the largest consumer-facing document personalization sites on the planet, our product has proven itself to be solid and reliable, yet also very extensible. It is integrated with numerous forms of shopping cart, DAM system, workflow system, and database, and it has diverse forms of User Interface:
no two Silicon Designers look the same!
Making it easy for our clients to customize their unique implementations has been our top priority. We have found that web standards, implemented correctly, make all the difference.
As more and more organizations implement web-to-print workflows that meet their ever-changing business demands, they often find that customization of their chosen solution is a must. Yet with HTML5 based solutions, this customization layer can be a significant challenge. This is due to the vastly different ways in which software vendors decide to combine the overlapping technologies.