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.
Silicon Connector is enjoying huge popularity, and as we build out more and more implementations (12 Connectors and counting!) the product is becoming more clearly defined, while the product roadmap is also taking shape. While the main feature of “connecting InDesign to URL-based assets” is itself quite enough of a product to save large authoring groups immense amounts of time, the “nice-to-have” features have taken on a life of their own, and become common to most new implementations. Here I will clarify the ways the product definition is being extended, now and into the future.
I hope to explain:
- What we originally meant by the term “Silicon Connector” and how this was consistently rather poorly explained by us, and in turn how it was often misinterpreted by the world.
- What we mean now by “Silicon Connector”. How to understand what this product is, and what it does.
- Where the product and its many variants (AEM Connector, the InDesign Plugin for Flight, the Widen InDesign Plugin, WebDAM CC Connector, etc.) are headed.
In places, this post quotes heavily from the original blog post about Silicon Connector that came out when we first announced this product in 2010. At that point of time we had a narrow perspective on the product. Six years later, it has grown quite organically and evolves in response to feedback from thousands of users worldwide, as it connects InDesign to a diverse and growing array of over 10 Digital Asset Management systems.
We have been working hard on our Silicon Connector product, and as it grows exponentially in popularity, its value versus any alternative connecting Adobe InDesign to DAMs and cloud-based storage systems is being confirmed again and again based on the feedback of thousands of users around the world. Here are both the specifics of the roadmap and the general software product development lessons learned from product feedback over the past 3 years, especially during the past 6 months.
Silicon Publishing has built InDesign Server Solutions the past 15 years for the largest organizations in the world: from Web to Print applications for the likes of Amazon, Hallmark and Shutterfly to Database Publishing applications for companies including Disney, Nike, and Royal Caribbean. In this context we have seen well over 30 “Digital Asset Management” (DAM) systems from third parties providers such as MediaBeacon, Widen and Adobe, as well as a number of home-built concoctions, some of which have actually been quite powerful.
We are not DAM-centric: we focus on InDesign Server automation and in most cases we integrate this with whatever asset management the client has running. Only quite rarely do we encounter clients at the point they are contemplating a new DAM. So we have made pretty much every popular DAM out there work, at least to the point of serving assets to our publishing applications.
At the time Adobe InDesign was created, 15 years ago, it was generally impractical to store print-quality assets on web servers. A decade and a half later, however, the maturity of cloud-based file storage and asset management systems is making links from InDesign to assets housed in modern platforms, such as Box, a powerful solution for creative professionals.
Asset storage as of Adobe InDesign 1.0
Adobe InDesign is the tool of choice for the creation of high-quality print documents. It is nearly ubiquitous among those creating newspapers, magazines, books, catalogs, marketing collateral, or almost anything that prints. InDesign started out as a competitor to QuarkXPress, and given the dominance of Adobe in tangential technology (PostScript, PDF, PhotoShop, Illustrator) along with substantial and well-focused investment in the product, it was inevitable that InDesign would take the place of Quark at the center of high-end publishing workflows.