merging

gatsby-config.js

@@ -104,6 +104,13 @@ module.exports = {
         name: `releasenotes`,
       },
     },
+    {
+      resolve: `gatsby-source-filesystem`,
+      options: {
+        path: `${__dirname}/source/content/iframeembeds`,
+        name: `iframeembeds`,
+      },
+    },
     {
       resolve: `gatsby-source-filesystem`,
       options: {

gatsby-node.js

@@ -139,7 +139,7 @@ exports.createPages = ({ graphql, actions }) => {
       allDocs: allMdx(
         filter: {
           fileAbsolutePath: {
-            regex: "/content(?!/(partials|changelog|guides|releasenotes)/)/"
+            regex: "/content(?!/(partials|changelog|guides|releasenotes|iframeembeds)/)/"
           }
           frontmatter: { draft: { ne: true } }
         }
@@ -195,6 +195,16 @@ exports.createPages = ({ graphql, actions }) => {
         }
       }
 
+
+      allIframeEmbeds: allMdx(limit: 10, filter: {fileAbsolutePath: {regex: "/iframeembeds/"}}) {
+          edges {
+            node {
+              slug
+              body
+            }
+          }
+        }
+
       allReleaseNotes: allMdx(
         filter: { fileAbsolutePath: { regex: "/releasenotes/" } }
         sort: { fields: [fileAbsolutePath], order: DESC }
@@ -444,6 +454,27 @@ exports.createPages = ({ graphql, actions }) => {
       })
     })
 
+    // Create iframeembed page
+    const iframeEmbeds = result.data.allIframeEmbeds.edges;
+    iframeEmbeds.forEach((iframeEmbed) => {
+
+      // There's an odd bug where the slug value is inconsistent, even for the same file
+      // across different gatsby builds. This is a workaround.
+      // if the slug does not contain "iframeembeds" the add it
+      if (!iframeEmbed.node.slug.includes("iframeembeds")) {
+        iframeEmbed.node.slug = `iframeembeds/${iframeEmbed.node.slug}`
+      }
+
+      createPage({
+        path: `${iframeEmbed.node.slug}`,
+        component: path.resolve(`./src/templates/iframeembed.js`),
+        context: {
+          slug: iframeEmbed.node.slug,
+          body: iframeEmbed.node.body,
+        },
+      })
+    })
+
     // Create contributor pages.
     const contributors = result.data.allContributorYaml.edges
     contributors.forEach((contributor) => {

source/content/guides/account-mgmt/traffic/03-overages.md

@@ -57,8 +57,6 @@ If you have an overage during any particular calendar month, you will be require
 
 To avoid future overage fees, you can [upgrade your plan](/guides/account-mgmt/plans) to a plan that is more appropriate for your current traffic volumes to avoid additional overage fees going forward. This new subscription will apply prospectively and will not retroactively change past overages.
 
-One benefit you’ll receive if you do upgrade to a new subscription, though, is you will restart your Overage Protection. For example, if you upgrade you plan on October 1, you will receive 1 month of free overage protection through the end of the calendar year.
-
 ## FAQs
 ### What environments count towards traffic limits?
 Only traffic for the Live environment is counted towards a site plan's traffic limit. Traffic for non-live environments (Dev, Test, and Multidev environments) are not counted towards the plan's traffic limit.

source/content/iframeembeds/certification/pressure-on-developers.md

@@ -0,0 +1,6 @@
+---
+title: WebOps Certification
+subtitle: "Pressure on Developers"
+---
+
+<Partial file="certification-guide/pressure-on-developers.md" />

source/content/iframeembeds/certification/pressure-on-it.md

@@ -0,0 +1,6 @@
+---
+title: WebOps Certification
+subtitle: "Pressure on IT"
+---
+
+<Partial file="certification-guide/pressure-on-it.md" />

source/content/iframeembeds/certification/what-is-webops.md

@@ -0,0 +1,6 @@
+---
+title: WebOps Certification
+subtitle: "What is WebOps?"
+---
+
+<Partial file="certification-guide/what-is-webops.md" />

source/content/iframeembeds/certification/what-problems-does-webops-solve.md

@@ -0,0 +1,6 @@
+---
+title: WebOps Certification
+subtitle: "People Under Pressure: What Problem Does WebOps Solve?"
+---
+
+<Partial file="certification-guide/what-problems-does-webops-solve.md" />

source/content/partials/certification-guide/pressure-on-developers.md

@@ -0,0 +1,37 @@
+### Pressure on Developers: Stay on the Critical Path
+
+<Alert title="By the end of this section, you should be able to:" type="info" >
+
+* Explain some of the extra tasks a developer is typically expected to perform, beyond simply writing code.
+* Describe how putting WebOps guardrails in place ahead of time helps Developers be more productive and work more efficiently.
+
+</Alert>
+
+Developers often feel caught in the middle. On one side, they have the Product Owner always asking for more to be done faster. On the other side, they know IT leaders are willing to slow down to stay safe. Navigating these competing pressures, staying on the critical path can feel like a puzzle.
+
+That's OK. Developers tend to like puzzles.
+
+Developers thrive on solving complex problems by breaking down business requirements, tasks and functions into discrete parts that work interchangeably with other parts. Their work requires deep focus, pinpoint attention to detail, a great deal of patience, as well as creativity and a collaborative spirit. 
+
+As web applications have become more complex over time, however, being a developer has often meant taking on additional tasks that can distract them from the critical path that gets quality code out the door.
+
+Some examples of the additional tasks that pull focus for Developers are:
+
+* **Setting up and maintaining a local development environment:** This process often involves installing and configuring various software and tools, which can be time-consuming and complex.
+* **Managing infrastructure:** Developers are sometimes tasked with ensuring that servers, storage, networks, and other systems are properly set up and functioning optimally.
+* **Ensuring server uptime:** It's essential to keep websites accessible and performing well, which can involve monitoring servers, managing traffic loads, and troubleshooting any issues that arise.
+* **Handling site maintenance:** Regular updates, backups, and troubleshooting are needed to keep a website running smoothly.
+* **Deploying code to production servers:** This task involves moving code from a testing or staging environment to a live server where it's accessible to users. This process can be tricky and, if not done correctly, can lead to service disruptions.
+* **Database management:** Developers often have to backup and restore databases, as well as ensure their security and performance.
+* **Troubleshooting performance issues:** Developers may need to review server logs, monitor system resources, and use other tools to identify and resolve performance bottlenecks.
+* **Securing websites: **This involves implementing security measures, staying up-to-date with the latest security patches, and ensuring compliance with data privacy regulations.
+
+
+
+It’s easy to see where the lines can be blurred between what Developers are concerned with and what IT is concerned with. At the end of the day, though, Developers are the ones who are on the hook for delivering the digital product owned by Marketing and secured by IT. With real deadlines and deliverables, Developers do not have the luxury of working around these extraneous tasks and systems in order to simply write code. They must deal with whatever is in their way and causing friction. And for this reason, the only way to optimize a Developer’s time and maximize their job satisfaction is to remove as much of the friction-causing concerns as possible.
+
+That's where you need a  WebOps platform!
+
+An effective WebOps platform can simplify a Developer’s job and allow them to focus on their primary work of writing code and deploying wonderful features. By packaging up environmental dependencies into a portable, containerized environment, WebOps makes it simple and straightforward to set up a local development environment where the Developer can be productive wherever and whenever they prefer - on the couch, in the early hours of the morning, on an airplane, or on the beach. A WebOps platform can securely wrap features into a pushbutton format, where tasks like spinning up a new, non-production, environment for developing and testing features, backing up the database and files to prevent data loss, versioning code to preserve the ability to roll back unwanted changes, and kicking off a Continuous Deployment pipeline can be done simply and without risk. 
+
+And when that WebOps platform is also part of an enterprise-grade, scalable, secure and performant web hosting environment, Developers no longer have to weigh concerns around infrastructure maintenance, server uptime, or cloud security. In other words, a WebOps platform removes most of the friction that prevents Developers from being as efficient and productive as they can be. And we believe this can make their jobs more collaborative, less stressful, and ultimately more fulfilling. 

source/content/partials/certification-guide/pressure-on-it.md

@@ -0,0 +1,38 @@
+### Pressure on IT: Preserve Stability
+
+<Alert title="By the end of this section, you should be able to:" type="info" >
+
+* Describe the types of challenges that IT leaders are typically most concerned about.
+* Explain why marketing teams might view IT as a bottleneck.
+
+</Alert>
+
+While Marketing teams are laser focused on hitting those KPIs, driving customer engagement, brand visibility, and lead generation, IT teams have their own set of pressures. 
+
+Some of the concerns that keep IT up at night include:
+
+* **System Stability**: IT operates in a world where any system downtime can result in significant business losses, as well as lost productivity and damage to the company’s reputation.
+* **Data Security:** IT must protect data from breaches, which could result in financial loss, damage to the brand reputation, and legal consequences.
+* **Infrastructure Scalability:** As businesses grow, IT is responsible for ensuring that the company’s digital infrastructure keeps pace with the growing needs of the business. This involves anticipating future needs, planning for increases in traffic, and implementing systems that are flexible enough to scale with the business.
+* **Technology Maintenance and Upgrades:** Aging technology that is not maintained properly can quickly become a security liability. IT ensures that key technologies are secure and up to date with the latest security updates. They manage software updates, hardware upgrades, and integration of new technologies into existing infrastructure.
+* **Compliance:** IT teams have to ensure that all systems are compliant with the appropriate regulations for their industry in order to avoid legal penalties.  
+
+IT **people** tend to prefer **processes** that emphasize thoroughness over speed in the face of these responsibilities. Marketing often requires fast turnarounds to keep up with market trends, competitive pressures, or campaign schedules. This discrepancy can often lead Marketing to view IT as a bottleneck.
+
+Another important thing to keep in mind is that the marketing website is just one application among many. IT is usually also responsible for managing entire fleets of systems and applications that make enterprises and organizations run. Where the Marketing team sees the website as a growth engine and a living, breathing entity, IT views it through the lens of mitigating risk, and maintaining stability, security and scalability. The old adage, “if it ain’t broke, don’t fix it” tends to resonate with IT’s aversion to risk. Marketing’s desire to experiment and continuously iterate on the website has the potential to make IT very nervous.
+
+That's why you need a WebOps platform!
+
+WebOps platforms automate repetitive tasks where constant manual interventions are not only inefficient, but also risky, in that they introduce risk of human error, threatening the stability and security of the website. A WebOps platform provides the tools and workflows to allow teams to automatically adhere to best practices every time by packaging multiple manual steps into automated, repeatable functions. This process is commonly known as a CI/CD pipeline, which includes three separate but related practices: Continuous Integration, Continuous Delivery, and Continuous Deployment (see fig. 1.1 for more detail).  
+
+#### Web Development Terminology: CI/CD Workflow
+
+**Continuous Integration** (CI) is the process of automatically turning the commits you make in your codebase into a usable build (website). It involves integrating changes from multiple contributors into the main codebase frequently, often several times a day. Each integration is verified by an automated build and test process to catch errors early. Continuous Integration requires some level of testing to verify that the build process succeeded. With CI you define how your code is transformed into a working site; often living in a sandbox environment.
+
+**Continuous Delivery** introduces the concept of a “deployment pipeline.” Continuous Delivery forces you to define in detail how your deployment pipeline takes changes from that sandbox and gets them to the production environment. Sites on Pantheon use a deployment pipeline that goes through our Dev, Test and Live environments. Doing Continuous Delivery requires adding on to the automated tests created to fulfill Continuous Integration. When your changes move through the deployment pipeline, your Continuous Delivery process should validate that the site works in each environment.
+
+**Continuous Deployment** is a business decision to send all changes straight through the deployment pipeline once tests have passed on those changes. With a strong deployment pipeline created in Continuous Delivery, Continuous Deployment is a simple business question. Ask your stakeholders “Do you want each change sent through the deployment pipeline to live as soon as the change is approved/merged? Or do you want changes held so that they are deployed in bunches at the end of each sprint (or other schedule)?” For many web agencies and their clients it is preferable to stick with scheduled releases.
+
+With guardrails in place through WebOps automation, IT can rest easier knowing that they don’t have to manually evaluate each task against their risk mitigation framework. They can allow Marketing to enjoy the convenience and velocity of self-service capabilities such as spinning up new website environments, publishing code commits, and granting limited access to additional developers on a project.
+
+With a WebOps platform, IT is no longer a bottleneck to Marketing, and instead becomes a business partner, strategizing with Marketing over how best to implement WebOps and therefore increase velocity of delivery, remove complexity, and deliver better results. Marketing relies on IT for strategic guidance and implementation, but they are no longer reliant on IT for common, repetitive tasks that could be done more efficiently without having to loop in IT. 

source/content/partials/certification-guide/what-is-webops.md

@@ -0,0 +1,44 @@
+## What is WebOps
+
+<Alert title="By the end of this section, you should be able to:" type="info" >
+
+
+* Define WebOps and the principles it emphasizes.
+* Describe WebOps' impact on the lifecycle of a web application.
+* Describe why WebOps is particularly valuable for Open Source developers.
+* List three general problems that can be solved through the implementation of WebOps.
+
+</Alert>
+
+Websites, like other software ecosystems, need to take the following factors into account:
+
+* Competing needs of different groups of **people**
+* Incongruent **processes** preferred by those groups
+* Approaches to **platform** technology
+
+If you've worked in software in recent years, you're likely familiar with the term "DevOps" and how it addresses this set of factors. DevOps is a collection of practices and tools designed to unify and streamline the processes of software development ('Dev') and IT operations ('Ops'). The fact that DevOps has become so popular underscores a critical hurdle in contemporary software development - that successful software releases are a team sport, requiring cohesive cross-functional collaboration, and that bridging the gap between diverse teams, each with its own perspectives and objectives, and guiding them towards a shared goal, can be complex and challenging.
+
+Put simply, WebOps seeks to apply the principles of DevOps to applications on the web, where digital marketing teams fight hard to deliver business impact through their most important channel - Digital.
+
+**WebOps is the practice of maximizing the value of web channels by driving the velocity of change.**
+
+WebOps requires  practices and principles for building and optimizing websites that emphasize cross-functional collaboration, automation of repeatable tasks, and a continuous iterative improvement model that lasts throughout the lifecycle of a website.
+
+WebOps methodologies help cross-functional teams work in harmony, improving the productivity and efficiency of the entire web team, from developers and designers to content editors and marketing and IT stakeholders. By facilitating the shift from the monolithic waterfall approach that has traditionally guided website launches, to an iterative, continuous cycle of measurable improvements over time, WebOps allows the website to change with velocity as a living, breathing entity that can deliver true impact at each stage of its lifecycle.
+
+At its core, WebOps leads teams to breaking down silos and creating a culture of collaboration and continuous improvement. By automating repetitive tasks and using tools that facilitate communication and feedback, teams can work more rapidly and more efficiently by reducing the risk of errors or miscommunications. This puts marketing teams in position to respond to changing business needs, market shifts, and new user requirements in real time.
+
+WebOps also emphasizes continuous integration and delivery, meaning that changes are tested and deployed quickly and reliably. This is achieved through the use of automated testing and deployment tools, which can help catch errors early in the development process and reduce the risk of downtime or other issues.
+
+For Open Source developers, WebOps is especially important because it provides a framework for managing the entire web development process, from design to deployment. Both Drupal and WordPress have lifecycles that often entail complex development requirements, cross-functional collaboration, performance and security considerations, and automated testing and deployment. By emphasizing collaboration, automation, and continuous integration and delivery, WebOps can help Drupal and WordPress developers work more efficiently and reduce errors.
+
+Ultimately, WebOps sets the stage for a high-performing team dynamic, enabling cross-functional collaboration, enhancing productivity, and driving superior end results. The flexibility inherent in this approach ensures businesses can adapt and thrive in an ever-evolving digital landscape.
+
+
+<Alert title="Key Takeaways" type="info" >
+
+* Successful software delivery is a collaborative effort among many different stakeholders and teams. Its success depends on how well these teams work together.
+* WebOps helps teams collaborate to successfully apply the principles of DevOps to their website, which is one of the most important marketing channels for driving the business forward.
+* Unlike traditional software, the website is a living, breathing entity that requires continuous feedback and improvement over time. WebOps makes this feedback loop faster and easier to navigate.
+
+</Alert>