Zaphne – Content Automation News for 06-30-2018

Automate IT Infrastructure

Chef Automate aggregates data about all systems you manage with chef, even across multiple Chef Servers, in one dashboard that can be searched or filtered according to your needs. With a full history of changes that have been applied, a trend graph of system health, and corresponding compliance dashboard, Chef Automate provides a single pane of glass into changes across your estate. Chef Automate gives you access to the level of detail you need, whether you’re an executive, practitioner, or anything in between. Each dashboard provides high level health information about your estate, with the ability to drill into each node, run list, or even individual resource that was run on each converge. Whether you just want to confirm your nodes are checking in successfully, or need to drill into error details for troubleshooting, Automate provides everything you need in one place. 

Chef Automate’s Workflow allows you to create a formal delivery pipeline for all your Chef code. Workflow provides a prescriptive set of stages for code promotion, and built-in tools for enforcing code review, approval, dependency management, and automated testing make it easier than ever for large teams to release changes safely, without losing momentum in their automation efforts. 

Keywords: [“Chef”,”Automate”,”need”]
Source: https://www.chef.io/chef

Application Deployment Automation

IBM UrbanCode Deploy is a tool for automating application deployments through your environments. Perhaps a three tier application with database, app and content components. Or A mobile application with the actual mobile application and back-end web services. UrbanCode Deploy tracks which components make up an application so they can be deployed and tracked together. Snapshots offer the ability to create a version of the application encapsulating versions of each of the components. 

Deployment automation tools need to know how to deploy your applications. Application processes are composed of component processes. You connect to clouds, model the virtual images in the environment, and add your application components to those images. You can provision environments and deploy the application components automatically and on demand. Because these rules are set per application and per environment, early test environments are likely to be setup to not require approvals. 

Integrations are provided for application servers, load balancers, databases, testing tools, build servers and more. Teams who have great deployment scripts already can continue to use them through UrbanCode Deploy either by directly calling the scripts, or embedding them in custom plugins. 

Keywords: [“Deploy”,”application”,”environment”]
Source: https://developer.ibm.com/urbancode/products/urbancode-deploy

Design versus automation: a strategic approach to content

It’s possible to deliver content in an automated workflow that uses a stellar design. A strategic approach to content needs to incorporate both design and automation as constraints and find the right balance between the two. Instead, think of design and automation as different facets of your content. The interesting quadrant is the last one: high design and high automation. You can accommodate 90% design and 100% automation or 90% automation and 100% design, but if you are unwilling to compromise on either axis, expect to spend a lot of money. 

When we discuss design versus automation, we are really arguing about when to implement a particular design. The publishing process is then a matter of applying the predefined design to new content. The traditional design process ingests content and then people apply design elements to it manually. In other words, automation requires design first, and this approach disrupts the traditional approach to design. Editorial designers know that the secret isn’t content first or content last it’s content and design at the same time. 

When we design with content the way we should, design augments the message of the content. A level we best achieve when we work with our editors and content creators as we design. 

Keywords: [“Design”,”content”,”automation”]
Source: https://www.scriptorium.com/2015/08/design-versus-automation-a…

Why Automated Curation Never Works

I’ve seen many automated content curation tools popup now and then. Li that claim content curation but are just veiled attempts at aggregation. Our philosophy is different than many of these curation tools. This drives our philosophy in not only what features we add to the base Curation Suite™ platform but also the types of features we add to the Listening Engine. It’s when you add this content discovery to the mix where things get a little murky and turn some content curation tools to the dark side. 

While the content you share is the appetizer, the commentary is the main course, the drinks, and the desert. The current state of automated curation looks at social shares and content engagement. No computer or curation tool can get even close to knowing this. Good content curation evokes an emotion in your audience. If we designed a way to automate content curation and it worked highly effectively and we could monetize it-I wouldn’t share it with you. 

Although one of their main sources is Reddit it’s still a fair amount of effort to put out content that will get people to click, share, and consume. I could probably list 5-6 more reasons why automated curation isn’t effective but in the end good content curation still requires a human element. 

Keywords: [“curation”,”content”,”audience”]
Source: https://curationsuite.com/…/why-automated-curation-never-works

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.