At Pantheon, we talk a lot about automating updates with testing and orchestrating multiple tools interacting to make a build system. For many folks, this might sound like some kind of mystic art. Literally the stuff of wizards and magic spells. But I am here to tell you, in all reality it is science. Computer science.
I’m happy to announce the release of a supported Command Line Interface (CLI) for the Pantheon platform. It’s free, open-source, built on Drush, and available on GitHub:
https://github.com/pantheon-systems/terminus
In a nutshell, Terminus allows you to do anything you can in the Pantheon dashboard from a terminal:
The invasion of Ukraine has both united and broken the world in unprecedented ways. The question facing many tech companies today is how to protect the internet and people relying on it for information.
Crippled by international sanctions and blocked from independent media sources, Russia has plunged into economic and digital darkness. With multinational companies leaving Russia at great speed, the public has called on high tech to follow suit and to create what the New Yorker called “a technology desert.”
This is the second post in a series on managing site configuration in code. You can find part one here, which introduces the idea of managing site configuration in code.
In this Forbes article, you’ll learn how WebOps is different from DevOps and what kind of team it takes to move the needle.
In May 2014, OpenView Advisors hired Churt to help the firm build a larger market share and knock content marketing out of the park. Running on legacy infrastructure and outsourcing to three different hosting vendors, Churt quickly realized that her team didn’t have enough control over their sites. After some research on the state of website hosting and discovering the more advanced website management platforms, Churt decided to bring OpenView’s websites over to Pantheon to take advantage of the workflow and long-term cost savings.
G2, a peer-to-peer review site, announced Pantheon as a leader in WebOps, Managed Hosting, and Web Content Management. This is a sign of what's to come.
When the first beta of Gutenberg was made available for testing, one of the most controversial decisions was that the default storage for block attributes is having the HTML saved in post content. Block attributes—the settings on blocks—can also be stored in post meta or other locations, but the system most core blocks use is to save the data as HTML (as the end user will view it) or to serialize it to comments.