serverlessworkflow · ricardozanini · Jun 18, 2026
@@ -1,6 +1,6 @@
-# Serverless Workflow Website Repository
+# Open Workflow Specification Website Repository
 
-This repository hosts the website for the [Serveless Workflow Specification](https://github.com/serverlessworkflow/specification) project at [https://serverlessworkflow.io](https://serverlessworkflow.io).
+This repository hosts the website for the [Open Workflow Specification](https://github.com/serverlessworkflow/specification) project at [https://serverlessworkflow.io](https://serverlessworkflow.io).
 
 ## 🧑 Contributing to the website
 

@@ -10,14 +10,14 @@ import {
 import Section from "./Section.astro";
 ---
 
-<Section title="💕 Love ServerlessWorkflow? Give us a Star on GitHub! ⭐" subTitle="Help us grow and show your support! Starring our repository helps more people discover and join our community.">
+<Section title="💕 Love Open Workflow Specification? Give us a Star on GitHub! ⭐" subTitle="Help us grow and show your support! Starring our repository helps more people discover and join our community.">
   <p class="text-center text-xl">👉<a class="link link-accent" target="_blank" rel="noopener" href={GITHUB_LINK}>Star our GitHub Repository</a></p>
 </Section>
 <footer class="bg-neutral text-neutral-content p-10">
   <div class="footer md:footer-horizontal max-w-7xl mx-auto">
     <aside>
       <p>
-        &copy; Serverless Workflow Authors | 
+        &copy; Open Workflow Specification Authors | 
         <a class="link" href="https://creativecommons.org/licenses/by/4.0" target="_blank" rel="noopener">CC BY 4.0</a> |
         <a class="link" href="https://www.linuxfoundation.org/legal/privacy-policy" target="_blank" rel="noopener">Privacy Policy</a>
       </p>

@@ -6,7 +6,7 @@ import ThemeIcon from './ThemeIcon.astro';
       <div class="navbar-start">
         <div class="flex gap-2">
           <div class="logo-header"></div>
-          <a class="text-xl font-bold" href="/">Serverless Workflow</a>
+          <a class="text-xl font-bold" href="/">Open Workflow Specification</a>
         </div>
       </div>
       <div class="navbar-end">

@@ -1,11 +1,11 @@
-export const DEFAULT_TITLE = 'Serverless Workflow';
-export const DEFAULT_DESC = `Serverless Workflow presents a vendor-neutral, open-source, and entirely community-driven ecosystem tailored for defining and executing DSL-based workflows in the realm of Serverless technology.`;
+export const DEFAULT_TITLE = 'Open Workflow Specification';
+export const DEFAULT_DESC = `Open Workflow Specification presents a vendor-neutral, open-source, and entirely community-driven ecosystem for defining and executing DSL-based workflows.`;
 
 export const CURRENT_VERSION = '1.0.3';
 
 export const GITHUB_ORG = 'https://github.com/serverlessworkflow/';
 export const GITHUB_LINK = GITHUB_ORG + 'specification/';
-export const SLACK_LINK = 'https://slack.cncf.io/';
+export const SLACK_LINK = 'https://cloud-native.slack.com/messages/open-workflow';
 export const X_TWITTER_LINK = 'https://x.com/cncfworkflow';
 export const LINKEDIN_LINK = 'https://www.linkedin.com/company/serverless-workflow/posts';
 export const DEV_MAILING_LIST_LINK = 'mailto:cncf-serverlessws-maintainers@lists.cncf.io';

@@ -0,0 +1,73 @@
+---
+title: Announcing our Rename to Open Workflow Specification
+author: Ricardo Zanini
+date: 2026-06-18
+description: >
+  We're excited to announce that the Serverless Workflow Specification project has been renamed to Open Workflow Specification, better reflecting our scope and vision as a platform-agnostic workflow orchestration standard.
+---
+
+We're thrilled to announce an important evolution for our project: **Serverless Workflow Specification is now Open Workflow Specification**!
+
+## Why the Change?
+
+When we started this journey, "Serverless Workflow" reflected our origins in the serverless computing ecosystem. However, as the project has matured and our community has grown, we've expanded far beyond serverless use cases. Today, the specification is used across diverse environments—from cloud-native applications to on-premises systems, from microservices orchestration to complex data pipelines.
+
+The name "Serverless Workflow" was becoming a barrier. Many potential users and contributors assumed the specification was limited to serverless architectures, when in reality, it's a vendor-neutral, platform-agnostic standard for workflow orchestration that works anywhere.
+
+**Open Workflow Specification** better captures our true nature:
+- **Open**: We're an open-source, community-driven CNCF project
+- **Workflow**: Workflow orchestration is what we do
+- **Specification**: We define a standard DSL, not a specific implementation
+
+## What's Changing?
+
+### Project Name & Branding
+- **New Name**: Open Workflow Specification
+- **DSL Name**: Open Workflow DSL (previously Serverless Workflow DSL)
+- **Community**: The #open-workflow Slack channel (previously #serverless-workflow)
+- **Organization**: We've secured the github.com/open-workflow-specification organization
+
+### What's Staying the Same?
+- **Our Mission**: Providing a vendor-neutral, platform-agnostic workflow orchestration standard
+- **The Specification**: All technical aspects remain unchanged
+- **Your Workflows**: No breaking changes to existing workflow definitions
+- **CNCF Membership**: We remain a proud CNCF Sandbox project
+- **Community**: Same amazing maintainers, contributors, and users
+- **GitHub URLs**: Old links will continue to redirect (for now)
+
+## What This Means for You
+
+**If you're using the specification:**
+- Your existing workflows continue to work without any changes
+- Schema URLs and references remain functional
+- SDKs will maintain backward compatibility
+
+**If you're contributing:**
+- Join us on Slack at #open-workflow (the #serverless-workflow channel is being migrated)
+- Update your bookmarks to our new GitHub organization (coming soon)
+- New documentation and resources will use the updated name
+
+## Looking Forward
+
+This rename marks an exciting milestone in our journey. By removing the "serverless" qualifier, we're opening doors to new use cases, new contributors, and new adopters who may have previously overlooked us due to our name.
+
+We remain committed to our core values:
+- **Vendor-neutral**: No lock-in, works everywhere
+- **Community-driven**: Your voice matters
+- **Platform-agnostic**: Cloud, on-prem, hybrid—we support it all
+- **Simple yet powerful**: Easy to learn, capable of handling complex workflows
+
+## Thank You
+
+A huge thank you to our community for your continued support. This change wouldn't be possible without the CNCF's approval and the hard work of our maintainers and contributors.
+
+We're excited about this next chapter and look forward to growing the Open Workflow Specification community together!
+
+## Get Involved
+
+- **Join our Slack**: [#open-workflow on CNCF Slack](https://cloud-native.slack.com/messages/open-workflow)
+- **Star us on GitHub**: [github.com/serverlessworkflow/specification](https://github.com/serverlessworkflow/specification)
+- **Attend our weekly meetings**: [Community Calendar](https://github.com/serverlessworkflow/specification/discussions/799)
+- **Contribute**: Check out our [Contributing Guide](https://github.com/serverlessworkflow/specification/blob/main/contributing.md)
+
+Here's to Open Workflow Specification! 🎉
@@ -7,14 +7,14 @@ import Section from '../components/Section.astro';
 <Layout title="Community">
   <Section title="" subTitle="" class="bg-primary text-primary-content">
     <!-- didn't use title/subTitle props because of the primary text on primary bg color -->
-    <h2 class="text-3xl font-bold text-center mb-4">Join the Serverless Workflow community</h2>
-    <p class="text-xl text-center">Serverless Workflow is an open source project that anyone in the community can use, improve, and enjoy. We'd love you to join us! Here's a few ways to find out what's happening and get involved.</p>
+    <h2 class="text-3xl font-bold text-center mb-4">Join the Open Workflow Specification community</h2>
+    <p class="text-xl text-center">Open Workflow Specification is an open source project that anyone in the community can use, improve, and enjoy. We'd love you to join us! Here's a few ways to find out what's happening and get involved.</p>
   </Section>
   <Section>
     <div class="grid grid-cols-2 gap-8">
       <div class="prose">
         <h3>Learn and Connect</h3>
-        <p>Using or want to use Serverless Workflow? Find out more here:</p>
+        <p>Using or want to use Open Workflow Specification? Find out more here:</p>
         <ul>
           <li title="User help">
             <a target="_blank" rel="noopener" href={GITHUB_LINK + 'discussions'}><i class="fa fa-envelope"></i> User help</a>:
@@ -32,22 +32,22 @@ import Section from '../components/Section.astro';
       </div>
       <div class="prose">
         <h3>Develop and Contribute</h3>
-        <p>If you want to get more involved by contributing to Serverless Workflow, join us here:</p>
+        <p>If you want to get more involved by contributing to Open Workflow Specification, join us here:</p>
         <ul>
           <li title="GitHub">
             <a target="_blank" rel="noopener" href={GITHUB_LINK}><i class="fab fa-github"></i> GitHub</a>:
             Development takes place here!
           </li>
           <li title="Slack">
             <a target="_blank" rel="noopener" href={SLACK_LINK}><i class="fab fa-slack"></i> Slack</a>:
-            Chat with other project developers at #serverless-workflow channel
+            Chat with other project developers at #open-workflow channel
           </li>
           <li title="Developer mailing list">
             <a target="_blank" rel="noopener" href={DEV_MAILING_LIST_LINK}><i class="fa fa-envelope"></i> Developer mailing list</a>:
             Discuss development issues around the project
           </li>
         </ul>
-        <p>You can find out how to contribute to Serverless Workflow in our <a href={GITHUB_LINK + 'blob/main/contributing.md' }>Contribution Guidelines</a>.</p>
+        <p>You can find out how to contribute to Open Workflow Specification in our <a href={GITHUB_LINK + 'blob/main/contributing.md' }>Contribution Guidelines</a>.</p>
       </div>
     </div>
   </Section>