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 just completed our eighth Silicon Connector, and over the coming months you will see some amazing new advances in connecting InDesign to remote assets, across the DAMs with which we have just finished integration. Because Connector lets InDesign talk directly to assets living in cloud-based DAMs, it is becoming very popular recently.
We have just identified the DAM that will become the ninth Silicon Connector. We chose Alfresco because, based on past experience, we know it is a solid system, and we see the user base growing recently. Alfresco is not just a DAM, it is a CMS, but our initial work is going to be just getting InDesign to talk to the assets using Silicon Connector. CMS integration has potential as well, but asset connectivity comes first, and this is very easy for us given the Connector foundation.
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.