I have a long time client who uses Contribute for the non-dynamic portions of a Coldfusion website. With Creative Cloud, Contribute is no longer available. However, I find it interesting that DW still offers "Contribute Compatibility" and "Manage site in Contribute" options (only to throw errors that Contribute is not available).
How am I to set up and manage new Contribute connections for this client when Contribute is not in CC? And I don't buy the "Contribute is being discontinued as a Adobe mistake" argument. Contribute 6.5 is in the works.
Since the site is a very large Coldfusion driving E-commerce site, it doesn't fit into a Business Catalyst profile of normal sites.
Am I stuck or could there possibly be plans on including Contribute in a Cloud subscription? Given the breadth of other products offered, I do not see how including it would be of severe detriment to the company. If it will NOT be offered in the cloud, What is a developer to do in this type of situation?
Thanks for any input, advice, or suggestions!
Adobe Contribute is not part of Creative Cloud but it will continue to be available as a point product. The Contribute engineering team will continue to provide updates and enhancements such as compatibility with Firefox, Internet Explorer, Windows 8, Mac OS X, and Microsoft Office and other workflows which are important to Adobe Contribute customers. The future roadmap for Contribute includes support for HTML5 and compatibility with new versions of Adobe Dreamweaver.
I don't need contribute per se. But as a developer, the ability to Manage the contribute setup (set / create accounts, roles,send keys, set rollbacks, compatibility, etc) is vital to being able to creating a Contribute compatible site for end users.
To not provide that functionality to developers means that the "simple" end user, the very non-tech people the software was designed to help are now the ones who have to set up the Contribute functionality. Seems a little counterintuitive.
Plus, by not providing a means for developers to set up and manage a Contribute compatible site, isn't Adobe missing out on opportunities for people who use ther high end tools (developers) to win over and generate revenue by recommending Adobe products to people who do not use their tools (end users)? Just a thought.
I never use the full Contribute product, so don't really care if it is in the cloud, but I believe the ability to set up and manage a contribute compatible site is a development role. An extension or management tool within DW would be a perfect mix for both the developer and facilitate sales opportunities to end-users.
I don't use Contribute or sell it as part of what I do. That said, I think most developers have long ago switched to server-side CMS solutions. Giving clients the ability to conveniently edit content from a browser makes more long term sense than making them purchase stand alone software which may or may not be supported in the future. Inasmuch as you're building the site with CF anyway, how hard would it be to add a simple CMS?
I could, but the client isn't really interested. the CMS built in coldfusion is a massive international E-commerce system so the Administation side is pretty big. To be able to keep it simple for a few pages here and there was what they wanted. They are not interested in a CMS heavy administration of basically static page content.
that's a thought. but the site is already in production. and they cannot add feature static pages via CKEditor. Really, the ability to create and manage a Contribute connection should be part of the product if the Contribute Compatibility is....